Message108124
| 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月18日.18:39:35 |
| SpamBayes Score |
0.004126357 |
| Marked as misclassified |
No |
| Message-id |
<1276886377.03.0.208178978667.issue7989@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Let me just add a story to show how an alternate python implementation may be useful for users. As I was porting datetime.py to 3.x, I saw many failures from pickle tests. It was not easy to figure out what was going on because C pickle code was calling buggy Python and pdb was unable to trace the full chain of calls. To work around that, I added sys.modules['_pickle'] = None to my test run and there you go - the problem was found in minutes. I am sure that someone debugging his tzinfo implementation, for example, may find datetime.py easier to work with.
The story may be a bit self-serving, but I was against this "feature" myself, but now I see enough use that I am actually working on it.
Yes, the work is in the sandbox, but I want to have py3k working version before I announce it. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2010年06月18日 18:39:37 | belopolsky | set | recipients:
+ belopolsky, lemburg, brett.cannon, rhettinger, amaury.forgeotdarc, mark.dickinson, pitrou, vstinner, techtonik, r.david.murray, brian.curtin, daniel.urban |
| 2010年06月18日 18:39:37 | belopolsky | set | messageid: <1276886377.03.0.208178978667.issue7989@psf.upfronthosting.co.za> |
| 2010年06月18日 18:39:35 | belopolsky | link | issue7989 messages |
| 2010年06月18日 18:39:35 | belopolsky | create |
|