Re: Reverting Django 3.1. to Django 3.0.6 raises "binascii.Error: Incorrect padding".

2020-05-15 Thread f.holop
Adam Johnson - Fri, 15 May 2020 at 17:53:21 > At least two of the major database servers that Django supports, PostgreSQL > and MySQL, provide zero downgrade-ability. It's too hard for them to do. while this is now officially true for both MariaDB and MySQL, until recentlyish it was possible to do

Re: Reverting Django 3.1. to Django 3.0.6 raises "binascii.Error: Incorrect padding".

2020-05-15 Thread Adam Johnson
Hi Uri Smooth upgrade-ability is hard. Smooth downgrade-ability is even harder. It also imposes a tax on development, and can slow the roll out of new features as they can need roll out over multiple versions. I agree both would be nice to have, but given the limited engineering resources for Dj

Reverting Django 3.1. to Django 3.0.6 raises "binascii.Error: Incorrect padding".

2020-05-15 Thread אורי
Hi, I submitted this ticket today and it was closed: https://code.djangoproject.com/ticket/31592 I think Django should handle downgrading versions without raising exceptions. If objects (such as sessions) are invalid because of downgrading, they should be deleted automatically. It may happen that