You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This came up on Slack from @cms21 and I have replicated it in my own environment.
The example in docs/userguide/examples used in https://parsl.readthedocs.io/en/stable/userguide/modularizing.html do not work right away: the guide does not talk about making the library modules importable (for example by placing on PYTHONPATH or installing in a package) and so attempting to run the examples fails with an import error on htex workers.
...
File "/opt/homebrew/anaconda3/lib/python3.9/site-packages/dill/_dill.py", line 444, in load
obj = StockUnpickler.load(self)
File "/opt/homebrew/anaconda3/lib/python3.9/site-packages/dill/_dill.py", line 434, in find_class
return StockUnpickler.find_class(self, module, name)
ModuleNotFoundError: No module named 'library'
History
Originally this example used the thread executor which does not have this problem, as it will be running in the submitting process which will have an import path likely to include the directory of the library.
PR #1719 changed this example to use the high throughput executor.
But sys.path is different inside the process_worker_pool and less likely to contain the library as described.
The text was updated successfully, but these errors were encountered:
This came up on Slack from @cms21 and I have replicated it in my own environment.
The example in docs/userguide/examples used in https://parsl.readthedocs.io/en/stable/userguide/modularizing.html do not work right away: the guide does not talk about making the library modules importable (for example by placing on
PYTHONPATH
or installing in a package) and so attempting to run the examples fails with an import error on htex workers.History
Originally this example used the thread executor which does not have this problem, as it will be running in the submitting process which will have an import path likely to include the directory of the library.
PR #1719 changed this example to use the high throughput executor.
But
sys.path
is different inside the process_worker_pool and less likely to contain the library as described.The text was updated successfully, but these errors were encountered: