PEP 484: Clarify definition of AnyStr - #744
Merged
ambv merged 1 commit intoSep 12, 2018
Merged
Conversation
Copy link
Copy Markdown
Member
Sorry, something went wrong.
The definition of AnyStr as given makes sense only in Python 3, as observed by @srittau. To prevent confusion, this PR changes the definition to use Text instead of str. I also changed the two places where AnyStr was defined as an example, and made a few other related adjustments: - Remove mention of None as modifying the type, which is not true as of python#689. - Move Text up in the list of convenience definition because we now need it for the definition of AnyStr. - Modify definition of Optional to use `None` instead of `type(None)`, because the latter is not a valid static type.
gvanrossum
approved these changes
Jul 21, 2018
Comment thread
pep-0484.txt
| What should the default value look like? Any of the options ``""``, | ||
| ``b""`` or ``None`` fails to satisfy the type constraint (actually, | ||
| ``None`` will *modify* the type to become ``Optional[AnyStr]``). | ||
| ``b""`` or ``None`` fails to satisfy the type constraint. |
Copy link
Copy Markdown
Member
There was a problem hiding this comment.
Good call.
Sorry, something went wrong.
Comment thread
pep-0484.txt
| * Optional, defined by ``Optional[t] == Union[t, type(None)]`` | ||
|
|
||
| * AnyStr, defined as ``TypeVar('AnyStr', str, bytes)`` | ||
| * Optional, defined by ``Optional[t] == Union[t, None]`` |
Copy link
Copy Markdown
Member
There was a problem hiding this comment.
Another good call. Perhaps the section on "Using None" should also be revised? It currently says
When used in a type hint, the expression None is considered equivalent to type(None).
But that's false -- at least for mypy, and IIRC we once discussed this and decided that this is intentional: type(None) is not acceptable at all in type hints!
Sorry, something went wrong.
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
Reviewers
4 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.
The definition of AnyStr as given makes sense only in Python 3, as observed by @srittau. To prevent confusion, this PR changes the definition to use Text instead of str.
I also changed the two places where AnyStr was defined as an example, and made a few other related adjustments: