Message222939
| Author |
serhiy.storchaka |
| Recipients |
Claudiu.Popa, benjamin.peterson, hynek, josh.r, pitrou, rhettinger, serhiy.storchaka, stutzbach |
| Date |
2014年07月13日.15:24:09 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1405265049.54.0.251652301408.issue21861@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
I now see that this issue is not so easy from C side.
And more, it is very uncommon for either Python or C implementations (especial C implementations) to introspect to figure out their "real" name. Existing cases are rather exceptions. And in many case this is only a side effect of sharing an implementation between several classes (set and frozenset, three buffered file classes in io, etc). In many cases repr's flexibility is limited: hardcoded or omitted module name, used class's __name__ instead of __qualname__, etc.
This should be discussed on Python-Dev maillist. |
|