Hi, On Wed, Nov 16, 2016 at 10:54 PM, Nick Coghlan <[email protected]> wrote: > On 19 July 2016 at 09:04, Matthew Brett <[email protected]> wrote: >> On Mon, Jul 18, 2016 at 11:58 PM, Nathaniel Smith <[email protected]> wrote: >>> On Mon, Jul 18, 2016 at 3:43 PM, Matthew Brett <[email protected]> >>> wrote: >>>> What to do about manylinux? I guess we need to have a pre-release >>>> Python built on the docker image. >>> >>> The problem here is that the 3.6 ABI will not be finalized until >>> 3.6-final is actually released -- any wheels built on 3.6-prereleases >>> could potentially segfault or whatever with the 3.6-final release. >>> Hopefully this won't happen very often in practice, esp. for the later >>> prereleases like the actual release candidates, but in principle it >>> could happen. (For 3.5, the "final rc" was rc3... until they found a >>> nasty problem with how they were building extension modules on >>> Windows, which forced a last minute rc4 [1].) >>> >>> I agree that it would be really good to improve the UX for wheels on >>> new Python releases, but I think it will require some discussion with >>> the Python release managers (and possibly distutils-sig, in case we >>> need finer grained Python version tags than just "3.6"). >>> >>> Definitely no-one should be uploading 3.6.0a3 wheels to PyPI :-) >> >> OK - good to know. I think we do need a solution of some sort. I'm >> guessing that people are starting to rely on wheels already, and they >> aren't going to be happy when everything breaks down for a few weeks >> after a new Python release. > > Resurrecting an old thread: this just came up on python-dev in the > context of ABI changes between alpha 3 and beta 3, and I've proposed > declaring the public ABI locked as part of the upcoming beta 4 release > (which is 3 weeks before the planned final release, while there's only > a single week planned between the first RC and the final release) to > give folks that want to pre-publish Python 3.6 wheel files more of an > opportunity to do so.
This just came up over at https://github.com/pypa/manylinux/issues/82 Can we depend on the current Python 3.6.0rc1 having the same ABI as the final release? And therefore start building 3.6 wheels with it? Thanks for thinking about this, Matthew _______________________________________________ Wheel-builders mailing list [email protected] https://mail.python.org/mailman/listinfo/wheel-builders
