Project

General

Profile

Development #49283

Compatibilité django 2.2

Added by Emmanuel Cazenave 10 months ago. Updated 8 months ago.

Status:
Solution déployée
Priority:
Normal
Category:
-
Target version:
-
Start date:
09 Dec 2020
Due date:
% Done:

0%

Estimated time:
Patch proposed:
Yes
Planning:
No

Description

Mais on doit garder python2, donc les cibles seraient py2-django111, py3-django111, py3-django2.2, ça parait un peu scabreux, mais je vais voir ce que ça donne.


Files


Related issues

Related to Publik - Project management #49998: compatibilité django 2.2Nouveau09 Jan 202131 Mar 2021

Actions
Blocked by Passerelle - Development #49188: préparer la compatibilité django 2.2Solution déployée07 Dec 2020

Actions
Blocks Publik Installation Développeur - Development #49999: tourner avec django 2.2Solution déployée09 Jan 202101 Mar 2021

Actions

Associated revisions

Revision ba6bb639 (diff)
Added by Emmanuel Cazenave 9 months ago

use contrib.auth class based views (#49283)

Revision 6539d8dd (diff)
Added by Emmanuel Cazenave 9 months ago

declare a manager on Role (#49283)

Revision 7eedc0bb (diff)
Added by Emmanuel Cazenave 9 months ago

use the new names of URL related class (#49283)

Revision 446788ec (diff)
Added by Emmanuel Cazenave 9 months ago

change command parser option or invocation (#49283)

To be compliant with https://code.djangoproject.com/ticket/27787 : parser arguments now gets introspected when using call_command.

Revision cd54c56f (diff)
Added by Emmanuel Cazenave 9 months ago

set CSRF_COOKIE_SAMESITE to None (#49283)

Revision 41d847ab (diff)
Added by Emmanuel Cazenave 9 months ago

use real string in migration (#49283)

Revision 1977c3ed (diff)
Added by Emmanuel Cazenave 9 months ago

run tests against django 2.2 (#49283)

History

#1

Updated by Emmanuel Cazenave 10 months ago

#3

Updated by Emmanuel Cazenave 10 months ago

  • Assignee deleted (Emmanuel Cazenave)
#4

Updated by Emmanuel Cazenave 9 months ago

  • Assignee set to Emmanuel Cazenave
  • Status changed from Nouveau to En cours
#5

Updated by Frédéric Péters 9 months ago

#6

Updated by Emmanuel Cazenave 9 months ago

Les choses notables :

  • 0004 : django plus stricte sur les invocations de commandes via call_command, il faut que le parser soit raccord avec les arguments passés à call_command
  • 0005 : suite de #45667, en django 2.2 il y a maintenant par défaut un CSRF_COOKIE_SAMESITE qui vaut 'lax'
  • 0006 : je n'ai pas l'explication complète mais il y a du y avoir des changements dans le commande de migration en django 2.x, résultat des courses dans les AttributeDefinition créé sans spécifier de kind, ça se retrouvait avec "b\'string\'" comme valeur pour cet attribut
#7

Updated by Emmanuel Cazenave 9 months ago

Et j'oubliais le point évoqué par mail sur django-tenant-schema, c'est 0004 qui règle l'affaire, comme on a on notre propre commande migrate_schemas c'est dans notre périmètre (mais j'avais cru que la mise à jour de django-tenant-schema nécessaire parce que la trace passe par tenant_schema.py::TenantMixin.create_schema qui invoque la commande migrate_schemas).

#8

Updated by Emmanuel Cazenave 9 months ago

#9

Updated by Frédéric Péters 9 months ago

  • Status changed from Solution proposée to Solution validée
#10

Updated by Emmanuel Cazenave 9 months ago

  • Status changed from Solution validée to Résolu (à déployer)
commit 1977c3ed9574b6d7c3bde29ea941fcfba313a35c
Author: Emmanuel Cazenave <ecazenave@entrouvert.com>
Date:   Tue Jan 12 14:52:39 2021 +0100

    run tests against django 2.2 (#49283)

commit 41d847ab04394b4aee4fab35c4560e536be97bb5
Author: Emmanuel Cazenave <ecazenave@entrouvert.com>
Date:   Tue Jan 12 13:56:08 2021 +0100

    use real string in migration (#49283)

commit cd54c56f8c802c13d708fb25e2a350cfc0ff5479
Author: Emmanuel Cazenave <ecazenave@entrouvert.com>
Date:   Tue Jan 12 11:34:27 2021 +0100

    set CSRF_COOKIE_SAMESITE to None (#49283)

commit 446788ece62e8d6b4c06653539820de52002ca8e
Author: Emmanuel Cazenave <ecazenave@entrouvert.com>
Date:   Mon Jan 11 17:33:42 2021 +0100

    change command parser option or invocation (#49283)

    To be compliant with https://code.djangoproject.com/ticket/27787 : parser arguments now gets introspected when using call_command.

commit 7eedc0bbccca9059024a500f81ee1b7f0f3a569c
Author: Emmanuel Cazenave <ecazenave@entrouvert.com>
Date:   Wed Jan 6 17:14:33 2021 +0100

    use the new names of URL related class (#49283)

commit 6539d8ddbf446a9c669f0360c514312c4c7092d1
Author: Emmanuel Cazenave <ecazenave@entrouvert.com>
Date:   Wed Jan 6 12:01:41 2021 +0100

    declare a manager on Role (#49283)

commit ba6bb6398ba50d543b8fb4c9fa61cf02a9b60b37
Author: Emmanuel Cazenave <ecazenave@entrouvert.com>
Date:   Wed Dec 9 11:17:54 2020 +0100

    use contrib.auth class based views (#49283)
#11

Updated by Frédéric Péters 8 months ago

  • Status changed from Résolu (à déployer) to Solution déployée

Also available in: Atom PDF