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 amaury.forgeotdarc
Recipients amaury.forgeotdarc, belopolsky, brett.cannon, brian.curtin, daniel.urban, lemburg, mark.dickinson, pitrou, r.david.murray, rhettinger, techtonik, vstinner
Date 2010-06-18.09:16:22
SpamBayes Score 0.136955
Marked as misclassified No
Message-id <>
>> One, we should not blindly pull in the PyPy code
>> without some core PyPy developer being in on this

You can count me among the PyPy developers.

> I concur.  Much of PyPy code is written for a restricted subset of
> Python instead of clean, idiomatic modern Python.

Not this part. The module is meant to be imported by the interpreter, and has no limitation (we call it "application-level" code, opposed to interpreter-level code which is translated to C and which indeed has serious constraints)
Date User Action Args
2010-06-18 09:16:25amaury.forgeotdarcsetrecipients: + amaury.forgeotdarc, lemburg, brett.cannon, rhettinger, mark.dickinson, belopolsky, pitrou, vstinner, techtonik, r.david.murray, brian.curtin, daniel.urban
2010-06-18 09:16:25amaury.forgeotdarcsetmessageid: <>
2010-06-18 09:16:22amaury.forgeotdarclinkissue7989 messages
2010-06-18 09:16:22amaury.forgeotdarccreate