Jump to solution
Verify

The Fix

pip install pydantic==1.10.1

Based on closed pydantic/pydantic issue #8677 · PR/commit linked

Production note: Most teams hit this during upgrades or environment changes. Roll out with a canary and smoke critical endpoints (health, OpenAPI/docs) before 100%.

Jump to Verify Open PR/Commit
@@ -0,0 +1 @@ @@ -0,0 +1 @@ +Fix `cls` argument in validators during assignment diff --git a/pydantic/main.py b/pydantic/main.py index b1d38d029c6..5372f5c67cd 100644
repro.py
from pydantic import BaseModel class Point(BaseModel): coordinates: tuple[float, float] | tuple[float, float, float] print(Point(coordinates=(1.0, 2.0)).model_dump()) print(Point(coordinates=(1.0, 2.0, 3.0)).model_dump())
verify
Re-run the minimal reproduction on your broken version, then apply the fix and re-run.
fix.md
Option A — Upgrade to fixed release\npip install pydantic==1.10.1\nWhen NOT to use: Do not use if it changes public behavior or if the failure cannot be reproduced.\n\n

Why This Fix Works in Production

  • Trigger: false-positive warning wiht pydantic 2.6.0 "Unexpected extra items present in tuple"
  • Mechanism: Fixed a false positive warning in Pydantic 2.6.0 regarding unexpected extra items in tuples.
  • Why the fix works: Fixed a false positive warning in Pydantic 2.6.0 regarding unexpected extra items in tuples. (first fixed release: 1.10.1).
Production impact:
  • If left unfixed, the same config can fail only in production (env differences), causing startup failures or partial feature outages.

Why This Breaks in Prod

  • Shows up under Python 3.10 in real deployments (not just unit tests).
  • Production symptom (often without a traceback): false-positive warning wiht pydantic 2.6.0 "Unexpected extra items present in tuple"

Proof / Evidence

Discussion

High-signal excerpts from the issue thread (symptoms, repros, edge-cases).

“@schenker, Thanks for the report. We'll look into a fix for this to be included in a patch release soon!”
@sydney-runkle · 2024-01-30 · source

Failure Signature (Search String)

  • false-positive warning wiht pydantic 2.6.0 "Unexpected extra items present in tuple"
  • Unexpected extra items present in tuple
Copy-friendly signature
signature.txt
Failure Signature ----------------- false-positive warning wiht pydantic 2.6.0 "Unexpected extra items present in tuple" Unexpected extra items present in tuple

Error Message

Signature-only (no traceback captured)
error.txt
Error Message ------------- false-positive warning wiht pydantic 2.6.0 "Unexpected extra items present in tuple" Unexpected extra items present in tuple

Minimal Reproduction

repro.py
from pydantic import BaseModel class Point(BaseModel): coordinates: tuple[float, float] | tuple[float, float, float] print(Point(coordinates=(1.0, 2.0)).model_dump()) print(Point(coordinates=(1.0, 2.0, 3.0)).model_dump())

Environment

  • Python: 3.10
  • Pydantic: 2.6.0

What Broke

Users experienced misleading warnings when using tuples in Pydantic models.

Fix Options (Details)

Option A — Upgrade to fixed release Safe default (recommended)

pip install pydantic==1.10.1

When NOT to use: Do not use if it changes public behavior or if the failure cannot be reproduced.

Use when you can deploy the upstream fix. It is usually lower-risk than long-lived workarounds.

Fix reference: https://github.com/pydantic/pydantic-core/pull/1174

First fixed release: 1.10.1

Last verified: 2026-02-09. Validate in your environment.

Get updates

We publish verified fixes weekly. No spam.

Subscribe

When NOT to Use This Fix

  • Do not use if it changes public behavior or if the failure cannot be reproduced.

Verify Fix

verify
Re-run the minimal reproduction on your broken version, then apply the fix and re-run.

Did This Fix Work in Your Case?

Quick signal helps us prioritize which fixes to verify and improve.

Prevention

  • Add a CI check that diffs key outputs after upgrades (OpenAPI schema snapshots, JSON payload shapes, CLI output).
  • Upgrade behind a canary and run integration tests against the canary before 100% rollout.

Version Compatibility Table

VersionStatus
1.10.1 Fixed

Related Issues

No related fixes found.

Sources

We don’t republish the full GitHub discussion text. Use the links above for context.