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 | benjamin.peterson |
|---|---|
| Recipients | Trundle, benjamin.peterson, daniel.urban, eric.araujo, ncoghlan, pitrou, rhettinger |
| Date | 2011年04月05日.14:12:58 |
| SpamBayes Score | 0.0018806625 |
| Marked as misclassified | No |
| Message-id | <1302012779.37.0.446230135571.issue10977@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I find this extremely ugly. The correct way to handle this is to use the generic methods themselves. Really, the type-specific names should only be used when you have just created the type or done PyXXX_CheckExact() yourself on it. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2011年04月05日 14:12:59 | benjamin.peterson | set | recipients: + benjamin.peterson, rhettinger, ncoghlan, pitrou, eric.araujo, Trundle, daniel.urban |
| 2011年04月05日 14:12:59 | benjamin.peterson | set | messageid: <1302012779.37.0.446230135571.issue10977@psf.upfronthosting.co.za> |
| 2011年04月05日 14:12:58 | benjamin.peterson | link | issue10977 messages |
| 2011年04月05日 14:12:58 | benjamin.peterson | create | |