[Python-Dev] [compatibility-sig] making sure importlib.machinery.SourceLoader doesn't throw an exception if bytecode is not supported by a VM (original) (raw)
Brett Cannon brett at python.org
Tue Jun 12 18:47:39 CEST 2012
- Previous message: [Python-Dev] [compatibility-sig] making sure importlib.machinery.SourceLoader doesn't throw an exception if bytecode is not supported by a VM
- Next message: [Python-Dev] [compatibility-sig] making sure importlib.machinery.SourceLoader doesn't throw an exception if bytecode is not supported by a VM
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Tue, Jun 12, 2012 at 12:38 PM, Alex Gaynor <alex.gaynor at gmail.com> wrote:
For PyPy: I'm not an expert in our import, but from looking at the source
1) imp.cachefromsource is unimplemented, it's an AttributeError.
Well, you will have it come Python 3.3 one way or another. =)
2) sys.dontwritebytecode is always false, we don't respect that flag (we really should IMO, but it's not a high priority for me, or anyone else apparently)
But doesn't PyPy read and write .pyc files ( http://doc.pypy.org/en/latest/config/objspace.usepycfiles.html suggests you do)? So I would assume you are not affected by this. Jython and IronPython, though, would be (I think). -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20120612/4b9881d7/attachment.html>
- Previous message: [Python-Dev] [compatibility-sig] making sure importlib.machinery.SourceLoader doesn't throw an exception if bytecode is not supported by a VM
- Next message: [Python-Dev] [compatibility-sig] making sure importlib.machinery.SourceLoader doesn't throw an exception if bytecode is not supported by a VM
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]