#32664: Cannot run makemigrations management command without a SECRET_KEY
-------------------------------------+-------------------------------------
Reporter: François Freitag | Owner: François
Type: | Freitag
Cleanup/optimization | Status: closed
Component: Core (Other) | Version: dev
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak):
Replying to [comment:12 Michael Manganiello]:
> Has it been considered to port this fix to the 3.2 branch? As it is
today, `PasswordResetTokenGenerator` initialization breaks the execution
of management commands when trying to follow the recommendation provided
by the release notes.
This release note is rather about custom management commands. It's
arguable (as you see from the above discussion) that build-in commands
that rely on `django.contrib.auth` module should not require the
`SECRET_KEY`. However, we decided to do the best we can to make
`SECRET_KEY` validation lazy also for built-in management commands. This
ticket is a cleanup not a bug in 948a874425e7d999950a8fa3b6598d9e34a4b861
that's why it doesn't qualify for a backport.
--
Ticket URL: <https://code.djangoproject.com/ticket/32664#comment:13>
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/073.d3a8514d12c8f8d2bf402584fa16c528%40djangoproject.com.
