René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Callable supplied to `shutil.rmtree(onexc=...)` should accept a single argument","articleBody":"The `onexc` argument was added two weeks ago to replace `onerror`: d51a6dc28e1b2cd0353a78bd13f46e288fa39aa6\r\n\r\nThough it improves the third argument (replacing a 3-tuple with the exception object), I think we should also consider two further improvements while we're in the business of replacing `onerror`, as the opportunity may not come again for a long time:\r\n\r\n1. The first argument, `function`, provides an unreasonably deep insight into the internals of `rmtree()`. The implementation already bends the truth, for example supplying `os.path.islink` when a *junction* check fails. Error reporting can already be achieved by printing or re-raising the exception. It's not used in the standard library (e.g. by `tempfile`). What legitimate use cases are there? I propose we remove it!\r\n2. The second argument, `path`, is already be available via `exc.filename`. This is noted in `os.walk()`'s documentation of its `onerror` argument. Also propose we remove it.\r\n\r\nIf we make `onexc` accept a single argument, it would align with the `onerror` argument to `os.walk()` and `os.fwalk()`, and provide more relevant (/less redundant) information.","author":{"url":"https://github.com/barneygale","@type":"Person","name":"barneygale"},"datePublished":"2023-04-03T18:14:49.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":4},"url":"https://github.com/103218/cpython/issues/103218"}