scoder
I should add one more thing: while this is a lot of work, it's probably quite easy. Why? Because it should be done at the C code level. That means...
Well, I should mention that there is a drawback to this. If Cython code cannot adapt to the specific CPython (minor) version, nor use CPython internals, it will run slower....
Nice! A really cool side-effect of having these two compilation modes in Cython is that it allows module authors to easily test and benchmark both, and then decide for themselves...
Further updates and fixes came in PR #3311, with more to come.
> we already have more internal patches that we should be upstreaming at some point Yes, you should, absolutely. :)
> PEP 652 was recently accepted, which I think may make this more easy to use!? The PEP basically says that they will take more care in maintaining that subset...
@gnossen, I think @eduardo-elizondo stopped working on this in 2020 and there were only a couple of improvements since then. You could look into https://github.com/cython/cython/issues/4495 to help us move it...
Sounds like running the tests in a CPython debug build might provide some hints.
I agree with what Robert said, also regarding a discussion on the list. To add a bit to that, CPython 3.8 is [scheduled](https://www.python.org/dev/peps/pep-0569/) for October 2019, and that seems like...
As discussed on the cython-users mailing list, Cython 3.0 will still provide support for Python 2.7, both for running the compiler in it and for building and using the generated...