Open thebaptiste opened 2 years ago
I am testing the migration from Django 3.2 to Django 4.2 as it is the current LTS version.
For postgresql support, mfext is providing version 3.1.4, but django 4.2 expects version 3.1.8 minimum, otherwise it won't start:
django.core.exceptions.ImproperlyConfigured: psycopg version 3.1.8 or newer is required; you have 3.1.4
Ref: https://docs.djangoproject.com/en/4.2/ref/databases/#postgresql-notes
Is it possible to upgrade psycopg to v3.1.8 or newer?
I am testing the migration from Django 3.2 to Django 4.2 as it is the current LTS version. For postgresql support, mfext is providing version 3.1.4, but django 4.2 expects version 3.1.8 minimum, otherwise it won't start:
django.core.exceptions.ImproperlyConfigured: psycopg version 3.1.8 or newer is required; you have 3.1.4
Ref: https://docs.djangoproject.com/en/4.2/ref/databases/#postgresql-notes
Is it possible to upgrade psycopg to v3.1.8 or newer?
Done in #1627 (v3.1.9)
make is not provided by mfext whereas it is an essential tool for metwork.
For me python-ldap is not a development tool but used in production.
It is provided by layer python3_devtools
but we usually install this layer only in development environment, as it is tools for "dev".
Is is possible to include ldap in a standard layer, not devtools ?
For me python-ldap is not a development tool but used in production. It is provided by layer
python3_devtools
but we usually install this layer only in development environment, as it is tools for "dev". Is is possible to include ldap in a standard layer, not devtools ?
Done by #1689 (python-ldap is moved in layer python3)
make is not provided by mfext whereas it is an essential tool for metwork.
--without-protobuf
required) : https://developers.google.com/protocol-buffers