Message257615
| Author |
gvanrossum |
| Recipients |
Arfrever, barry, brett.cannon, bronger, cool-RR, daniel.ugra, ezio.melotti, georg.brandl, gvanrossum, pitrou, r.david.murray, serhiy.storchaka, tshepang |
| Date |
2016年01月06日.17:30:22 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<CAP7+vJLteLDFmF7m8TrOabq0o-CAurAsQ4U_q-g991=8r6grDQ@mail.gmail.com> |
| In-reply-to |
<1452078501.63.0.296947355834.issue22570@psf.upfronthosting.co.za> |
| Content |
I think it's actually very reasonable for a Path to have a path attribute
that's a string. The DirEntry has two string attributes: name (the last
component) and path (the full path). The Path object already has the
former. Adding the latter makes sense to me. After all you've gotta give it
*some* name, and 'path' is used (unsurprisingly) in this meaning already in
many places.
The shortest idiom in libraries wanting to support this would be
path = gettattr(arg, 'path', arg)
This extracts the path attribute from a DirEntry or Path object, and
assumes the argument is a string otherwise. I think this is relatively
reasonable to encode in C as well. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2016年01月06日 17:30:22 | gvanrossum | set | recipients:
+ gvanrossum, barry, brett.cannon, georg.brandl, pitrou, bronger, ezio.melotti, Arfrever, r.david.murray, daniel.ugra, cool-RR, tshepang, serhiy.storchaka |
| 2016年01月06日 17:30:22 | gvanrossum | link | issue22570 messages |
| 2016年01月06日 17:30:22 | gvanrossum | create |
|