Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bpo-40982: Fix outdated copytree() "example" in the shutil docs #24778

Merged

Conversation

Copy link
Contributor

@ZackerySpytz ZackerySpytz commented Mar 7, 2021

It is not preferable to keep a copy of the implementation in the
docs.

https://bugs.python.org/issue40982

It is not preferable to keep a copy of the implementation in the
docs.
@github-actions
Copy link

@github-actions github-actions bot commented Apr 7, 2021

This PR is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale label Apr 7, 2021
@@ -470,42 +470,7 @@ file then shutil will silently fallback on using less efficient
copytree example
~~~~~~~~~~~~~~~~
Copy link
Contributor

@nanjekyejoannah nanjekyejoannah May 29, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think removing it would make sense but you leave a hanging heading. Do you have a reason for this?

Also, the bpo asked for a fix to the example, I would think deciding to remove it instead requires some consensus, maybe @willingc and @Mariatta can advise.

Copy link
Member

@iritkatriel iritkatriel Jun 24, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think this leaves the header dangling - it relates to the next example (not that the last modified like changes "Another example..." to "An example...", because the next one is now the first).

@JelleZijlstra JelleZijlstra self-assigned this Apr 3, 2022
@JelleZijlstra JelleZijlstra merged commit e06f920 into python:main Apr 5, 2022
12 checks passed
@miss-islington
Copy link
Contributor

@miss-islington miss-islington commented Apr 5, 2022

Thanks @ZackerySpytz for the PR, and @JelleZijlstra for merging it 🌮🎉.. I'm working now to backport this PR to: 3.9, 3.10.
🐍🍒🤖 I'm not a witch! I'm not a witch!

miss-islington pushed a commit to miss-islington/cpython that referenced this issue Apr 5, 2022
…24778)

It is not preferable to keep a copy of the implementation in the
docs.
(cherry picked from commit e06f920)

Co-authored-by: Zackery Spytz <zspytz@gmail.com>
miss-islington pushed a commit to miss-islington/cpython that referenced this issue Apr 5, 2022
…24778)

It is not preferable to keep a copy of the implementation in the
docs.
(cherry picked from commit e06f920)

Co-authored-by: Zackery Spytz <zspytz@gmail.com>
@bedevere-bot
Copy link

@bedevere-bot bedevere-bot commented Apr 5, 2022

GH-32326 is a backport of this pull request to the 3.10 branch.

@bedevere-bot
Copy link

@bedevere-bot bedevere-bot commented Apr 5, 2022

GH-32327 is a backport of this pull request to the 3.9 branch.

miss-islington added a commit that referenced this issue Apr 5, 2022
It is not preferable to keep a copy of the implementation in the
docs.
(cherry picked from commit e06f920)

Co-authored-by: Zackery Spytz <zspytz@gmail.com>
miss-islington added a commit that referenced this issue Apr 5, 2022
It is not preferable to keep a copy of the implementation in the
docs.
(cherry picked from commit e06f920)

Co-authored-by: Zackery Spytz <zspytz@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA signed docs skip news stale
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants