[issue17908] Unittest runner needs an option to call gc.collect() after each test

STINNER Victor added the comment: This issue is no newcomer friendly, I remove the "easy" keyword. -- keywords: -easy versions: +Python 3.9 -Python 3.5 ___ Python tracker

[issue17908] Unittest runner needs an option to call gc.collect() after each test

Adam added the comment: Any comments about this proposed patch? -- ___ Python tracker ___ ___

[issue17908] Unittest runner needs an option to call gc.collect() after each test

STINNER Victor added the comment: While I like the idea of adding an option to force a garbage collection after running each time, I don't like how unittest is growing :-( It looks more and more like regrtest and I hate regrtest (I reworked its code recently to create a less ugly

[issue17908] Unittest runner needs an option to call gc.collect() after each test

STINNER Victor added the comment: Well, maybe we can add yet another parameter to all unittest classes (push this change), but IMHO someone must rework the unittest API to make it more extensible instead of adding more and more stuff in the base API. --

[issue17908] Unittest runner needs an option to call gc.collect() after each test

Changes by Ankit Baruah : -- nosy: +@nkit ___ Python tracker ___ ___

[issue17908] Unittest runner needs an option to call gc.collect() after each test

Changes by Raymond Hettinger : -- nosy: +haypo ___ Python tracker ___ ___

[issue17908] Unittest runner needs an option to call gc.collect() after each test

Robert Collins added the comment: say, something to run a test until failure, or to watch for reference leaks, or to run tests in multiple processes :-)) I think a few complimentary things. unittest extensability currently requires a new CLI entry point for each thing. I'd like to fix that.

[issue17908] Unittest runner needs an option to call gc.collect() after each test

Antoine Pitrou added the comment: Le 28/04/2015 21:00, Robert Collins a écrit : So you could add this as a hook to the loader (decorate each test with some new thing) and a CLI option to use that hook for a gc collect call. Can I take this as meaning you're not opposed to adding other

[issue17908] Unittest runner needs an option to call gc.collect() after each test

Guido van Rossum added the comment: It's trivial to add to a single test or even a single TestCase subclass, yes. The use case is more that you have a ton of tests and you suspect there's a problem due to GC. Being able to call gc.collect() after each test through the flip of a flag would be

[issue17908] Unittest runner needs an option to call gc.collect() after each test

Antoine Pitrou added the comment: I still think that it's something that people can trivially implement and that has no place in the standard unittest package. -- versions: +Python 3.5 -Python 3.4 ___ Python tracker rep...@bugs.python.org

[issue17908] Unittest runner needs an option to call gc.collect() after each test

Serhiy Storchaka added the comment: See also issue23839 where proposed not only call gc.collect(), but clear all caches in test.regrtest. -- nosy: +serhiy.storchaka ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17908

[issue17908] Unittest runner needs an option to call gc.collect() after each test

Robert Collins added the comment: I'm going to disagree with michael and antoine here. The *internals* should be clean and pluggable for sure, but this is actually a pretty common thing to try, so there's no reason to force it to only be done by external plugins. Right now the way to plug

[issue17908] Unittest runner needs an option to call gc.collect() after each test

Adam added the comment: Is this enhancement still open? I've run into this problem previously, and would be more than happy to implement this feature. -- nosy: +azsorkin ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17908

[issue17908] Unittest runner needs an option to call gc.collect() after each test

Changes by Ned Deily n...@acm.org: -- nosy: +rbcollins ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17908 ___ ___ Python-bugs-list mailing list

[issue17908] Unittest runner needs an option to call gc.collect() after each test

Guido van Rossum added the comment: Does the cpython test runner have this? Might be nice there. Not sure if the default test runner is something to extend at this point. Eveybody is using py.test anyway... On Monday, April 27, 2015, Ned Deily rep...@bugs.python.org wrote: Changes by Ned

[issue17908] Unittest runner needs an option to call gc.collect() after each test

Changes by Demian Brecht demianbre...@gmail.com: -- nosy: -demian.brecht ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17908 ___ ___

[issue17908] Unittest runner needs an option to call gc.collect() after each test

Changes by Andrew Svetlov andrew.svet...@gmail.com: -- nosy: +asvetlov ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17908 ___ ___

[issue17908] Unittest runner needs an option to call gc.collect() after each test

Changes by Demian Brecht demianbre...@gmail.com: -- nosy: +dbrecht ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17908 ___ ___ Python-bugs-list

[issue17908] Unittest runner needs an option to call gc.collect() after each test

Changes by Phil Connell pconn...@gmail.com: -- nosy: +pconnell ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17908 ___ ___ Python-bugs-list

[issue17908] Unittest runner needs an option to call gc.collect() after each test

Antoine Pitrou added the comment: TBH I would *love* for there to be a standardized way to extend the command line options! If it existed I would help myself. As it is, that's way to complicated. (Then again, most customizations to the default test runner are too complicated IMO. :-) +1.

[issue17908] Unittest runner needs an option to call gc.collect() after each test

Michael Foord added the comment: The default test runner is quite horrible. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17908 ___ ___

[issue17908] Unittest runner needs an option to call gc.collect() after each test

Michael Foord added the comment: I'm afraid I'm inclined to agree with Antoine. This seems a relatively specialised problem and I'd expect to see it solved in the test system rather than in unittest itself. One solution, and something I'd like to see, is a way for test systems to extend the

[issue17908] Unittest runner needs an option to call gc.collect() after each test

Guido van Rossum added the comment: TBH I would *love* for there to be a standardized way to extend the command line options! If it existed I would help myself. As it is, that's way to complicated. (Then again, most customizations to the default test runner are too complicated IMO. :-)

[issue17908] Unittest runner needs an option to call gc.collect() after each test

Changes by Giampaolo Rodola' g.rod...@gmail.com: -- nosy: +giampaolo.rodola ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17908 ___ ___

[issue17908] Unittest runner needs an option to call gc.collect() after each test

Antoine Pitrou added the comment: OTOH it's a useful option to have in case you're tracking down something that happens (or doesn't happen) when an object is collected IMO this is a good reason to implement your specific tearDown method (or call addCleanup if you prefer), possibly in a

[issue17908] Unittest runner needs an option to call gc.collect() after each test

Guido van Rossum added the comment: On Sun, May 5, 2013 at 4:29 AM, Antoine Pitrou rep...@bugs.python.org wrote: Antoine Pitrou added the comment: OTOH it's a useful option to have in case you're tracking down something that happens (or doesn't happen) when an object is collected IMO this

[issue17908] Unittest runner needs an option to call gc.collect() after each test

New submission from Guido van Rossum: It would be nice if there was a command-line option to tell the test runner to call gc.collect() after each test. See https://groups.google.com/d/msg/python-tulip/tstjvOQowIU/IRihc8NCHZUJ -- Glyph points out that always doing this is problematic because

[issue17908] Unittest runner needs an option to call gc.collect() after each test

Ezio Melotti added the comment: See also #17534. -- nosy: +ezio.melotti, michael.foord stage: - needs patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17908 ___