django shouldn't delete the startproject command

[IanHolsman]

but put a warning in it's place

[IanHolsman]

patch to add a warning

[Russell Keith-Magee]

No problem with the idea here, but there is a problem with the implementation. Using this approach, startproject will appear on the list of valid commands when you run django-admin.py help.

Also, as a matter of style, I would also be temped to refactor InvalidStartProjectContextCommand into a more generic DisabledCommand that can be configured with a generic message explaining why a command has been disabled. We only have one disabled command right now, but I can see that it could be useful in other circumstances.

Tests integrated with admin_scripts would also be desirable.

[Adrian Holovaty]

Another (granted, small) problem with this patch: the error message is a bit awkward. I'd rephrase it like this --

The "startproject" command is disabled, because you've already defined a project. To create a new project, unset your DJANGO_SETTINGS_MODULE environment variable.

[(none)]

Milestone post-1.0 deleted

[msabramo]

Patch to display warning when "startproject" subcommand is disabled because of DJANGO_SETTINGS_MODULE

[msabramo]

My patch takes a bit of a different approach from Ian's. With it, "startproject" is not displayed as an available subcommand (like the current behavior), but a warning is printed.

Ian's patch is interesting. I hadn't seen it before I created my own. I can't decide whether I like his (ideally with the changes suggested by Adrian and Russell) or mine better.

I know I don't like silently removing the command.

[msabramo]

Any comments on my patch (or Ian's)? If it needs some tweaks, let me know.

[Jannis Leidel]

Fixed in r16964.