A RetroSearch Logo

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

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2005-September/055927.html below:

[Python-Dev] [Python-checkins] python/dist/src/Lib/test test_re.py, 1.45.6.3, 1.45.6.4

[Python-Dev] [Python-checkins] python/dist/src/Lib/test test_re.py, 1.45.6.3, 1.45.6.4Jim Jewett jimjjewett at gmail.com
Thu Sep 1 01:56:04 CEST 2005
On 8/31/05, akuchling at users.sourceforge.net
<akuchling at users.sourceforge.net> wrote:
> Log Message:
> ... the tests aren't run by default because I wanted to minimize
> upheaval to the 2.3 test suite


What is the reasoning behind this?

It seems to me that if a (passing) test is being added, maintenance releases 
are the *most* important places to run them.

On the other hand, I've also seen Raymond check (regression) tests into
only development, so it seems to be a conscious choice.  *I* just don't 
understand it.

-jJ
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