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 ethan.furman
Recipients brett.cannon, eryksun, ethan.furman, paul.moore, serhiy.storchaka, steve.dower, tim.golden, zach.ware
Date 2016-06-03.19:22:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
The expected scenario, and the purpose of os.fspath(), is to enable high-level libraries to not know or care if they receive a pathlib object or a string.

In other words, they already have os.path.join() and os.path.split() calls, and currently break noisily if a pathlib.Path is passed in; by enhancing os.path to accept a pathlib.Path object that high-level library can start working with pathlib.Path objects without changing a thing, which means the user of that library can use pathlib.Path painlessly.

Unless I have seriously misunderstood something, os.path will be changed to work with __fspath__ objects.
Date User Action Args
2016-06-03 19:22:27ethan.furmansetrecipients: + ethan.furman, brett.cannon, paul.moore, tim.golden, zach.ware, serhiy.storchaka, eryksun, steve.dower
2016-06-03 19:22:27ethan.furmansetmessageid: <>
2016-06-03 19:22:27ethan.furmanlinkissue27184 messages
2016-06-03 19:22:27ethan.furmancreate