Ben Steffensmeier

Your error is likely caused because the Java process cannot find the python310 dll. You could try setting PYTHONHOME to "C:\Users\Daniel\AppData\Local\Programs\Python\" or adding the directory where the python310 dll is...

> But now I have another question. In your .bat-file, I see the line > SET jni_path="C:\Users\Daniel\AppData\Local\Programs\Python\Python310\Lib\site-packages\jep" > But really (after setting PYTHONHOME) all works fine even I does not...

This is a duplicate of #401 and a fix has already been written and will be included in the next release of Jep. In the meantime if it is unnacceptable...

I have added a [Roadmap](https://github.com/ninia/jep/wiki/Roadmap) to the wiki with our release plans. Next release will come out around October 2022.

I think this is an interesting idea and people would definitely appreciate having something like this in Jep. One concern I have is that it would really make it difficult...

> 1. Have the thread-safe interpreter expose an `exec` method, and calls could then run The problem here is that every method on PyObject is calling back into python, even...

There is currently no way to get the python exception from a JepException. I have considered adding the python exception to the JepException as a PyObject but it never seemed...

1. I agree we need some way to throw and ideally also catch specific Python exceptions from Java. One suggestion I have seen before is that we could have subtypes...

It looks like the decimal module is not entirely compatible with sub-interpreters. I can repeat this problem without jep using the cpython api for testing subinterpreters(code below), so I do...

You may be running into the Global Interpreter Lock(GIL). More information about [Jep and the GIL is on the wiki](https://github.com/ninia/jep/wiki/Jep-and-the-GIL).