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

Showing content from https://mail.python.org/pipermail/python-dev/2008-October/083001.html below:

[Python-Dev] backporting tests [was: [Python-checkins] r66863

• Previous message: [Python-Dev] Summary of Python tracker Issues
• Next message: [Python-Dev] 2 modifications in robotparser.py
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

In http://mail.python.org/pipermail/python-dev/2008-October/082994.html
Martin v. Löwis wrote:

> So 2.6.0 will contain a lot of tests that have never been tested in
> a wide variety of systems. Some are incorrect, and get fixed in 2.6.1,
> and stay fixed afterwards. This is completely different from somebody
> introducing a new test in 2.6.4. It means that there are more failures
> in a maintenance release, not less as in the first case.

If 2.6.1 has some (possibly accidental, but exposed to the users)
behavior that is not a clear bug, it should be kept through 2.6.x.
You may well want to change it in 2.7, but not in 2.6.4.  Adding a
test to 2.6.2 ensures that the behavior will not silently disappear
because of an unrelated bugfix in 2.6.3.

-jJ

• Previous message: [Python-Dev] Summary of Python tracker Issues
• Next message: [Python-Dev] 2 modifications in robotparser.py
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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