Update primer-on-jinja-templating pins to match the refreshed tutorial - #810
Open
realpython-bot wants to merge 1 commit into
Open
Update primer-on-jinja-templating pins to match the refreshed tutorial#810realpython-bot wants to merge 1 commit into
realpython-bot wants to merge 1 commit into
Conversation
The tutorial "Primer on Jinja Templating" was refreshed in the CMS and now declares Flask 3.1.3 / Jinja2 3.1.6 on Python 3.14. This file still pinned the 2024 set, so the materials built a different environment than the article describes. blinker 1.8.2 -> 1.9.0 click 8.1.7 -> 8.5.0 Flask 3.0.3 -> 3.1.3 Jinja2 3.1.4 -> 3.1.6 MarkupSafe 2.1.5 -> 3.0.3 Werkzeug 3.0.3 -> 3.1.8 itsdangerous stays at 2.2.0, its current release. The transitive bumps are required, not cosmetic: Flask 3.1.3 needs Werkzeug>=3.1, so pinning Flask forward while leaving Werkzeug at 3.0.3 would be an inconsistent set. The versions here are what the resolver picks for Flask==3.1.3 plus Jinja2==3.1.6 on Python 3.14. Verified by running app.py under these pins: both routes return 200 and /results renders the five students ordered by name, matching the article's final results.html. No template or app.py changes -- the content audit raised no code issues for this article. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The tutorial Primer on Jinja Templating was refreshed in the CMS and now declares Flask 3.1.3 / Jinja2 3.1.6 on Python 3.14. This folder still pinned the 2024 set, so the materials built a different environment than the article describes.
What changed
The article itself only names Flask and Jinja2, but the transitive bumps are required, not cosmetic: Flask 3.1.3 requires
Werkzeug>=3.1, so pinning Flask forward while leavingWerkzeug==3.0.3would be an inconsistent set. These versions are exactly what the resolver picks forFlask==3.1.3+Jinja2==3.1.6on Python 3.14.Verification
Ran
app.pyunder these pins with Flask's test client:/→ 200/results→ 200, rendering all five students asFrieda 92, Fritz 40, Gergeley 87, Sandrine 100, Sirius 75— ordered by name, matching the article's finalresults.html(sort(attribute="name")).No template or
app.pychanges. The content audit raised no code issues for this article; the one prose fix in this update pass concerned a chained-sort example that is presented as a hypothetical aside in the article and is not part of the trackedresults.html, so materials are unaffected by it.Prepared during a written-content maintenance review (reviewer: Martin Breuss).
🤖 Generated with Claude Code