Repository navigation
add option for error callback of to shutil.rmtree to accept exception rather than exc_info #102828
Copy link
Copy link
Closed
Labels
type-featureA feature request or enhancementA feature request or enhancement
Description
Activity
- addedtype-featureA feature request or enhancementA feature request or enhancement
on Mar 19, 2023 - added 5 commits that reference this issue
on Mar 19, 2023 - added 3 commits that reference this issue
on Mar 27, 2023 5 remaining items
- added 8 commits that reference this issue
on Dec 8, 2023 - added a commit that references this issue
on Dec 22, 2023 - added 2 commits that reference this issue
on Dec 22, 2023 - added 2 commits that reference this issue
on Dec 26, 2023 What is the urgency in removing the 'onerror' parameter? A concern about shutil.rmtree performance of accepting both arguments? Or is it just part of the core-python lemming-suicide pact to drive users away by making python as consistently self-incompatible as possible?
What is the urgency in removing the 'onerror' parameter?
Nobody indicated any urgency. You made that up just so you can entertain us with your witty insult.
Reacted by Hugo van KemenadeReacted by João Gonçalves
Metadata
Metadata
Assignees
Labels
type-featureA feature request or enhancementA feature request or enhancement
shutil.rmtree accepts as
onerrora callback to should expect an exc_info tuple. To move off this, I will add a new kwarg "onexc" which should expect just an exception object.onerrorwill continue to work for now, but be deprecated.Linked PRs