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 belopolsky
Recipients amaury.forgeotdarc, belopolsky, brett.cannon, brian.curtin, daniel.urban, lemburg, mark.dickinson, pitrou, r.david.murray, rhettinger, techtonik, vstinner
Date 2010-06-17.19:37:56
SpamBayes Score 0.0836015
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
> I concur.  Much of PyPy code is written for a restricted subset of
> Python instead of clean, idiomatic modern Python.

Raymond, I think you misread Brett's comment the same way as I did when I first saw it.  Brett wrote "core PyPy developer", not "core CPython developer".  Of course this will go through normal patch review process and will be looked at by at least two cpython developers before it goes it.  I also agree with Brett that it would be great to get input from PyPy developers and they may see benefit from 2.7 and 3.x ports of their code.  I am just not familiar with PyPy community and will have to research how to approach them.
Date User Action Args
2010-06-17 19:37:57belopolskysetrecipients: + belopolsky, lemburg, brett.cannon, rhettinger, amaury.forgeotdarc, mark.dickinson, pitrou, vstinner, techtonik, r.david.murray, brian.curtin, daniel.urban
2010-06-17 19:37:57belopolskysetmessageid: <>
2010-06-17 19:37:56belopolskylinkissue7989 messages
2010-06-17 19:37:56belopolskycreate