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 barry
Recipients barry
Date 2014-10-06.15:33:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
pathlib is really nice, but currently it's rather inconvenient to use due to the lack of support in other parts of the stdlib for Path objects.  For historical reasons, everything accepts string paths, but few places accept Paths.  As an example: but there are lots of others.

I'm opening this bug to start a conversation about better support for Path objects in the stdlib.  Against all hope, I wish there was a simple way to extend the compatibility, but I don't like having to sprinkle `str(some_path)` calls everywhere (kind of defeats the purpose of having the nicer pathlib API IMHO).  I suspect instead that it will be a matter of adding type tests or str() conversions to the relevant methods, but there may be other issues to discuss, like is it even a good idea to do this? ;)
Date User Action Args
2014-10-06 15:33:51barrysetrecipients: + barry
2014-10-06 15:33:51barrysetmessageid: <>
2014-10-06 15:33:51barrylinkissue22570 messages
2014-10-06 15:33:51barrycreate