RetroSearch Browse

Sat Feb 25 17:55:32 CET 2012 · https://mail.python.org/pipermail/python-dev/2012-February/116826.html

On Fri, 24 Feb 2012 19:23:36 +0100
Georg Brandl <g.brandl at gmx.net> wrote:
> 
> > I also think the branches and releases management should be even
> > simpler:
> > 
> > - 2.7: as today
> > - 3.3: bug fixes + stdlib enhancements
> > - default: language enhancements / ABI-breaking changes
> > 
> > Every 6 months, a new stdlib + bugfix release would be cut (3.3.1,
> > 3.3.2, etc.), while language enhancement releases (3.4, 3.5...) would
> > still happen every 18 months.
> 
> Sorry, I don't think that's feasible at all.  For one, it removes the
> possibility to target a stable set of features for a longer time.

Why does it? You can target the 3.3.0 set of features and be
(reasonably) confident that your code will still work with 3.3.1.

Regards

Antoine.

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2012-February/116826.html below:

Faster evolution of the Python Standard Library