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 erik.bray
Recipients brett.cannon, erik.bray, pitrou
Date 2013-03-01.19:51:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1362167486.73.0.923197015567.issue17330@psf.upfronthosting.co.za>
In-reply-to
Content
Why should modifying the file in place be expected to do anything with respect to the directory cache?  If that module has already been imported then modifying it should not require the cache to be invalidated.

If the file is modified *before* it's imported that's still irrelevant because that means the file exists in the directory and will be included in the cache when it gets generated.

Relying on invalidate_caches() is a workaround because it's not even necessary on better filesystems--the existing behavior already leads to hard to find bugs.
History
Date User Action Args
2013-03-01 19:51:26erik.braysetrecipients: + erik.bray, brett.cannon, pitrou
2013-03-01 19:51:26erik.braysetmessageid: <1362167486.73.0.923197015567.issue17330@psf.upfronthosting.co.za>
2013-03-01 19:51:26erik.braylinkissue17330 messages
2013-03-01 19:51:26erik.braycreate