➜

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 serhiy.storchaka
Recipients Arfrever, blokeley, eric.araujo, giampaolo.rodola, martin.panter, paul.moore, pitrou, r.david.murray, rhettinger, santoso.wijaya, serhiy.storchaka, terry.reedy
Date 2015-04-20.09:04:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1429520653.72.0.0571775813156.issue11344@psf.upfronthosting.co.za>
In-reply-to
Content 
I thought that splitpath() could be used in implementations of realpath(), relpath(), commonpath(), and in user code. But looks as realpath(), relpath() and commonpath() should use specialized inlined versions for efficiency, and user code can use more highlevel pathlib. For now there are no strong arguments for adding splitpath().

The patch is updated to the tip (for the case if it will needed in the future) and the issue is closed.
History
Date User Action Args
2015-04-20 09:04:13serhiy.storchakasetrecipients: + serhiy.storchaka, rhettinger, terry.reedy, paul.moore, pitrou, giampaolo.rodola, eric.araujo, Arfrever, r.david.murray, santoso.wijaya, blokeley, martin.panter
2015-04-20 09:04:13serhiy.storchakasetmessageid: <1429520653.72.0.0571775813156.issue11344@psf.upfronthosting.co.za>
2015-04-20 09:04:13serhiy.storchakalinkissue11344 messages
2015-04-20 09:04:13serhiy.storchakacreate