Project

General

Profile

Development #75590

supprimer les warnings dus au passage à django 3.2

Added by Lauréline Guérin 2 months ago. Updated about 2 months ago.

Status:
Solution déployée
Priority:
Normal
Category:
-
Target version:
-
Start date:
20 March 2023
Due date:
% Done:

0%

Estimated time:
Patch proposed:
No
Planning:
No

Description

Encore un peu:

app.Model: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'.
    HINT: Configure the DEFAULT_AUTO_FIELD setting or the AppConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'.
app.Model.field: (fields.W904) django.contrib.postgres.fields.JSONField is deprecated. Support for it (except in historical migrations) will be removed in Django 4.0.
    HINT: Use django.db.models.JSONField instead.
app.Model.field: (fields.W903) NullBooleanField is deprecated. Support for it (except in historical migrations) will be removed in Django 4.0.
    HINT: Use BooleanField(null=True) instead.

History

#1

Updated by Robot Gitea 2 months ago

  • Status changed from Nouveau to Solution proposée

Lauréline Guérin (lguerin) a ouvert une pull request sur Gitea concernant cette demande :

#2

Updated by Robot Gitea 2 months ago

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

Benjamin Dauvergne (bdauvergne) a approuvé une pull request sur Gitea concernant cette demande :

#3

Updated by Robot Gitea 2 months ago

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

Lauréline Guérin (lguerin) a mergé une pull request sur Gitea concernant cette demande :

#4

Updated by Valentin Deniaud 2 months ago

(pour info la correction était déjà dans #75446, effectuée automatiquement par la montée de version cible de django-upgrade)

#5

Updated by Transition automatique about 2 months ago

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

Also available in: Atom PDF