Project

General

Profile

Actions

Feature #11460

closed

Update Django from 3.0.6 to 4.0.3

Added by Evgeny Novikov 11 months ago. Updated 10 months ago.

Status:
Closed
Priority:
High
Category:
Bridge
Target version:
Start date:
03/04/2022
Due date:
03/09/2022
% Done:

100%

Estimated time:
Published in build:

Description

Our Web UI (Bridge) still bases on Django 3.0.6 released almost 2 years ago. Moreover, the corresponding branch 3.x is not supported anyhow for almost 1 year. Let's try to use the latest available version of Django in Bridge.


Related issues 2 (0 open2 closed)

Related to Klever - Feature #11463: Update Python packages used by KleverClosedEvgeny Novikov03/04/2022

Actions
Blocked by Klever - Feature #10937: Migrate Klever to Python 3.10ClosedEvgeny Novikov09/10/2021

Actions
Actions #1

Updated by Evgeny Novikov 11 months ago

Actions #2

Updated by Evgeny Novikov 11 months ago

It turns out that new versions of Django require Python 3.8 while many things in Klever are bound to Python 3.7. So we need to update Python in addition.

Actions #3

Updated by Evgeny Novikov 11 months ago

  • Related to Feature #11463: Update Python packages used by Klever added
Actions #4

Updated by Evgeny Novikov 11 months ago

Another issue is that new versions of psycopg2 are not compatible with old versions of Django (you can read here for example). Thus, I have to restrict them additionally when doing #11463. Do not forget to get rid from this restriction after updating Django.

Actions #5

Updated by Vladimir Gratinskiy 11 months ago

  • Due date set to 03/09/2022
  • Status changed from New to Resolved
  • % Done changed from 0 to 100

Implemented in branch "bridge-11460". New DB migrations should be applied.

Actions #6

Updated by Evgeny Novikov 10 months ago

  • Status changed from Resolved to Closed

I merged this branch to master in d1891272c as a part of branch switch-to-python-3.10, so all updates will be applied together. Tests passed successfully after update.

Klever deployment scripts migrate Klever's database automatically, so you only need to do that manually if you have handcrafted deployments.

Actions

Also available in: Atom PDF