On Feb 03, 2010, at 11:07 PM, Nick Coghlan wrote: >It's also the case that having to run Python to manage my own filesystem >would very annoying. If a dev has a broken .pyc that prevents the >affected Python build from even starting how are they meant to use the >nonfunctioning interpreter to find and delete the offending file? How is >someone meant to find and delete the .pyc files if they prefer to use a >graphical file manager over (or in conjunction with) the command line? I agree. I'd prefer to have a predictable place for the cached files, independent of having to run Python to tell you where that is. -Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 835 bytes Desc: not available URL: <http://mail.python.org/pipermail/python-dev/attachments/20100206/84d9cc9f/attachment.pgp>
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