A RetroSearch Logo

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

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/2005-March/051942.html below:

[Python-Dev] rationale for the no-new-features approach

[Python-Dev] rationale for the no-new-features approach [Python-Dev] rationale for the no-new-features approachGuido van Rossum gvanrossum at gmail.com
Wed Mar 9 17:01:09 CET 2005
On Wed, 09 Mar 2005 10:38:12 -0500, Jim Fulton <jim at zope.com> wrote:
> +1 (wish * could say +sys.maxint).

Anthony gets my +1 too, which then adds up to sys.maxint. :-)

> To emphasize:
> 
> - We want people to update to bug fix releases quickly. For people
>    to do that, they need to know the risk of breakage is low.  Reducing the
>    scope of the release is important for that.
> 
> - Python has gotten much better at this than it used to be.  I remember the
>    days when major features in 3rd-dot releases caused major headaches for us.

For those who only remember bool(), Python 1.5.2 was probably the
worst offender here (it had nothing to do with 1.5.1). Mea culpa
etcetera.

-- 
--Guido van Rossum (home page: http://www.python.org/~guido/)
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4