Skip to content

[Snyk] Security upgrade django from 1.2 to 4.2.26 #41

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
hsingh23 wants to merge 1 commit into
base: master
Choose a base branch
from
Open

[Snyk] Security upgrade django from 1.2 to 4.2.26 #41

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion requirements.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@
# during development.

# GAE packages should match the "libraries" section of app.yaml
django==1.2
django==4.2.26
jinja2==2.6
Comment on lines 6 to 8
Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot Nov 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P0 Badge Upgrading to Django 4 breaks Python 2 environment

Bumping django to 4.2.26 assumes a Python ≥3.8 runtime, while the project still targets the legacy App Engine Python runtime (app.yaml declares runtime: python and the surrounding pinned packages are Python‑2–only). On the existing Python 2 dev/CI setup pip install -r requirements.txt will now fail with “Django 4.2 requires Python >=3.8”, preventing the application from installing dependencies or running. Unless the entire stack is ported to Python 3 alongside this change, this upgrade is a build‑blocking regression.

Useful? React with 👍 / 👎.

markupsafe==0.15
webapp2==2.3
Expand Down