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 bronger
Recipients Arfrever, barry, brett.cannon, bronger, cool-RR, daniel.ugra, ezio.melotti, georg.brandl, pitrou, r.david.murray, tshepang
Date 2015-10-17.10:13:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1445076814.05.0.321317436481.issue22570@psf.upfronthosting.co.za>
In-reply-to
Content
Please be conservative with adding methods to Path.

FWIW, my own experiences with pathlib have shown that utility methods have the disadvantage of duplicating well-established Python idioms.  This reduces code readability in my opinion.  While it is desirable that the rather inconvenient os.path may be superseded by pathlib in the long run,  utility methods like Path.glob, Path.open, Path.mkdir, and Path.readtext have convenient stdlib counterparts with long tradition, and using the methods seems disruptive and confusing to me.

This is a further argument for having a path protocol instead IMO.
History
Date User Action Args
2015-10-17 10:13:34brongersetrecipients: + bronger, barry, brett.cannon, georg.brandl, pitrou, ezio.melotti, Arfrever, r.david.murray, daniel.ugra, cool-RR, tshepang
2015-10-17 10:13:34brongersetmessageid: <1445076814.05.0.321317436481.issue22570@psf.upfronthosting.co.za>
2015-10-17 10:13:34brongerlinkissue22570 messages
2015-10-17 10:13:33brongercreate