Reid Kleckner wrote:
On Sun, Jan 31, 2010 at 8:34 AM, Nick Coghlan <ncogh...@gmail.com> wrote:
That still leaves the question of what to do with __file__ (for which
even the solution in the PEP isn't particularly clean). Perhaps the
thing to do there is to have __file__ always point to the source file
and introduce a __file_cached__ that points to the bytecompiled file on
disk (set to None if it doesn't exist, as may be the case for __main__
or due to writing of bytecode files being disabled).
+1 for this, it seems to be what most people want anyway, given the
code that munges the .pyc back to the .py. I bet this change would
break very little code.
Isn't .pyc just an optimisation for performance reasons? If so, then the
user is more interested in the .py file.
_______________________________________________
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
