[Python-Dev] [compatibility-sig] making sure importlib.machinery.SourceLoader doesn't throw an exception if bytecode is not supported by a VM

Amaury Forgeot d'Arc amauryfa at gmail.com
Tue Jun 12 19:02:02 CEST 2012


2012/6/12 Alex Gaynor <alex.gaynor at gmail.com>

>
>
> On Tue, Jun 12, 2012 at 11:47 AM, Brett Cannon <brett at python.org> wrote:
>
>>
>>
>> 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.cache_from_source is unimplemented, it's an AttributeError.
>>>
>>
>> Well, you will have it come Python 3.3 one way or another. =)
>>
>>
>
> Sure, I'm not totally up to speed on the py3k effort.
>

It's indeed implemented in pypy's py3k branch.


>
>
>>
>>> 2) sys.dont_write_bytecode 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).
>>
>
> This is a compile time option, not a runtime option.  However, it looks
> like I lied, someone did implement it correctly, so we have the same
> behavior as CPython.


Yes, PyPy seems to respect sys.dontwritebytecode.

-- 
Amaury Forgeot d'Arc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20120612/f2eb5f4a/attachment.html>


More information about the Python-Dev mailing list