Nick Coghlan wrote:
Ron Adam wrote:
I think I misunderstood this at first.
It looks like, while developing a python 3.2+ program, if you don't
create an empty __pycache__ directory, everything will still work, you
just won't get the .pyc files. That can be a good thing during
development because you also will not have any problems with old .pyc
files hanging around if you move or rename files.
The behaviour you described (not creating __pycache__ automatically) was
just a suggestion in this thread.
The behaviour in the actual PEP (and what will be implemented for 3.2+)
is to create __pycache__ if it is missing.
Cheers,
Nick.
OK :-)
hmmmm... unless there is a __pycache__ *file* located there first. ;-)
Not that I can think of any good reason to do that at this moment.
Ron
_______________________________________________
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
