On Wed, Sep 8, 2010 at 3:39 AM, Benjamin Peterson <benjamin at python.org> wrote: > 2010/9/7 Nick Coghlan <ncoghlan at gmail.com>: >> I've raised an RFE (http://bugs.python.org/issue9789) to point out >> that the need for that GC collect call in there to make the test >> portable to other implementations is rather ugly > > Why? You're testing garbage collection, so you should call garbage collection. Having that test *as well* as a specific release test (to check implicit as well as explicit release) is a different story (we do that for generators, files and assorted other things). Having forced GC invocation be the only way to do explicit release is the part I found ugly. Cheers, Nick. -- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
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