Ben Steffensmeier

> * Should we focus on trying to make it work for 4.2 or 4.3? I do not plan on making 4.2.x work with isolated sub-interpreters. Normally a crash is...

> Just to know, is there an ETA for 4.3? The current plan is to release 4.3 after Python 3.14 comes out which puts it in October. Since the sub-interpreter...

I have managed to eliminate the errors in my testing when using isolated sub-interpreters on the dev_4.3 branch with the changes in #601. Any additional testing on this branch before...

It looks like the crash is in `javac`. There were some small changes to java files in Jep 4.2.2 but nothing major. It looks like the specific compile command that...

Thanks for the Dockerfile. I've built it 30 times on my machine and it succeeded each time. After building a few times I changed the Dockerfile to add an ARG...

> Wait, it seems necessary to check that `pyAttr` is not `NULL` before proceeding with `Py_DECREF(pyAttr);`, that is: jobject_as_PyObject() only returns null when the python exception is set so the...

> > > Wait, it seems necessary to check that `pyAttr` is not `NULL` before proceeding with `Py_DECREF(pyAttr);`, that is: > > > > > > jobject_as_PyObject() only returns null...

> `Java_jep_python_PyObject_equals` > Okay, I'm not very familiar with Python's C interface. I was just considering whether we need to maintain consistency with the rest of the code, such as...

I finally had some time to look at this closely. I added a test to see if equals is leaking and found it is not leaking, I just didn't notice...

You need to ensure that both your java and python installation are built for the same architecture,either x86_64 or arm64. Right now they are each using a different architecture so...