-
Notifications
You must be signed in to change notification settings - Fork 150
Ben Steffensmeier edited this page Dec 16, 2023
·
28 revisions
- Jep should work with any pure Python modules. CPython extensions and Cython modules may or may not work correctly, it depends on how they were coded. There are various techniques to try and overcome some of the complications of CPython extensions, please see the Workarounds for CPython Extensions page.
- Jep works with a variety of CPython extensions. Developers have reported that Jep works with numpy, scipy, pandas, tensorflow, matplotlib, cvxpy, and more. Please let us know what other CPython extensions you are using with Jep or update this list.
- That's a complex question. It depends on your project's requirements, but here's a simplification of the question. Do you want to run a Java process or a Python process?
-
Java
- Do you need to use CPython modules (e.g. numpy)?
- Yes: Jep is a good fit because we strive to work well with native CPython modules.
- Do you need to use CPython modules (e.g. numpy)?
-
Python
- Sinces Jep embeds CPython, it can run Python code just like other Python interpreters. But it cannot be launched from a Python process (we may add this in the future). If you want access to Java from a Python process, consider the following projects:
-
Java
-
This error informs you that the Java process cannot find Jep's built C library. The name of the library is somewhat platform dependent, it is usually libjep.so on Linux, libjep.jnilib on OS X, and jep.dll on Windows. There are a few different ways to fix the problem:
-
New in version 3.8: Jep will try harder to find the native library for you if you set the PYTHONHOME environment variable. When using Anaconda, set PYTHONHOME to your Anaconda installation directory, e.g.
$(HOME)/anaconda3
. - Place the shared library where Python has its other shared libraries. This is usually python/lib with *nix systems and python/dlls with Windows systems.
- Set an environment variable that tells Java the directory of the Jep shared library.
- On Linux, set
LD_LIBRARY_PATH
. - On OS X, set
DYLD_LIBRARY_PATH
. - On Windows, set
PATH
.
- On Linux, set
- Pass the argument
-Djava.library.path
to your Java process with the location of the Jep shared library. -
New in version 3.9: You can set the absolute path of the native jep library in code by using
MainInterpreter.setJepLibraryPath(String absolutePath);
-
New in version 3.8: Jep will try harder to find the native library for you if you set the PYTHONHOME environment variable. When using Anaconda, set PYTHONHOME to your Anaconda installation directory, e.g.
-
See http://stackoverflow.com/questions/20038789/default-java-library-path for more information.
-
An example to automatically load the Jep's C library is at https://gist.github.com/vwxyzjn/c054bae6dfa6f80e6c663df70347e238
- The jars are available through Maven, the native library is not. Look at the pom.xml file to find the groupId is black.ninia and the artifactId is jep.
- We haven't tried it yet. In theory it should possible, but there may be some challenges to overcome. If you try this, we'd love to hear about it and will gladly accept contributions to make Jep work well on more platforms.
- Jep has been run with Swing and SWT.
- Yes.
-
eval(String)
was originally written to support interactive mode or non-interactive mode (multiple statements or a single statement, see javadoc), so the boolean return value is whether or not the statement was actually executed. There is also an overhead of always returning the result, especially if code is making multiple calls to eval(String) and doesn't need the results. To change the method signature now would potentially break compatibility with a number of applications. -
getValue(String)
is almost identical in the C code toeval(String)
and will return the result of the evaluation, and can be used instead of eval where desired. For example:
// evaluates and discards the result
jep.eval("2 + 4");
// evaluates and places the results in x
jep.eval("x = 2 + 4");
Integer x = (Integer) jep.getValue("x");
// evaluates and returns the results
Integer y = (Integer) jep.getValue("2 + 4");
- If you see fatal Python errors when first using Jep, that often implies the
PATH
orLD_LIBRARY_PATH
environment variables are incorrect or inconsistent. This is often seen if multiple versions of Python are installed and/or Jep was built with a different version of Python than it is running with.
- Jep is only officially supported and routinely tested using the CPython reference distribution. There are just too many different combinations of Java, Python, and OS variants to be able to support them all. For Windows the versions on AppVeyor are used for development and testing. For OS X the version available on Travis CI is used for development and testing. The default Python on most *nix variants is almost always a compatible CPython build.
- Many Jep users have reported Jep works with Anaconda.
- Other versions of Python may work but they do not receive routine testing and they may require additional effort to ensure that the correct versions of all native libraries can be loaded. If you are having trouble you can try Google or the Mailing List to see if there are other users with a similar setup.
- Yes.
- Yes, however there are currently a few limitations
- You must ensure that all Python threads have completed before closing Jep.
- You cannot access Java from any new Python threads.
- Jep does not provide any sand-boxing of the executed Python so code will have the full power of Python including the ability to read/write files and start new processes. In general executing Python code from jep is as safe as running the code from the eval() function in Python. There are numerous articles and discussions online about how safe eval() is, I find this stackoverflow post provides a concise explanation and it contains many links for more information.