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
We will often need to ship a jars only to users, but some of the visualization software will be in python. Shipping a separate python package means the potential for version shear. It would be best if we can get a hook into the jpype.imports system to check to see if init.py exists in the jar and load the python module from there. There are some existing examples for loading a module from memory in stackoverflow and the python docs. Perhaps one of them would be a working base.
The text was updated successfully, but these errors were encountered:
We will often need to ship a jars only to users, but some of the visualization software will be in python. Shipping a separate python package means the potential for version shear. It would be best if we can get a hook into the jpype.imports system to check to see if init.py exists in the jar and load the python module from there. There are some existing examples for loading a module from memory in stackoverflow and the python docs. Perhaps one of them would be a working base.
The text was updated successfully, but these errors were encountered: