Re: Status of 3.1 release blockers.

Thank you. אורי u...@speedy.net On Fri, Aug 7, 2020 at 8:24 AM Mariusz Felisiak wrote: > > *> After I signed up and logged in, I reverted to Django 3.0, and then one > user was logged out (who should be logged in) and another user got the > exception `Incorrect padding` (from > `base64.b64deco

Re: Status of 3.1 release blockers.

*> After I signed up and logged in, I reverted to Django 3.0, and then one user was logged out (who should be logged in) and another user got the exception `Incorrect padding` (from `base64.b64decode(session_data.encode('ascii'))`). * This is a separate issue, see #31864

Re: Critical hints about Django migrations

While I agree with some of the author's points, I think a critical piece of context is that Django migrations are designed for the 90% case - i.e., people who just want something to work on a small scale and don't need to worry about many aspects of the database yet. Like all parts of Django, i

Critical hints about Django migrations

HI all, I would suggest reading this interesting article by Daniele Varrazzo (the maintainer of psycopg2 and creator of psycopg3) on Django migrations. It contains some criticisms but I also think some interesting hints for improving Django ORM : https://www.varrazzo.com/blog/2020/07/25/surviving

Re: FK field caching behavior change between 1.11.x and 2.x

Unless someone objects to adjusting Model.__copy__(self) to deal with self._state.fields_cache I'd say we should create a ticket about it. Would you be interested in creating the ticket and possibly submitting a patch Gert? Simon Le mardi 4 août 2020 à 21:23:47 UTC-4, Alex Hill a écrit : > I