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 brett.cannon
Recipients Jim Fasarakis-Hilliard, brett.cannon, docs@python
Date 2017-03-03.20:37:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
As brought up on the PR, it turns out Path.absolute() is extremely under-tested.

Perhaps we should deprecate Path.absolute() instead of document it and properly test it (and the testing will be necessary to move forward with the documentation)? Path.resolve() handles absolute paths already while also resolving '.' and '..': It also works with non-existent paths so unless there's some performance issue I'm not aware of for resolving '.' and '..', then I say we deprecate Path.absolute().
Date User Action Args
2017-03-03 20:37:32brett.cannonsetrecipients: + brett.cannon, docs@python, Jim Fasarakis-Hilliard
2017-03-03 20:37:32brett.cannonsetmessageid: <>
2017-03-03 20:37:32brett.cannonlinkissue29688 messages
2017-03-03 20:37:32brett.cannoncreate