This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author brett.cannon
Recipients Arfrever, Marc.Abramowitz, Ronan.Lamy, brett.cannon, jcea, ncoghlan
Date 2012-08-12.00:39:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1344731969.93.0.527995857685.issue15031@psf.upfronthosting.co.za>
In-reply-to
Content
So the more I think about this, the more I'm willing to do this in Python 3.4. First, though, the docs would need to be updated in importlib to distinguish between bytecode and byte-compiled files.

From there, I think importlib.abc.SourceLoader.parse_byte_compiled_file(data) could exist. It would be a classmethod so people can call it directly if they really want. It would verify the magic number, and if that's good, return a dict that can be directly compared against what path_stats() returns plus the bytecode for the module. This should properly shield the format of bytecode from users while still providing an API people can rely on.
History
Date User Action Args
2012-08-12 00:39:31brett.cannonsetrecipients: + brett.cannon, jcea, ncoghlan, Arfrever, Marc.Abramowitz, Ronan.Lamy
2012-08-12 00:39:29brett.cannonsetmessageid: <1344731969.93.0.527995857685.issue15031@psf.upfronthosting.co.za>
2012-08-12 00:39:29brett.cannonlinkissue15031 messages
2012-08-12 00:39:26brett.cannoncreate