Closed its-ogawa closed 2 years ago
It's always doing something like:
import six
print(six.__version__, six.__file__)
as close as possible to the problem code, and check to make sure you are running the copy of six you think you are, and the version. For instance, The 3D program Maya provides an ancient copy of six as part of its MASH plugin, and it wound up higher on sys.path than the copy of six we had made available. We had to adjust our sys.path addition to be higher than Maya's. There might be something similar here with this "wandb" package the stacktrace mentions, or elsewhere in the Python environment.
It's always doing something like:
import six print(six.__version__, six.__file__)
as close as possible to the problem code, and check to make sure you are running the copy of six you think you are, and the version. For instance, The 3D program Maya provides an ancient copy of six as part of its MASH plugin, and it wound up higher on sys.path than the copy of six we had made available. We had to adjust our sys.path addition to be higher than Maya's. There might be something similar here with this "wandb" package the stacktrace mentions, or elsewhere in the Python environment.
Thank you! You've just saved my life, hhhh.
I am using espnet. When I do the following import, I get a module error for six.
I am using version 1.16.0 of six. When or if will I be able to use collections_abc in my version?