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 Charles Machalow
Recipients Aaron Hall, Charles Machalow, Dreami, giampaolo.rodola, pitrou, serhiy.storchaka, tarek
Date 2020-06-14.07:48:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I'm disappointed to see this closed. For new (and old) users, it makes complete sense to have an rmtree method on the Path object itself.

If I'm using pathlib, I try not to delegate to os.<things> for file operations, since it also tends to seem more OO and clean to stick with the object methods. Same thought process for shutil for rmtree.

We already have things like owner() and group() that explicitly go import grp, pwd to do their job on Path objects. Why is shutil special with regards to using another piece of the standard library from pathlib? To me this request falls in the same boat as those functions; they were likely added for convenience and since it made sense.

I believe the very same holds true for the request to add rmtree().
Date User Action Args
2020-06-14 07:48:31Charles Machalowsetrecipients: + Charles Machalow, pitrou, giampaolo.rodola, tarek, serhiy.storchaka, Aaron Hall, Dreami
2020-06-14 07:48:31Charles Machalowsetmessageid: <>
2020-06-14 07:48:31Charles Machalowlinkissue33498 messages
2020-06-14 07:48:31Charles Machalowcreate