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 Jim.Jewett
Recipients Jim.Jewett, brett.cannon, eric.snow, ncoghlan, pitrou
Date 2012-02-27.00:46:13
SpamBayes Score 6.9948787e-06
Marked as misclassified No
Message-id <1330303574.01.0.997870132266.issue14067@psf.upfronthosting.co.za>
In-reply-to
Content
As long as the interpreter knows about about files that *it* wrote, no repeat checks during startup seems utterly reasonable; sneaking in a new or changed file is inherently a race condition.

I think it would also be reasonable for general use, so long as there was also a way to say "for this particular directory, always check".
History
Date User Action Args
2012-02-27 00:46:14Jim.Jewettsetrecipients: + Jim.Jewett, brett.cannon, ncoghlan, pitrou, eric.snow
2012-02-27 00:46:14Jim.Jewettsetmessageid: <1330303574.01.0.997870132266.issue14067@psf.upfronthosting.co.za>
2012-02-27 00:46:13Jim.Jewettlinkissue14067 messages
2012-02-27 00:46:13Jim.Jewettcreate