Feature #11460
closed
Update Django from 3.0.6 to 4.0.3
Added by Evgeny Novikov about 2 years ago.
Updated about 2 years ago.
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.
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.
- Related to Feature #11463: Update Python packages used by Klever added
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.
- 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.
- 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.
Also available in: Atom
PDF