Benedikt Reinartz

Well, one can generate a process-independent environment (`OwnedEnv`), create terms from there and keep those around across `.await` points. But that shouldn't be an issue, right?

Sorry for the late reply. Could you give a sketch of how one would fix 2360 with this?

Thanks! Would you mind adding tests for this and #702?

Any help is appreciated. There is a branch you can test (https://github.com/pythonnet/pythonnet/pull/2611), but our CI is currently thoroughly broken and I haven't found the time to fix it, yet.

Work is happening in #2611. It works in general, but there are at least two crashes that I (or someone who wants to dive in) have to investigate.

It is not. 1. Please don't cross post. If you have an issue, open one, don't comment in two unrelated threads. 2. Please add more data than "does not work"....

Status report: After applying the alignment "fix" (thanks!), things work for the most part. There are some crashes in explicit garbage collection, so I have disabled those tests for now.

Also, we currently apparently have a weird inheritance order for our meta type, which leads to it using the `PyObject_GenericSetAttr` instead of `type_setattro`, which in turn triggers assertions since https://github.com/python/cpython/commit/5a1618a2c8c108b8c73aa9459b63f0dbd66b60f6

There you go. There are still pending issues with the embedding tests that are being worked on in #2638, but I'd be fine with releasing a wheel if we get...

This is the issue that we run into with the `PyObject_GenericSetAttr` usage: - https://github.com/cython/cython/issues/6323 - Related Python PR: https://github.com/python/cpython/pull/118454