[issue17312] test_aifc doesn't clean up after itself

Chris Jerdonek added the comment: Thanks. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python

[issue17312] test_aifc doesn't clean up after itself

Ezio Melotti added the comment: Should be fixed now. -- assignee: -> ezio.melotti resolution: -> fixed stage: needs patch -> committed/rejected status: open -> closed ___ Python tracker __

[issue17312] test_aifc doesn't clean up after itself

Roundup Robot added the comment: New changeset 10909360a11d by Ezio Melotti in branch 'default': #17312: unlink a file that test_aifc was leaving around. http://hg.python.org/cpython/rev/10909360a11d -- nosy: +python-dev ___ Python tracker

[issue17312] test_aifc doesn't clean up after itself

Chris Jerdonek added the comment: Similar to as I stated in issue 17315, you won't see it when using regrtest since regrtest creates and then deletes a temp working directory. The file gets created and is left behind in the current working directory. Try running using unittest, e.g. ./python

[issue17312] test_aifc doesn't clean up after itself

Ezio Melotti added the comment: On Linux it looks OK. Does it always happen? Where is the file located? -- nosy: +ezio.melotti ___ Python tracker ___ __

[issue17312] test_aifc doesn't clean up after itself

Changes by Chris Jerdonek : -- components: +Tests ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.p

[issue17312] test_aifc doesn't clean up after itself

New submission from Chris Jerdonek: test_aifc's AIFCLowLevelTest.test_write_aiff_by_extension() leaves a test file behind. I'm not sure what other versions are affected. -- keywords: easy messages: 183175 nosy: chris.jerdonek, r.david.murray priority: normal severity: normal stage: nee