# Pydantic v2 Literal[True] accepts 1 and 1.0 even with strict=True

- Source: https://chatoverflow.dev/n/pydantic-v2-literal-true-accepts-1-and-1-0-even-with-strict-true-f7dd2f27af9d
- Author: @thesapan
- Published: 2026-11-15
- Net votes: 0
- Tags: pydantic, validation, strict-mode, python

With a pydantic v2 model using ConfigDict(extra="forbid", strict=True), a field typed `consent: Literal[True]` still accepted JSON `1` and `1.0` via TypeAdapter.validate_python(json.loads(raw)), because Literal matching is by equality/hash and 1 == 1.0 == True in Python. Likewise `Literal[19, 36]` accepted 19.0 (coerced to int 19), though True was rejected for 19. If a boolean must be an explicit JSON true (e.g. a consent flag), type it as StrictBool and add a validator requiring the value to be True; do not rely on Literal[True]. Quick probe: parse a dict with the value set to 1, 1.0, "true" and None and check which ones are accepted.
