Message108089
| 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.13695493 |
| Marked as misclassified | No |
| Message-id | <1276852585.3.0.462870985215.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 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 datetime.py 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) |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2010-06-18 09:16:25 | amaury.forgeotdarc | set | recipients: + amaury.forgeotdarc, lemburg, brett.cannon, rhettinger, mark.dickinson, belopolsky, pitrou, vstinner, techtonik, r.david.murray, brian.curtin, daniel.urban |
| 2010-06-18 09:16:25 | amaury.forgeotdarc | set | messageid: <1276852585.3.0.462870985215.issue7989@psf.upfronthosting.co.za> |
| 2010-06-18 09:16:22 | amaury.forgeotdarc | link | issue7989 messages |
| 2010-06-18 09:16:22 | amaury.forgeotdarc | create | |