#34436: `makemigrations --check` fails with error code 1 if system checks
identify
warnings
-------------------------------+--------------------------------------
Reporter: James Addison | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 4.2
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* resolution: => invalid
Comment:
Replying to [ticket:34436 James Addison]:
> Note that both `manage.py makemigrations --check` and `manage.py check`
are provided above for clarity.
>
> These are deprecation warnings (to be removed in Django 5.1). I think
this management command should not be erroring out in relation to these at
this point in time.
`check` cannot succeed when warnings are raised, so a non-zero return code
is expected. You can always use the
[https://docs.djangoproject.com/en/4.1/ref/settings/#std-setting-
SILENCED_SYSTEM_CHECKS SILENCED_SYSTEM_CHECKS] setting to ignore them.
--
Ticket URL: <https://code.djangoproject.com/ticket/34436#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070187154ba558-cbe3e382-1cb5-475a-ac66-2d8e10d2493c-000000%40eu-central-1.amazonses.com.
