[Python-Dev] __file__ and bytecode-only
R. David Murray
rdmurray at bitdance.com
Sun Mar 14 17:46:11 CET 2010
On Sun, 14 Mar 2010 12:59:50 -0000, Jon Ribbens <jon+python-dev at unequivocal.co.uk> wrote:
> On Fri, Mar 12, 2010 at 05:56:57PM -0500, Barry Warsaw wrote:
> > Nope, sorry I should have been clearer.
> >
> > *creation* is the key here. As per BDFL pronouncement, we'll support reading
> > pyc-only modules just like we do today. This is in PEP 3147. We won't
> > support creating them though.
> >
> > BTW, I'm actually starting to work on the implementation now, so if you want
> > to play along:
> >
> > % bzr branch lp:~barry/python/pep3147
>
> Sorry if I missed it, but why on earth is the bytecode directory
> __pycache__ and not .pycache? (Or indeed anything else that starts
> with a '.') Surely this is a classic ideal use case for a "hidden"
> directory?
You did miss it. Perhaps a link to the discussion should be added to
the PEP, or a summary of it. If I remember correctly the BDFL even
weighed in on this point.
--
R. David Murray www.bitdance.com
More information about the Python-Dev
mailing list