Strict Mode for "Strict" Equivalence of Literals (type)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 250
- Forks
- 36
- PR merge metrics
- No merged PRs in 30d
Description
As per: Equivalence of two Literals
Two types Literal[v1] and Literal[v2] are equivalent when both of the following conditions are true:
type(v1) == type(v2)
v1 == v2
I would like to update deserialization for typing.Literal in v1 opt-in to account for this.
Perhaps a Meta setting strict_mode_for_literals: bool, or else more simply a strict: bool, can be added to support this feature / enhancement.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the v1 opt-in deserialization path for typing.Literal and the Meta configuration described in the issue. Compare the current behavior with the typing specification's equivalence rules, then determine the configuration shape and add coverage demonstrating strict and non-strict literal handling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100