[issue11798] Test cases not garbage collected after run

2013-08-28 Thread Matt McClure
Matt McClure added the comment: This might fix it (untested): diff -r d748d7020192 Lib/test/test_doctest.py --- a/Lib/test/test_doctest.py Sat Aug 03 10:09:25 2013 -0400 +++ b/Lib/test/test_doctest.py Wed Aug 28 15:35:58 2013 -0400 @@ -2329,6 +2329,8 @@ Now, when we run the test

[issue11798] Test cases not garbage collected after run

2013-08-27 Thread Matt McClure
Matt McClure added the comment: Andrew, I signed the agreement as matthewlmcclure and as matthewlmcclure-gmail. Is there any way I can merge those two user accounts? I believe the original patch was Tom Wardill's. I just updated his patch. -- nosy: +matthewlmc

[issue11798] Test cases not garbage collected after run

2013-08-27 Thread Matt McClure
Matt McClure added the comment: Andrew, I didn't understand your message. Are you asking me to change the patch somehow? Or asking Michael to review and apply it? Best, Matt -- ___ Python tracker <http://bugs.python.org/is

[issue11798] Test cases not garbage collected after run

2013-08-04 Thread Matt McClure
Changes by Matt McClure : Added file: http://bugs.python.org/file31154/11798-20130803-matthewlmcclure.patch ___ Python tracker <http://bugs.python.org/issue11

[issue11798] Test cases not garbage collected after run

2013-08-04 Thread Matt McClure
Matt McClure added the comment: Michael Foord voidspace.org.uk> writes: > On 2 Aug 2013, at 19:19, Antoine Pitrou pitrou.net> wrote: > > The patch is basically ready for commit, except for a possible doc > > addition, no? > > Looks to be the case, reading t

[issue4943] trace.CoverageResults.write_results can't write results file for modules loaded by __path__ manipulation

2009-01-13 Thread Matt McClure
Matt McClure added the comment: The attached patch replaces the offending colon with a period. -- keywords: +patch Added file: http://bugs.python.org/file12735/tracebug.patch ___ Python tracker <http://bugs.python.org/issue4

[issue4943] trace.CoverageResults.write_results can't write results file for modules loaded by __path__ manipulation

2009-01-13 Thread Matt McClure
New submission from Matt McClure : The function trace.CoverageResults.write_results() can't write coverage results on Windows for modules loaded by using the __path__ feature of PEP 302. For example, Bazaar uses the __path__ feature to load plugins from directories specified b