Olivier Dalang

will wait until django 3.2 is EOL (first trimester 2024), then drop support for python 3.6 altogether

You're right, in the case the database was correctly managed, that should never happen. But unfortunately, other cases are not uncommon (e.g. user made manual changes on the DB, or...

I agree with 3 assumptions, but then can't really follow on what you mean. To clarify : - In an ideal world (where your database are always in a consistent,...

Hmm actually it doesn't seem linked to newly added columns, but just to NULL values as if I run my script in two steps (first update the schema, then create...

Think I found the bug here : https://github.com/michaelsogos/pg-diff-api/pull/9

Oops I just saw I downloaded https://www.djangoproject.com/m/vms/djangocore-box-1.1.box , I misread the link and didn't make the difference between 1.1 and 1.11... Sorry for the noise !

No I found the link on the mailing list thread. But is the last version hosted somewhere else than on hashicorp's server ? They don't support resuming downloads (!!) making...

Ok it works better with the correct version, but I still run into some errors. ``` (vm) ~$ runtests35-mysql ``` returned ``` ERROR: py35-mysql: InvocationError: /usr/bin/python3 -m virtualenv --python /usr/bin/python3.5...

No. It looks it's the same error on that other issue, I didn't see it. I'll test again when I have a chance to download the new box.

Hi, Testing again with the last version, it now works with the following fixes : 1. enable symlink for the virtual machine (replace django-box_default_1474373922214_44815 by the VM name in VirtualBox)...