Yocto Project Discussions
 help / color / mirror / Atom feed
From: Tim Orling <ticotimo@gmail.com>
To: yocto@lists.yoctoproject.org
Subject: [layerindex-web 00/10] Django 4.2 LTS Upgrade
Date: Fri,  6 Oct 2023 12:59:03 -0700	[thread overview]
Message-ID: <cover.1696621423.git.tim.orling@konsulko.com> (raw)

This series upgrades to the current LTS for Django, 4.2.

The two most obvious changes are:
* django.utils.translation.ugettext() -> gettext
* django.conf.urls.url() -> re_path()

See:
https://docs.djangoproject.com/en/4.2/releases/4.0/#features-removed-in-4-0
https://docs.djangoproject.com/en/4.2/internals/deprecation/#deprecation-removed-in-4-0

While we are at it, upgrade all components in requirements.txt and
update to reflect missing dependencies.

One casualty of this upgrade is django-bootstrap-pagination which
is no longer maintained and incompatible with Django 4.2.

One additional requirement for settings.py is setting CSRF_TRUSTED_ORIGINS to
allow POST requests (ALLOWED_HOSTS is no longer sufficient).

Tim Orling (10):
  requirements.txt: upgrade Django 3.2 -> 4.2
  docker-compose.yml: bump mariadb from 10.3 to 10.4
  Drop django-bootstrap-pagination: incompatible
  bootstrap_pagination: disable via comment
  Refactor usage of django.conf.urls
  Dockerfile: drop python3-pil
  requirements.txt: upgrade all to latest
  requirements.txt: update dependencies
  password_validation.py: fix deprecated ugettext
  docker/settings.py: add CSRF_TRUSTED_ORIGINS

 Dockerfile                                 |   1 -
 docker-compose.yml                         |   2 +-
 docker/settings.py                         |   2 +-
 layerindex/urls.py                         | 108 ++++++++++-----------
 layerindex/urls_branch.py                  |  25 +++--
 password_validation.py                     |   2 +-
 requirements.txt                           |  47 +++++----
 rrs/urls.py                                |  16 +--
 settings.py                                |   1 -
 templates/layerindex/bulkchangesearch.html |   2 +
 templates/layerindex/classes.html          |   2 +
 templates/layerindex/classicrecipes.html   |   2 +
 templates/layerindex/distros.html          |   2 +
 templates/layerindex/history.html          |   2 +
 templates/layerindex/layers.html           |   2 +
 templates/layerindex/machines.html         |   2 +
 templates/layerindex/recipes.html          |   2 +
 templates/layerindex/reviewlist.html       |   2 +
 templates/layerindex/updatelist.html       |   2 +
 urls.py                                    |  31 +++---
 20 files changed, 140 insertions(+), 115 deletions(-)

-- 
2.34.1



             reply	other threads:[~2023-10-06 19:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-06 19:59 Tim Orling [this message]
2023-10-06 19:59 ` [layerindex-web 01/10] requirements.txt: upgrade Django 3.2 -> 4.2 Tim Orling
2023-10-06 19:59 ` [layerindex-web 02/10] docker-compose.yml: bump mariadb from 10.3 to 10.4 Tim Orling
2023-10-06 19:59 ` [layerindex-web 03/10] Drop django-bootstrap-pagination: incompatible Tim Orling
2023-10-06 19:59 ` [layerindex-web 04/10] bootstrap_pagination: disable via comment Tim Orling
2023-10-06 19:59 ` [layerindex-web 05/10] Refactor usage of django.conf.urls Tim Orling
2023-10-06 19:59 ` [layerindex-web 06/10] Dockerfile: drop python3-pil Tim Orling
2023-10-06 19:59 ` [layerindex-web 07/10] requirements.txt: upgrade all to latest Tim Orling
2023-10-06 19:59 ` [layerindex-web 08/10] requirements.txt: update dependencies Tim Orling
2023-10-06 19:59 ` [layerindex-web 09/10] password_validation.py: fix deprecated ugettext Tim Orling
2023-10-06 19:59 ` [layerindex-web 10/10] docker/settings.py: add CSRF_TRUSTED_ORIGINS Tim Orling

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cover.1696621423.git.tim.orling@konsulko.com \
    --to=ticotimo@gmail.com \
    --cc=yocto@lists.yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox