-
Notifications
You must be signed in to change notification settings - Fork 299
typeddict: clarify that .get() with an unknown literal key is not an error #2312
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
ashishpatel26
wants to merge
2
commits into
python:main
Choose a base branch
from
ashishpatel26:fix/2054-typeddict-get-unknown-literal-key
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, 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
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -757,9 +757,19 @@ This section discusses some specific operations in more detail. | |
| should be allowed for TypedDict objects, for an arbitrary expression | ||
| ``e`` with type ``str``. The motivation is that these are safe and | ||
| can be useful for introspecting TypedDict objects. The static type | ||
| of ``d.get(e)`` should be the union of all possible item types in ``d`` | ||
| if the string value of ``e`` cannot be determined statically. | ||
| (This simplifies to ``object`` if ``d`` is :term:`open`.) | ||
| of ``d.get(e)`` depends on what is known about the value of ``e``: | ||
|
|
||
| - If ``e`` is a string literal equal to a defined key of ``d``, the | ||
| return type is the declared type of that key combined with ``None`` | ||
| for non-required keys. For required keys, type checkers may return | ||
| either the declared type ``T`` or ``T | None``. | ||
| - If ``e`` is a string literal that is **not** a defined key of ``d``, | ||
| no error should be reported. The return type is the union of all | ||
| possible value types in ``d`` combined with ``None``. | ||
| - If the string value of ``e`` cannot be determined statically, the | ||
| return type is the union of all possible value types in ``d`` | ||
| combined with ``None``. (This simplifies to ``object | None`` if | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Which is just |
||
| ``d`` is :term:`open`.) | ||
|
|
||
| * ``clear()`` is not safe on :term:`open` TypedDicts since it could remove required items, some of which | ||
| may not be directly visible because of :term:`structural` | ||
|
|
||
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why leave this as an option? If the key is required, then it must be present so
.get()can't return None.