[Python-Dev] __file__ and bytecode-only

Barry Warsaw barry at python.org
Mon Mar 15 16:16:54 CET 2010

On Mar 14, 2010, at 12:17 AM, Nick Coghlan wrote:

>Hmm - methinks the PEP actually needs to talk explicitly about the
>py_compile and compileall modules. These compile the files directly
>rather than using the import system's side-effect, so they'll need to
>understand the intricacies of the new system.

Good point.  I'll add this to the PEP.

>While it's probably OK if the import side-effects only create files
>using the new scheme, the standard library modules will likely need to
>support both schemes (although I'm not sure if "same as import system"
>or "same as Python 3.1" make more sense as the default semantics -
>probably the former).

I don't understand this point.

compileall probably /could/ be extended to understand bytecode-only
(i.e. legacy or <3.2) layout.  I've added that to the PEP too.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/python-dev/attachments/20100315/514c798e/attachment.pgp>

More information about the Python-Dev mailing list