[issue17315] test_posixpath doesn't clean up after itself

Chris Jerdonek added the comment: Thanks, I confirmed the fix. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe

[issue17315] test_posixpath 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 versions: +Python 2.7, Python 3.2, Python 3.3 ___ Python tracker

[issue17315] test_posixpath doesn't clean up after itself

Roundup Robot added the comment: New changeset ed3ca7298055 by Ezio Melotti in branch '2.7': #17315: unlink a file that test_posixpath was leaving around. http://hg.python.org/cpython/rev/ed3ca7298055 New changeset c65e98ce1a05 by Ezio Melotti in branch '3.2': #17315: unlink a file that test_pos

[issue17315] test_posixpath doesn't clean up after itself

Chris Jerdonek added the comment: The file gets created in the current working directory. You won't see it when using regrtest since regrtest creates and then deletes a temp working directory. To see it easier, try running instead: ./python.exe -m unittest test.test_posixpath -- ___

[issue17315] test_posixpath 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 ___ __

[issue17315] test_posixpath doesn't clean up after itself

New submission from Chris Jerdonek: test_posixpath leaves behind a file of the following form when running on Mac OS X: lrwxr-xr-x @test_17700_tmpa -> @test_17700_tmpa/b I'm not sure which test it is or which other versions are affected. -- components: Tests messages: 183178 nosy: chr