bpo-27635: Fix pickle documentation about __new__ not being called. (GH-19269)

miss-islington · furkanonder · web-flow · commit 0abb548cc7b2 · 2020-04-18T11:14:41.000-07:00
Automerge-Triggered-By: @pitrou (cherry picked from commit 482259d) Co-authored-by: Furkan Önder <furkantahaonder@gmail.com>
diff --git a/Doc/library/pickle.rst b/Doc/library/pickle.rst
@@ -562,9 +562,9 @@ the methods :meth:`__getstate__` and :meth:`__setstate__`.
    At unpickling time, some methods like :meth:`__getattr__`,
    :meth:`__getattribute__`, or :meth:`__setattr__` may be called upon the
    instance.  In case those methods rely on some internal invariant being
-   true, the type should implement :meth:`__getnewargs__` or
-   :meth:`__getnewargs_ex__` to establish such an invariant; otherwise,
-   neither :meth:`__new__` nor :meth:`__init__` will be called.
+   true, the type should implement :meth:`__new__` to establish such an
+   invariant, as :meth:`__init__` is not called when unpickling an
+   instance.
 
 .. index:: pair: copy; protocol
 
diff --git a/Misc/NEWS.d/next/Documentation/2020-04-01-00-27-03.bpo-27635.VwxUty.rst b/Misc/NEWS.d/next/Documentation/2020-04-01-00-27-03.bpo-27635.VwxUty.rst
@@ -0,0 +1,2 @@
+The pickle documentation incorrectly claimed that ``__new__`` isn't called by
+default when unpickling.

Original file line number	Diff line number	Diff line change
`@@ -0,0 +1,2 @@`
	`1`	+The pickle documentation incorrectly claimed that ``__new__`` isn't called by
	`2`	`+default when unpickling.`