In order to ensure Athento's compliance with functional and security requirements at platform level and to allow our customers to have access to more modern technologies and new capabilities, the framework has been upgraded from Python 3.7 to Python 3.11 and from Django 3.2 to Django 4.2.
General questions for upgrade
Are special hardware features required?
All our customers are on Python version 3.7, which guarantees that they have a machine with Ubuntu Server 22.04. for each of the instances. For more information see: Athento installation requirements.
At the server architecture level, are any changes required?
No changes are required.
Are changes required at the database level?
It is recommended that the PostgreSQL version be updated to version 12 or higher. In order not to mix both interventions, it is recommended to perform before or after the framework version upgrade.
Is the balancing structure maintained?
The final infrastructure after the upgrade will be the same, so the previously established balancing configurations will be maintained.
Are there any changes with Elasticsearch for the migration?
It is not necessary to make changes in the integration with Elasticsearch. For more information see: Integration with Elastic Search
What are the implications?
All changes at the product level are first tested by our engineers, however in the upgrade process there is a possibility that issues may arise that have not been detected in previous tests.
In this case, the biggest change is in Django, for which some libraries have had to be updated by forking the original repository, as it does not yet have support for Python 3.11 or Django 4.2.
How is it done?
Initially the upgrade will be deployed in UAT environments, only in those cases where there are deliveries or projects in progress will require a particular planning, for this situation please contact Athento's project team.
For production environments, after the version upgrade there will be a stabilization period of 1 week attended by support.
Do I have to make changes to custom code?
At the moment, the custom code changes we have detected are as follows:
When we have imports of the style:
from django.conf.urls import url
they need to be changed to:
from django.urls import re_path as url
When we have imports of the style:
from django.utils.translation import ugettext as _
they need to be changed to:
from django.utils.translation import gettext as _
Reference documentation: https://docs.python.org/3.11/whatsnew/index.html
Comments
0 comments
Please sign in to leave a comment.