#30872: ManagementUtility.fetch_command prints "No Django settings specified."
even
if they are.
-------------------------------------+-------------------------------------
Reporter: Keryn Knight | Owner: Carlton
Type: | Gibson
Cleanup/optimization | Status: assigned
Component: Core (Management | Version: master
commands) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson):
* status: new => assigned
* owner: nobody => Carlton Gibson
* easy: 0 => 1
* stage: Unreviewed => Accepted
Comment:
Hi Keryn.
`startproject` and `startapp` (at least) can bypass that `if
settings.configured` check in `execute()` that you link, so we can get to
`fetch_command()` without them in play.
As it is, I take re-triggering of the `You must either define the
environment variable DJANGO_SETTINGS_MODULE or call settings.configure()`
error to be targeting the ''usual'' case. But, I think you're right, the
message is wrong: `No Django settings specified.` — you might well have
manually called `settings.configure()`. (So a small clean up there.)
[https://github.com/django/django/pull/11903 PR].
--
Ticket URL: <https://code.djangoproject.com/ticket/30872#comment:2>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.9720beee07d3a89f5f468226a379866b%40djangoproject.com.
