bpo-36896: Clarify that some types constructors are unstable#13271
bpo-36896: Clarify that some types constructors are unstable#13271encukou merged 1 commit intopython:masterfrom
Conversation
I'm trying to make the consensus explicit: https://mail.python.org/pipermail/python-dev/2019-May/157795.html |
|
Thanks @encukou I'm happy to rephrase; I 'm just tryin to convey they are supposed to mostly be used for checking isinstance. Would you prefer something around "stability of constructor signatures is not guaranteed between python versions, not recommend and thus not documented" ? |
terryjreedy
left a comment
There was a problem hiding this comment.
Add a blurb. With very few exceptions, there should be one for every bpo issue. (If multiple PRs for an issue, there would normally still be just one blurb.)
|
A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated. Once you have made the requested changes, please leave a comment on this pull request containing the phrase |
90b070f to
29b5f2f
Compare
|
I have made the requested changes; please review again. |
|
Thanks for making the requested changes! @terryjreedy: please review the changes made to this pull request. |
Misc/NEWS.d/next/Documentation/2019-05-31-10-46-36.bpo-36896.wkXTW9.rst
Outdated
Show resolved
Hide resolved
At least it will represent the current state, which seem to be a consensus; but is not explicit.
29b5f2f to
f26a1a3
Compare
|
Thanks !
…On Sun, Jun 2, 2019, 17:44 Petr Viktorin ***@***.***> wrote:
Merged #13271 <#13271> into master.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#13271?email_source=notifications&email_token=AACR5T63CIZKAP2T347VM2LPYRSODA5CNFSM4HMLSOE2YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGORYIREEA#event-2383483408>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AACR5TZBLI3LQE67G7YXJVDPYRSODANCNFSM4HMLSOEQ>
.
|
At least it will represent the current state, which seem to be a
consensus; but is not explicit.
Not sure this requires a News item; it would also be good to add this
info in the constructors docstrings.
https://bugs.python.org/issue36896