Message302495
| Author | eric.araujo |
|---|---|
| Recipients | eric.araujo, eric.snow, ezio.melotti, gvanrossum, martin.panter, pitrou, rbcollins, serhiy.storchaka, veky, vstinner |
| Date | 2017-09-19.02:38:25 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1505788706.12.0.626789796515.issue13224@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Martin Panter > I’m a bit confused. In the current patch, the new type_str() function > appears to use the “qualname” (which I support), but some of the test > changes seem to contradict this, e.g.: > >>> C.foo(1) > -classmethod <class 'test.test_descrtut.C'> 1 > +classmethod C 1 C is a qualname, as would be C.NestedD or something.<locals>.NestedD The qualname PEP explains why the module is not part of the qualname. Me > Finally, I don’t remember why I changed functions and modules when the two > original use cases were only for classes. The reason is a message by Nick on python-ideas. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2017-09-19 02:38:26 | eric.araujo | set | recipients: + eric.araujo, gvanrossum, pitrou, vstinner, rbcollins, ezio.melotti, eric.snow, martin.panter, serhiy.storchaka, veky |
| 2017-09-19 02:38:26 | eric.araujo | set | messageid: <1505788706.12.0.626789796515.issue13224@psf.upfronthosting.co.za> |
| 2017-09-19 02:38:26 | eric.araujo | link | issue13224 messages |
| 2017-09-19 02:38:25 | eric.araujo | create | |