Django

Code

Ticket #8639 (closed: fixed)

Opened 2 years ago

Last modified 8 months ago

startproject is disabled if a settings module is specified

Reported by: whiskybar Assigned to: nobody
Milestone: 1.0 Component: Documentation
Version: SVN Keywords: django-admin
Cc: Triage Stage: Unreviewed
Has patch: 1 Needs documentation: 0
Needs tests: 0 Patch needs improvement: 0

Description

I believe the documentation to django-admin.py should say the command startproject will be disabled if a settings module has been specified on the command-line or $DJANGO_SETTINGS_MODULE has been set. I have spent hours browsing docs, tickets, googlegroups, and irc to see where the command startproject has gone and why no one actually complains.

Finally, I came across a very well hidden documentation string at get_commands() in django/core/management/init.py which explained the problem to me.

Attachments

django-admin.diff (410 bytes) - added by whiskybar on 08/28/08 07:38:44.

Change History

08/28/08 07:38:44 changed by whiskybar

  • attachment django-admin.diff added.

08/28/08 07:44:51 changed by russellm

  • status changed from new to closed.
  • needs_better_patch changed.
  • resolution set to duplicate.
  • needs_tests changed.
  • needs_docs changed.

Duplicate of #8329.

08/29/08 00:06:30 changed by kmtracey

#8329 looks to be geared toward making the error message more explanatory. Given that it has been moved to post-1.0, would it make sense to reopen this & get the little doc fix suggested here into 1.0? I think #8666 is another using tripping over this.

08/29/08 00:10:24 changed by mtredinnick

  • milestone set to 1.0.

Yes, we have to do something here. I got bitten by this the other day, too, and had a momentary "huh?!" moment.

08/29/08 00:10:29 changed by mtredinnick

  • status changed from closed to reopened.
  • resolution deleted.

08/30/08 03:59:37 changed by ubernostrum

  • status changed from reopened to closed.
  • resolution set to fixed.

(In [8740]) Fixed #8639; documented the fact that the "startproject" command is invalid when fed an existing project's settings

12/23/09 02:15:03 changed by anonymous

  • status changed from closed to reopened.
  • resolution deleted.

I don't consider this fixed. Why can't it have a statement when I try to use the command that I have that shows which app is already in context to let me know, instead "unknown command." It's not an unknown command, it's all over the docs. It's a command that's disabled because an existing app's settings are being used and the command line response should point that out including indicating what that current project's name is.

12/23/09 03:05:58 changed by russellm

  • status changed from reopened to closed.
  • resolution set to fixed.

This *was* fixed to the satisfaction of the core team in [8740]. Please don't reopen tickets that have been closed by the core. If you disagree with a decision that has been made, ask on django-dev.

Add/Change #8639 (startproject is disabled if a settings module is specified)




Change Properties
Action