<br><br><div class="gmail_quote">On Fri, Feb 10, 2012 at 16:29, Tres Seaver <span dir="ltr"><<a href="mailto:tseaver@palladion.com">tseaver@palladion.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<div class="im"><br>
On 02/10/2012 03:38 PM, Brett Cannon wrote:<br>
> Changes in any fashion to the directory. Do filesystems atomically<br>
> update the mtime of a directory when they commit a change? Otherwise<br>
> we have a potential race condition.<br>
<br>
</div>Hmm, maybe I misundersand you. In POSIX land, the only thing which<br>
changes the mtime of a directory is linking / unlinking / renaming a<br>
file: changes to individual files aren't detectable by examining their<br>
containing directory's stat().<br></blockquote><div><br></div><div>Individual file changes are not important; either the module is already in sys.modules so no attempt is made to detect a change or it hasn't been loaded and so it will have to be read regardless. All I'm asking is whether filesystems typically update the filesystem for a e.g. file deletion atomically with the mtime for the containing directory or not. </div>
</div>