bpo-28556: Update the opening note in typing docs#16204
Merged
ilevkivskyi merged 2 commits intopython:masterfrom Sep 16, 2019
Merged
bpo-28556: Update the opening note in typing docs#16204ilevkivskyi merged 2 commits intopython:masterfrom
ilevkivskyi merged 2 commits intopython:masterfrom
Conversation
ilevkivskyi
added
docs
gvanrossum
reviewed
Sep 16, 2019
Doc/library/typing.rst
Outdated
| :term:`provisional basis <provisional api>`. New features might | ||
| be added and API may change even between minor releases if deemed | ||
| necessary by the core developers. | ||
| Python runtime does not enforce the function and variable type annotations. |
Member
There was a problem hiding this comment.
The Python runtime does not enforce the function and ...
gvanrossum
approved these changes
Sep 16, 2019
Member
gvanrossum
left a comment
gvanrossum
left a comment
There was a problem hiding this comment.
I don't recall exactly how it became non-provisional, I think we already bent the rules for provisional modules by keeping it provisional longer than one release cycle. :-)
Contributor
|
Thanks @ilevkivskyi for the PR 🌮🎉.. I'm working now to backport this PR to: 3.7, 3.8. |
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this pull request
Sep 16, 2019
This PR replaces the old note mentioning that `typing` is a provisional module with a new one mentioning types are not enforced at runtime. I am not sure if there was any official announcement about making `typing` non-provisional, but _de-facto_ no new features were added during Python 3.7, and no backwards incompatible changes were made except for few small things that were considered bugs. (cherry picked from commit 81528ba) Co-authored-by: Ivan Levkivskyi <levkivskyi@gmail.com>
|
GH-16205 is a backport of this pull request to the 3.8 branch. |
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this pull request
Sep 16, 2019
This PR replaces the old note mentioning that `typing` is a provisional module with a new one mentioning types are not enforced at runtime. I am not sure if there was any official announcement about making `typing` non-provisional, but _de-facto_ no new features were added during Python 3.7, and no backwards incompatible changes were made except for few small things that were considered bugs. (cherry picked from commit 81528ba) Co-authored-by: Ivan Levkivskyi <levkivskyi@gmail.com>
|
GH-16206 is a backport of this pull request to the 3.7 branch. |
miss-islington
added a commit
that referenced
this pull request
Sep 16, 2019
This PR replaces the old note mentioning that `typing` is a provisional module with a new one mentioning types are not enforced at runtime. I am not sure if there was any official announcement about making `typing` non-provisional, but _de-facto_ no new features were added during Python 3.7, and no backwards incompatible changes were made except for few small things that were considered bugs. (cherry picked from commit 81528ba) Co-authored-by: Ivan Levkivskyi <levkivskyi@gmail.com>
miss-islington
added a commit
that referenced
this pull request
Sep 16, 2019
This PR replaces the old note mentioning that `typing` is a provisional module with a new one mentioning types are not enforced at runtime. I am not sure if there was any official announcement about making `typing` non-provisional, but _de-facto_ no new features were added during Python 3.7, and no backwards incompatible changes were made except for few small things that were considered bugs. (cherry picked from commit 81528ba) Co-authored-by: Ivan Levkivskyi <levkivskyi@gmail.com>
JelleZijlstra
added a commit
to python/peps
that referenced
this pull request
May 1, 2021
PEP 484 is still marked as "Provisional", but as @Fidget-Spinner pointed out in python/typing#805, it shouldn't be any more. python/cpython#16204 removed talk about typing's provisional status from the module docs, and enhancements to typing have been in the form of new PEPs for the last few release cycles. Going to mark this as a draft so Guido can have a chance to comment once he's back.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR replaces the old note mentioning that
typingis a provisional module with a new one mentioning types are not enforced at runtime. I am not sure if there was any official announcement about makingtypingnon-provisional, but de-facto no new features were added during Python 3.7, and no backwards incompatible changes were made except for few small things that were considered bugs.https://bugs.python.org/issue28556