__pycache__, one more good reason to stck with Python 2?
Carl Banks
pavlovevidence at gmail.com
Wed Jan 19 14:30:36 EST 2011
More information about the Python-list mailing list
Wed Jan 19 14:30:36 EST 2011
- Previous message (by thread): __pycache__, one more good reason to stck with Python 2?
- Next message (by thread): __pycache__, one more good reason to stck with Python 2?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Jan 19, 6:42 am, Steven D'Aprano <steve +comp.lang.pyt... at pearwood.info> wrote: > But having said that, the __pycache__ idea isn't too bad. If you have > this directory structure: > > ./module.py > ./module.pyc > > and import module, the top-level .pyc file will continue to be used. Nope. PEP 3147 says it now always uses __pycache__. Carl Banks
- Previous message (by thread): __pycache__, one more good reason to stck with Python 2?
- Next message (by thread): __pycache__, one more good reason to stck with Python 2?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list