On 7Nov 2006, at 12:20 AM, Greg Ewing wrote: > >> Also, if we do our own directory caching, the question >> is when to invalidate the cache. > > 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. Not only IDE's, also the interactive prompt. It is very convenient that you can currently install an additional module when an import fails and then try the import again (at the python prompt). Ronald -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3562 bytes Desc: not available Url : http://mail.python.org/pipermail/python-dev/attachments/20061107/9dd3183f/attachment.bin
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4