Closed jacopo-chevallard closed 5 years ago
I could make the test work by running pip uninstall multiprocess dill pathos
and reinstalling with conda install -c conda-forge pathos
, I have now multiprocess-0.70.5, dill-0.2.8.2, and pathos-0.2.1
That's weird... hmm. Thanks for your report. I just tried your code with your exact package configuration, and I'm not seeing an error. So the only thing I can think of is... is there some weird naming conflict? You'll notice that the import is from . import source...
, so that means it's supposed to be looking in the same directory for source.py
, which is actually dill.source
.
That error you are seeing is coming from dill
... and the version of dill
in both cases is the same for you... so that's terribly strange.
The difference between the versions of pathos
is primarily for python 3.7 support, so that shouldn't also be an issue. The update to multiprocess
was significant, in that I updated the 2.7
support to python 2.7.15
, so that might be something if it's not an $PATH or naming issue.
Thanks for the quick feedback, I'll take a look at potential path/naming issues and report back
@jacopo-chevallard: Any resolution on this on your side? Since I didn't hear back from you, can I assume it was resolved?
After rereading this thread, here's what I expect happened... I expect you have a pip
install and a conda
install, and they are different installations -- both in different directories. That can lead to weird import conflicts and failures, link conflicts and failures, and versioning conflicts and failures. I expect the uninstall and reinstall with conda
resolved it either by fixing a broken install or resync'ing a broken dependency chain due to having two different installs seen on a single PATH
.
Please feel free to reopen if the issue is not resolved.
Hi, I'm running Python 2.7.15 and just updated pathos (to version 0.2.2.1) and dependencies (dill-0.2.8.2, multiprocess-0.70.6.1), and unfortunately I'm getting this strange error
when running this simple example
any hint?