Nick Coghlan ncoghlan at gmail.com
Wed Apr 6 02:29:34 EDT 2016

• Previous message (by thread): [Python-Dev] When should pathlib stop being provisional?
• Next message (by thread): [Python-Dev] When should pathlib stop being provisional?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

On 6 April 2016 at 15:57, Serhiy Storchaka <storchaka at gmail.com> wrote:
> On 06.04.16 05:44, Nick Coghlan wrote:
>>
>> The most promising option for that is probably "getattr(path, 'path',
>> path)", since the "path" attribute is being added to pathlib, and the
>> given idiom can be readily adopted in Python 2/3 compatible code
>> (since normal strings and any other object without a "path" attribute
>> are passed through unchanged). Alternatively, since it's a protocol,
>> double-underscores on the property name may be appropriate (i.e.
>> "getattr(path, '__path__', path)")
>
> This was already discussed. Current conclusion is using the "path"
> attribute. See http://bugs.python.org/issue22570 .

I'd missed the existing precedent in DirEntry.path, so simply taking
that and running with it sounds good to me.

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia

---

• Previous message (by thread): [Python-Dev] When should pathlib stop being provisional?
• Next message (by thread): [Python-Dev] When should pathlib stop being provisional?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list