[Python-Dev] Preserving the definition order of class namespaces.
ncoghlan at gmail.com
Wed May 27 10:34:29 CEST 2015
On 27 May 2015 18:18, "Antoine Pitrou" <solipsis at pitrou.net> wrote:
> On Mon, 25 May 2015 17:30:02 -0700
> Larry Hastings <larry at hastings.org> wrote:
> > So, in all three cases it's work that's been under development for a
> > while. These people did this work out of the kindness of their hearts,
> > to make Python better. As a community we want to encourage that and
> > make sure these developers know we appreciate their efforts. These
> > people would be happier if the work shipped in 3.5 as opposed to 3.6 so
> > it got into user's hands sooner.
> I second that sentiment. But it strikes me that we're doing this
> because our release frequency is completely inadapted. If we had
> feature releases, say, every 6 or 9 months, the problem wouldn't really
> exist in the first place. Exceptions granted by the RM only tackle a
> very small portion of the problem, because the long delay before an
> accepted patch being in an official release *still* frustrates everyone,
> and the unpredictability of exceptions only makes things *more*
> frustrating for most players.
I'd actually like to pursue a more nuanced view of what's permitted in
maintenance releases, based on a combination of the language moratorium
PEP, and an approach inspired by PEP 466, requiring that every feature
added in a maintenance release be detectable through an attribute check on
a module (with corresponding support in dependency checking tools).
The problem with simply speeding up the release cycle without constraining
the interim releases in some way is that it creates significant pain for
alternate implementations and for downstream redistributors (many of whom
are still dealing with the fallout of the Python 3 transition).
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Python-Dev