Nate Jensen

This is a really old ticket. It appears it was written against Jep 3.3 when I added numpy support. For the record, newer versions of Jep release the GIL **every**...

@kaiseu, you can use multiple Java threads with Jep. Just use a separate Jep instance for each Java thread. You can only set the Jep library path once and it...

> After doing that many tests started to fail and I checked several and they are using SubInterpreters. Are you saying SharedInterpreters are ok? I found on [this ticket](https://bugs.python.org/issue45056) they...

Besides the jep script, does running `python` from the command line work and if so can you import encodings? It sounds like the Python install may be incomplete somehow. It...

Target for 3.9.1 or 4.0.0, whichever comes first.

I retract my statement about targeting a fix for a release, as the idea that sys.prefix and sys.exec_prefix are different is now shown to be incorrect. At present we cannot...

This may be irrelevant because the original ticket is at runtime on macOS and this error I'm linking to is at build time on Linux, but when building on travisCI...

https://bugs.python.org/issue38236 added extra output to Python 3.8 and 3.9 when this occurs. Hopefully the extra output helps developers figure out what is going on.

Possibly related to #284

I got this on macOS with Python 3.7 and Jep 4.0 in a virtualenv. The fix was to **not** set PYTHONHOME which then caused the jep script to not see...