"Martin v. Löwis" wrote: > Greg Ewing schrieb: >> I think I'd be happy with having to do that explicitly. >> I expect the vast majority of Python programs don't >> need to track changes to the set of importable modules >> during execution. The exceptions would be things like >> IDEs, and they could do a cache flush before reloading >> a module, etc. > > That would be a change in behavior, of course. > > Currently, you can put a file on disk and import it > immediately; that will stop working. I'm pretty sure > that there are a number of applications that rely > on this specific detail of the current implementation > (and not only IDEs).
Would it be reasonable to always do a stat() on the directory, reloading if there's been a change? Would this be reliable across platforms? Tim Delaney _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
