Conversation
|
It looks like the generic (not postgres-specific) So, forgive me for asking, but is there any appetite for doing a major (backwards-compatible) release which drops support Django < 3, and older Python versions too? |
No, Django > 3 and Python >= 3.6 should be the way to go forward. I'm only concerned about migrating existing data from the third-party JSONField to the Django in-built one. |
|
Hey @adamcharnock , I've changed our Drone config and the Travis one to use Django>3 and Python>3.6. Please rebase your PR branch onto master. |
Happy to re-add formatting later, I just need to know which tool you used to do it. Also, maybe we'll move to poetry.
…rce_str()
Warning was:
RemovedInDjango40Warning: force_text() is deprecated in favor of force_str().
Warning was:
MigrationNotice: `XXX.filter_class` attribute should be renamed `filterset_class`. See: https://django-filter.readthedocs.io/en/master/guide/migration.html
Warning was:
RemovedInDjango40Warning: django.conf.urls.url() is deprecated in favor of django.urls.re_path().
Warning was:
RemovedInDjango40Warning: django.utils.translation.ugettext_lazy() is deprecated in favor of django.utils.translation.gettext_lazy().
…s fix)
Warning was:
RemovedInDjango40Warning: django.conf.urls.url() is deprecated in favor of django.urls.re_path().
…ting uses to reflect this
JWT library now requires the `algorithms` parameter to be specified when decoding. Silver uses the default algorithm when encoding (HS256), so I specified that for the decoding.
…ango 3. Making it longer.
NullBooleanField is deprecated. Support for it (except in historical migrations) will be removed in Django 4.0. HINT: Use BooleanField(null=True) instead. Adding migration for this and previous change to JSONField default values
?: (admin.W411) 'django.template.context_processors.request' must be enabled in DjangoTemplates (TEMPLATES) in order to use the admin navigation sidebar.
…json objects. Note added to CHANGELOG
adamcharnock
force-pushed
the
pr/01-django-3-python-3
branch
from
af0104d to
eda8766
Compare
|
@bogdanpetrea Rebase done |
|
Included and merged in a separate PR (#680). Thanks again! |
2 participants
As per #676, I've gone ahead and brought all dependencies up to date and got all tests passing. Note:
I'm sorry that this this is a big PR, but I don't really think there a practical way to do this incrementally. I've tried to make every commit pretty stand-alone though, so you should be able to walk through the individual commits and see what is going on. It's mostly very simple changes over a large number of files.