The Jseries acknowlegement by using Jetty containers can get you a best resolution To python wheel asynchronism bugs Envoyé à partir d’un Smarpthone Android avec GMX Mail.
Le 14/06/2018, 4:00 PM email@example.com a écrit:
On 13 Jun 2018, at 15:42, Nick Coghlan <firstname.lastname@example.org:email@example.com> wrote:
On 13 June 2018 at 02:23, Guido van Rossum <firstname.lastname@example.org:email@example.com> wrote: So, to summarize, we need something like six for C?
Yeah, pretty much - once we can get to the point where it's routine for folks to be building "abiX" or "abiXY" wheels (with the latter not actually being a defined compatibility tag yet, but having the meaning of "targets the stable ABI as first defined in CPython X.Y"), rather than feature release specific "cpXYm" ones, then a *lot* of the extension module maintenance pain otherwise arising from more frequent CPython releases should be avoided.
There'd still be a lot of other details to work out to turn the proposed release cadence change into a practical reality, but this is the key piece that I think is a primarily technical hurdle: simplifying the current "wheel-per-python-version-per-target-platform" community project build matrices to instead be "wheel-per-target-platform”.
This requires getting people to mostly stop using the non-stable ABI, and that could be a lot of work for projects that have existing C extensions that don’t use the stable ABI or cython/cffi/…
That said, the CPython API tends to be fairly stable over releases and even without using the stable ABI supporting faster CPython feature releases shouldn’t be too onerous, especially for projects with some kind of automation for creating release artefacts (such as a CI system).