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 | ncoghlan |
|---|---|
| Recipients | amaury.forgeotdarc, benjamin.peterson, christoph, davidfraser, georg.brandl, hodgestar, lemburg, ncoghlan, pitrou |
| Date | 2008年06月11日.09:32:09 |
| SpamBayes Score | 0.0005699219 |
| Marked as misclassified | No |
| Message-id | <1213176744.02.0.830768417637.issue2517@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
As far as I am concerned, the implementation of PyObject_Unicode in object.c has a bug in it: it should NEVER be retrieving __unicode__ from the instance object. The implementation of PyObject_Format in abstract.c shows the correct way to retrieve a pseudo-slot method like __unicode__ from an arbitrary object. Line 482 in object.c is the offending line: func = PyObject_GetAttr(v, unicodestr); Fix that bug, then add a __unicode__ method back to Exception objects and you will have the best of both worlds. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年06月11日 09:32:29 | ncoghlan | set | spambayes_score: 0.000569922 -> 0.0005699219 recipients: + ncoghlan, lemburg, georg.brandl, amaury.forgeotdarc, davidfraser, pitrou, benjamin.peterson, christoph, hodgestar |
| 2008年06月11日 09:32:24 | ncoghlan | set | spambayes_score: 0.000569922 -> 0.000569922 messageid: <1213176744.02.0.830768417637.issue2517@psf.upfronthosting.co.za> |
| 2008年06月11日 09:32:22 | ncoghlan | link | issue2517 messages |
| 2008年06月11日 09:32:19 | ncoghlan | create | |