-
-
Notifications
You must be signed in to change notification settings - Fork 30.4k
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
The copy module already uses copyreg #55690
Comments
In the copyreg documentation there is this sentence: "The copy module is likely to use this in the future as well." (http://docs.python.org/dev/py3k/library/copyreg) But the copy module already uses the copyreg module. |
A quick reword could be the one attached. |
After quite a long chat with Ezio, I'm just proposing this updated patch:
I'd like to hear comments/suggestions about it. |
New changeset 2bd6150b48ea by Ezio Melotti in branch '2.7': New changeset e089bdca9d9c by Ezio Melotti in branch '2.7': New changeset 12dbb3187105 by Ezio Melotti in branch '3.2': New changeset 87ec3ce3a04e by Ezio Melotti in branch '3.3': New changeset 20b65b88e0a0 by Ezio Melotti in branch 'default': |
I made a few minor changes and applied the patch. |
Maybe some 2.7 backport is missing w.r.t. the documentation of the copy module? At least, http://docs.python.org/2/library/copy.html still states: "The copy module does not use the copy_reg registration module." |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: