fix PyCall.__init__
when no __main__
present
#819
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In some environments,
__main__
isn't a module, eg on an ipyparallel worker__main__
is aIPython.core.interactiveshell.DummyMod
, causing PyCall to error on loading because thatpyeval_
is trying to use__main__
by default. Or worse, if you've compiled a custom sysimage with PyCall (eg for pyjulia), then an error during__init__
means a segfault. This fixes that.Actually, with this PR, I can now run an
ipyparallel
cluster of Python workers calling Julia via pyjulia w/ custom sysimage 馃帀Seems a decent bit of people on the pyjulia Issues have been trying do similar stuff (also with multiprocessing and/or Dask), maybe this will be a helpful solution to point out there assuming this PR makes sense to you guys.