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 rhettinger
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:12:33
SpamBayes Score 0.0298315
Marked as misclassified No
Message-id <1276801955.46.0.336440772302.issue7989@psf.upfronthosting.co.za>
In-reply-to
Content
> 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.

Also, this should not be marked as high priority.  It may be a personal priority for you, but it is by no means essential for Py3.2 or something that other developers should prioritize higher than other tasks like fixing bugs.
History
Date User Action Args
2010-06-17 19:12:35rhettingersetrecipients: + rhettinger, lemburg, brett.cannon, amaury.forgeotdarc, mark.dickinson, belopolsky, pitrou, vstinner, techtonik, r.david.murray, brian.curtin, daniel.urban
2010-06-17 19:12:35rhettingersetmessageid: <1276801955.46.0.336440772302.issue7989@psf.upfronthosting.co.za>
2010-06-17 19:12:34rhettingerlinkissue7989 messages
2010-06-17 19:12:33rhettingercreate