Skip to content

bpo-20823: Clarify copyreg.pickle() documentation #30230

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.

Sign up for GitHub

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

Merged
serhiy-storchaka merged 1 commit into from
Jan 18, 2022
Merged

bpo-20823: Clarify copyreg.pickle() documentation #30230

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
bpo-20823: Clarify copyreg.pickle() documentation
  • Loading branch information
@kumaraditya303
kumaraditya303 committed Dec 22, 2021
commit aa461a3a6d2dba9bd2c82d3aacfe7d14e4c834c8
4 changes: 2 additions & 2 deletions Doc/library/copyreg.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,8 +33,8 @@ Such constructors may be factory functions or class instances.

The optional *constructor* parameter, if provided, is a callable object which
can be used to reconstruct the object when called with the tuple of arguments
returned by *function* at pickling time. :exc:`TypeError` will be raised if
*object* is a class or *constructor* is not callable.
returned by *function* at pickling time. A :exc:`TypeError` is raised if the
Comment thread
kumaraditya303 marked this conversation as resolved.
*constructor* is not callable.

See the :mod:`pickle` module for more details on the interface
expected of *function* and *constructor*. Note that the
Expand Down