From ncoghlan at gmail.com  Wed Nov 16 22:54:38 2016
From: ncoghlan at gmail.com (Nick Coghlan)
Date: Thu, 17 Nov 2016 13:54:38 +1000
Subject: [Wheel-builders] Pre-release Python on docker image?
In-Reply-To: <CAH6Pt5p+ZG=yqBqsgFoATwsA5jtgXCT_OZaJwyeVq=kQWOX34Q@mail.gmail.com>
References: <CAH6Pt5pZrP6Ay7YKyaYGXQ8CQZVNgA8C+twL4347Aa3Zw9EKdg@mail.gmail.com>
 <CAPJVwBmpXDQm8tWONtE9JqJz9uuEKiO9huHeA4MrPypoCV4k5A@mail.gmail.com>
 <CAH6Pt5p+ZG=yqBqsgFoATwsA5jtgXCT_OZaJwyeVq=kQWOX34Q@mail.gmail.com>
Message-ID: <CADiSq7ekuUMePwP0bFepaCJSUpzqwJi_A5DLPBaHnwXKUy_P5w@mail.gmail.com>

On 19 July 2016 at 09:04, Matthew Brett <matthew.brett at gmail.com> wrote:
> On Mon, Jul 18, 2016 at 11:58 PM, Nathaniel Smith <njs at pobox.com> wrote:
>> On Mon, Jul 18, 2016 at 3:43 PM, Matthew Brett <matthew.brett at gmail.com> 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.

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia