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 | bfroehle |
|---|---|
| Recipients | Arfrever, amaury.forgeotdarc, bfroehle, chris.jerdonek, christopherthemagnificent, kushal.das |
| Date | 2012年10月31日.01:50:41 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1351648241.48.0.220930738329.issue16268@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Your patch looks good to me, and I can verify that it properly tests for the issue in Python 3.3. On a related note, I've found that PyType_Ready(...) isn't called for a few other core PyTypeObjects... see #16369. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2012年10月31日 01:50:41 | bfroehle | set | recipients: + bfroehle, amaury.forgeotdarc, Arfrever, christopherthemagnificent, chris.jerdonek, kushal.das |
| 2012年10月31日 01:50:41 | bfroehle | set | messageid: <1351648241.48.0.220930738329.issue16268@psf.upfronthosting.co.za> |
| 2012年10月31日 01:50:41 | bfroehle | link | issue16268 messages |
| 2012年10月31日 01:50:41 | bfroehle | create | |