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/2009-June/090156.html below:

[Python-Dev] draft pep: backwards compatibility

[Python-Dev] draft pep: backwards compatibility [Python-Dev] draft pep: backwards compatibilityCollin Winter collinw at gmail.com
Sat Jun 20 19:49:59 CEST 2009
On Thu, Jun 18, 2009 at 7:17 PM, Benjamin Peterson<benjamin at python.org> wrote:
[snip]
> Backwards Compatibility Rules
> =============================
>
> This policy applys to all public APIs.  These include the C-API, the standard
> library, and the core language including syntax and operation as defined by the
> reference manual.
>
> This is the basic policy for backwards compatibility:
>
> * The behavior of an API *must* not change between any two consecutive releases.

Is this intended to include performance changes? Clearly no-one will
complain if things simply get faster, but I'm thinking about cases
where, say, a function runs in half the time but uses double the
memory (or vice versa).

Collin
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