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 | belopolsky |
|---|---|
| Recipients | belopolsky, gvanrossum, ncoghlan |
| Date | 2008年03月17日.17:19:25 |
| SpamBayes Score | 0.18515259 |
| Marked as misclassified | No |
| Message-id | <1205774367.38.0.934722531282.issue868845@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I think the attached patch captures the most of what can currently be
said about <...> reprs.
I think the biggest offender in terms of inconsistency in the 2.x series
is the file object with the repr which does not even start with the name
of the type.
For 3.0, I think it is feasible to standardize on the <{type} object
['{name}'] ... at 0x{addr}> pattern. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年03月17日 17:19:27 | belopolsky | set | spambayes_score: 0.185153 -> 0.18515259 recipients: + belopolsky, gvanrossum, ncoghlan |
| 2008年03月17日 17:19:27 | belopolsky | set | spambayes_score: 0.185153 -> 0.185153 messageid: <1205774367.38.0.934722531282.issue868845@psf.upfronthosting.co.za> |
| 2008年03月17日 17:19:26 | belopolsky | link | issue868845 messages |
| 2008年03月17日 17:19:26 | belopolsky | create | |