github-starred/awesome-compose
2
0
Fork 0
mirror of https://github.com/docker/awesome-compose.git synced 2026-03-09 06:52:08 -05:00
Code Issues 627 Packages Projects Releases Wiki Activity

[PR #538] Update Django version to 4.2 (LTS) and Python to 3.12 in Django example #544

New Issue
Open
opened 2025-11-06 14:28:26 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-06 14:28:26 -06:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/docker/awesome-compose/pull/538
Author: @weslord
Created: 12/21/2024
Status: 🔄 Open

Base: master ← Head: django-version

📝 Commits (3)

  • a0eb607 Update Django version to 4.2 (LTS) and Python to 3.12
  • 41904ed Update Django example project files to match 4.2 template
  • 7981244 Update image version number in django/README.md examples

📊 Changes

7 files changed (+48 additions, -28 deletions)

View changed files

📝 django/README.md (+2 -2)
📝 django/app/Dockerfile (+1 -1)
➕ django/app/example/asgi.py (+16 -0)
📝 django/app/example/settings.py (+18 -15)
📝 django/app/example/urls.py (+9 -8)
📝 django/app/example/wsgi.py (+1 -1)
📝 django/app/requirements.txt (+1 -1)

📄 Description

Django 3.2 and Python 3.7 are no longer supported.

I also ran django-admin startproject to update the project files.

The diff looks hairier than it is. Most of the lines are startproject updating the version number in comments.

Here are the concrete changes:

  • URL config uses path() instead of url() (this is the only breaking change)
  • Settings uses pathlib.Path instead of path.join
  • Added new ASGI config
  • DEFAULT_AUTO_FIELD = 'django.db.models.BigAutoField'

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/docker/awesome-compose/pull/538 **Author:** [@weslord](https://github.com/weslord) **Created:** 12/21/2024 **Status:** 🔄 Open **Base:** `master` ← **Head:** `django-version` --- ### 📝 Commits (3) - [`a0eb607`](https://github.com/docker/awesome-compose/commit/a0eb607d45c5f673ae9971cc70e55b53f077ae14) Update Django version to 4.2 (LTS) and Python to 3.12 - [`41904ed`](https://github.com/docker/awesome-compose/commit/41904edd6a919ef41c961a19f6d2779d2fc8ef90) Update Django example project files to match 4.2 template - [`7981244`](https://github.com/docker/awesome-compose/commit/7981244a37bb5a624907e6e02aee7c5f6b3439e8) Update image version number in django/README.md examples ### 📊 Changes **7 files changed** (+48 additions, -28 deletions) <details> <summary>View changed files</summary> 📝 `django/README.md` (+2 -2) 📝 `django/app/Dockerfile` (+1 -1) ➕ `django/app/example/asgi.py` (+16 -0) 📝 `django/app/example/settings.py` (+18 -15) 📝 `django/app/example/urls.py` (+9 -8) 📝 `django/app/example/wsgi.py` (+1 -1) 📝 `django/app/requirements.txt` (+1 -1) </details> ### 📄 Description Django 3.2 and Python 3.7 are no longer supported. I also ran `django-admin startproject` to update the project files. The diff looks hairier than it is. Most of the lines are `startproject` updating the version number in comments. Here are the concrete changes: - URL config uses `path()` instead of `url()` (this is the only breaking change) - Settings uses `pathlib.Path` instead of `path.join` - Added new ASGI config - `DEFAULT_AUTO_FIELD = 'django.db.models.BigAutoField'` --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2025-11-06 14:28:26 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
good first issue
proposal
pull-request
Mirrored from GitHub Pull Request
 question
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/awesome-compose#544
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?