bpo-36896: Clarify that some types constructors are unstable (GH-13271)

13136e83 · Matthias Bussonnier · Petr Viktorin · 1e375c62 · 13136e83 · 13136e83
Commit 13136e83 authored Jun 02, 2019 by Matthias Bussonnier Committed by Petr Viktorin Jun 03, 2019
Showing with 5 additions and 0 deletions

Doc/library/types.rst Doc/library/types.rst +3 -0

Misc/NEWS.d/next/Documentation/2019-05-31-10-46-36.bpo-36896.wkXTW9.rst ...xt/Documentation/2019-05-31-10-46-36.bpo-36896.wkXTW9.rst +2 -0

No files found.
--- a/Doc/library/types.rst
+++ b/Doc/library/types.rst
@@ -98,6 +98,9 @@ the types that arise only incidentally during processing such as the
 Typical use of these names is for :func:`isinstance` or
 :func:`issubclass` checks.

+
+If you instantiate any of these types, note that signatures may vary between Python versions.
+
 Standard names are defined for the following types:

 .. data:: FunctionType

--- a/Misc/NEWS.d/next/Documentation/2019-05-31-10-46-36.bpo-36896.wkXTW9.rst
+++ b/Misc/NEWS.d/next/Documentation/2019-05-31-10-46-36.bpo-36896.wkXTW9.rst
+Clarify that some types have unstable constructor signature between Python
+versions.