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 r.david.murray
Recipients barry, brett.cannon, cool-RR, ezio.melotti, georg.brandl, pitrou, r.david.murray, tshepang
Date 2014-10-16.19:14:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Well, if you use an isinstance check you privilege the stdlib Path over any other pathlike implementation.  Since it *is* in the stdlib, this isn't an automatic reason for rejection, but it does have a bit of a code smell to it.  Why should everything that deals with path strings have to have intimate knowledge of Path objects?

I originally wrote here "Maybe we need a __path__ magic method" as a half-joke, but rereading the issue I see that this has in fact been proposed seriously, and referenced by Antoine (the pathlib author).

I'm -1 on just sprinkling support for Path throughout the stdlib.  Do it in a universally applicable fashion or don't do it at all, IMO.
Date User Action Args
2014-10-16 19:14:13r.david.murraysetrecipients: + r.david.murray, barry, brett.cannon, georg.brandl, pitrou, ezio.melotti, cool-RR, tshepang
2014-10-16 19:14:13r.david.murraysetmessageid: <>
2014-10-16 19:14:13r.david.murraylinkissue22570 messages
2014-10-16 19:14:13r.david.murraycreate