Update to Django4 #27

New Issue

mpeltriaux · 2021-10-12T07:45:50+02:00

mpeltriaux commented

2021-10-12 07:45:50 +02:00

Status quo

We are running on Django 3.2.x, which is nice and all but considering Django 4.x being released in December 2021, we should analyze the changes and consider upgrading asap.

ToDo

Read the release notes carefully: https://docs.djangoproject.com/en/dev/releases/4.0/
Make sure backwards incompatibilities won't have any effect on our project, especially on third party packages in use.
Be aware that Python >= 3.8 is needed for development as well as the production environment!

# Status quo We are running on Django 3.2.x, which is nice and all but considering Django 4.x being released in December 2021, we should analyze the changes and consider upgrading asap. # ToDo 1. Read the release notes carefully: https://docs.djangoproject.com/en/dev/releases/4.0/ 1. Make sure backwards incompatibilities won't have any effect on our project, especially on third party packages in use. 1. Be aware that Python >= 3.8 is needed for development as well as the production environment!

mpeltriaux added the

enhancement

question

labels 2021-10-12 07:45:50 +02:00

mpeltriaux self-assigned this 2021-10-12 07:45:50 +02:00

mpeltriaux commented

2022-12-06 13:32:40 +01:00

Changes to GEOS and Python

There have been issues detected on newer Python versions (needed by Django 4.0) and e.g. the newer Django GEOS library.

E.g. geometries created from string data resulted not in MultiPolygons but in GeometryCollections, which are not supported by the database.

Switching to Django 4.0 must be tested absolutely thoroughly before being deployed on staging or even production!

# Changes to GEOS and Python There have been issues detected on newer Python versions (needed by Django 4.0) and e.g. the newer Django GEOS library. E.g. geometries created from string data resulted not in MultiPolygons but in GeometryCollections, which are not supported by the database. Switching to Django 4.0 must be tested absolutely thoroughly before being deployed on staging or even production!

mpeltriaux commented

2023-10-12 09:53:54 +02:00

Further dependencies

django-simple-sso 1.2.0 depends on itsdangerous < 1.0.0 --> need to keep itsdangerous to an older version

# Further dependencies * `django-simple-sso` 1.2.0 depends on `itsdangerous` < 1.0.0 --> need to keep itsdangerous to an older version

mpeltriaux added reference django_4

2023-11-21 13:49:28 +01:00

mpeltriaux commented

2023-12-11 10:45:42 +01:00

Merged in #363

# Merged in #363

mpeltriaux closed this issue

2023-12-11 10:45:42 +01:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: IT-Naturschutz/konova#27