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/2006-April/063728.html below:

[Python-Dev] [Python-checkins] r45334 - python/trunk/Lib/test/leakers/test_gen1.py python/trunk/Lib/test/leakers/test_generator_cycle.py python/trunk/Lib/test/leakers/test_tee.py

[Python-Dev] [Python-checkins] r45334 - python/trunk/Lib/test/leakers/test_gen1.py python/trunk/Lib/test/leakers/test_generator_cycle.py python/trunk/Lib/test/leakers/test_tee.py [Python-Dev] [Python-checkins] r45334 - python/trunk/Lib/test/leakers/test_gen1.py python/trunk/Lib/test/leakers/test_generator_cycle.py python/trunk/Lib/test/leakers/test_tee.pyNeal Norwitz nnorwitz at gmail.com
Fri Apr 14 08:40:33 CEST 2006
On 4/13/06, Tim Peters <tim.peters at gmail.com> wrote:
>
> Rather than delete a leak test, perhaps we could simply move it into a
> new old-leaking-tests subdirectory?  Likewise for crash tests.  When
> the bug reappears, it's helfpul to have the focussed (whittled-down)
> old test that provoked it handy.

Good point.  I updated both READMEs.  Hell, one of the tests I removed
still leaked.  Who knows what I was smoking.  The removed test that
really doesn't leak was moved into test generators.  I think it was
different than all the other existing tests.

Feel free to tweak the READMEs or policy.  I agree with the intent,
however it may be implemented.

n
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