[Python-Dev] [Python-checkins] r84562 - in python/branches/py3k: Doc/library/io.rst Lib/_pyio.py Lib/test/test_memoryio.py Misc/NEWS Modules/_io/_iomodule.c Modules/_io/_iomodule.h Modules/_io/bytesio.c (original) (raw)
Nick Coghlan ncoghlan at gmail.com
Wed Sep 8 00:09:13 CEST 2010
- Previous message: [Python-Dev] [Python-checkins] r84562 - in python/branches/py3k: Doc/library/io.rst Lib/_pyio.py Lib/test/test_memoryio.py Misc/NEWS Modules/_io/_iomodule.c Modules/_io/_iomodule.h Modules/_io/bytesio.c
- Next message: [Python-Dev] Volunteer help with porting
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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
- Previous message: [Python-Dev] [Python-checkins] r84562 - in python/branches/py3k: Doc/library/io.rst Lib/_pyio.py Lib/test/test_memoryio.py Misc/NEWS Modules/_io/_iomodule.c Modules/_io/_iomodule.h Modules/_io/bytesio.c
- Next message: [Python-Dev] Volunteer help with porting
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]