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 Ronan.Lamy
Recipients Ronan.Lamy, brett.cannon
Date 2012-06-07.18:29:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1339093745.36.0.217954238906.issue15030@psf.upfronthosting.co.za>
In-reply-to
Content
PyPycLoader can't read or write .pyc files created by the core import machinery. I'm attaching a failing test case demonstrating the issue: if you import a .py file using standard mechanisms, thus creating a .pyc, and then (in a separate process, say) attempt to make use of that cached file with PyPycLoader, the import fails with 'ValueError: bad marshal data (unknown type code)'.

It looks like that there has been a change in the binary format of .pyc files but PyPycLoader wasn't updated.
History
Date User Action Args
2012-06-07 18:29:05Ronan.Lamysetrecipients: + Ronan.Lamy, brett.cannon
2012-06-07 18:29:05Ronan.Lamysetmessageid: <1339093745.36.0.217954238906.issue15030@psf.upfronthosting.co.za>
2012-06-07 18:29:04Ronan.Lamylinkissue15030 messages
2012-06-07 18:29:04Ronan.Lamycreate