The Fix
Upgrade to version 2.0.0 or later.
Based on closed pallets/flask issue #3881 · 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%.
@@ -63,6 +63,7 @@ Unreleased
This could allow a session interface to change behavior based on
``request.endpoint``. :issue:`3776`
+- Use Jinja's implementation of the ``|tojson`` filter. :issue:`3881`
Option A — Upgrade to fixed release\nUpgrade to version 2.0.0 or later.\nWhen NOT to use: This fix is not suitable if the original Flask behavior is required.\n\n
Why This Fix Works in Production
- Trigger: Users experience silent overrides in templates, making debugging difficult.
- Mechanism: Flask's `tojson` filter overrides Jinja2's `tojson` filter, limiting configurability
- Why the fix works: Modifies Flask to use Jinja's `tojson` filter instead of overriding it, allowing for better configurability. (first fixed release: 2.0.0).
- 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
- Flask's `tojson` filter overrides Jinja2's `tojson` filter, limiting configurability
- Production symptom (often without a traceback): Users experience silent overrides in templates, making debugging difficult.
Proof / Evidence
- GitHub issue: #3881
- Fix PR: https://github.com/pallets/flask/pull/3895
- First fixed release: 2.0.0
- Reproduced locally: No (not executed)
- Last verified: 2026-02-09
- Confidence: 0.95
- Did this fix it?: Yes (upstream fix exists)
- Own content ratio: 0.77
Discussion
High-signal excerpts from the issue thread (symptoms, repros, edge-cases).
“Took another look at how Jinja's is implemented, and it allows setting the dumps function through Environment.policies, so we could actually completely drop our implementations…”
“I think I'd rather make the flask one as configurable as the jinja one, so flask just adds functionality on top of it...”
“The two do the exact same thing, except Jinja's has an indent parameter”
Failure Signature (Search String)
- Users experience silent overrides in templates, making debugging difficult.
Copy-friendly signature
Failure Signature
-----------------
Users experience silent overrides in templates, making debugging difficult.
Error Message
Signature-only (no traceback captured)
Error Message
-------------
Users experience silent overrides in templates, making debugging difficult.
What Broke
Users experience silent overrides in templates, making debugging difficult.
Why It Broke
Flask's `tojson` filter overrides Jinja2's `tojson` filter, limiting configurability
Fix Options (Details)
Option A — Upgrade to fixed release Safe default (recommended)
Upgrade to version 2.0.0 or later.
Use when you can deploy the upstream fix. It is usually lower-risk than long-lived workarounds.
Fix reference: https://github.com/pallets/flask/pull/3895
First fixed release: 2.0.0
Last verified: 2026-02-09. Validate in your environment.
When NOT to Use This Fix
- This fix is not suitable if the original Flask behavior is required.
Did This Fix Work in Your Case?
Quick signal helps us prioritize which fixes to verify and improve.
Prevention
- Capture the exact failing error string in logs and tests so you can reproduce via a minimal script.
- Pin production dependencies and upgrade only with a reproducible test that hits the failing path.
Version Compatibility Table
| Version | Status |
|---|---|
| 2.0.0 | Fixed |
Related Issues
No related fixes found.
Sources
We don’t republish the full GitHub discussion text. Use the links above for context.