This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ncoghlan
Recipients barry, brett.cannon, ncoghlan, v2m, vstinner
Date 2018-08-30.16:17:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1535645850.48.0.56676864532.issue34200@psf.upfronthosting.co.za>
In-reply-to
Content
Given that importlib is essentially just doing "listdir", it would be interesting to know how the following behaves in a tight loop on affected systems:
    
    # Write a file
    f = open(os.path.join(dirname, "testname.py"), "w")
    f.write("text\n")
    f.close()
    # Make a directory
    os.mkdir(os.path.join(dirname, "testname"))
    # List the directory
    os.listdir(dirname)

The core assumption that test_pkg is indirectly making is that the directory listing in importlib will always list both entries created by the test suite without any special care being needed at the application level.
History
Date User Action Args
2018-08-30 16:17:30ncoghlansetrecipients: + ncoghlan, barry, brett.cannon, vstinner, v2m
2018-08-30 16:17:30ncoghlansetmessageid: <1535645850.48.0.56676864532.issue34200@psf.upfronthosting.co.za>
2018-08-30 16:17:30ncoghlanlinkissue34200 messages
2018-08-30 16:17:30ncoghlancreate