[Python-Dev] time-based releases (was Re: Preserving the definition order of class namespaces.)

Antoine Pitrou solipsis at pitrou.net
Fri May 29 01:15:36 CEST 2015

On Thu, 28 May 2015 08:48:11 +1000
Nick Coghlan <ncoghlan at gmail.com> wrote:
> I just remembered one of the biggest causes of pain: Windows binaries for
> projects that aren't using the stable ABI. It used to regularly take 6+
> months for the Windows ecosystem to catch up after each 2.x release.

You're right, compatibility of C extension builds under Windows is
pretty much the killer.

> After all, the real difference between the alphas and the final releases
> isn't about anything *we* do, it's about the testing *other people* do that
> picks up gaps in our test coverage. A gated trunk makes it more feasible
> for other projects to do continuous integration against it.

Long ago (before I became a core developer) we had "community
buildbots" for that. They didn't receive any attention or maintenance
from third-party projects.



More information about the Python-Dev mailing list