Modify

Ticket #439 (assigned defect)

Opened 4 years ago

Last modified 3 years ago

Command responses should examine management command name

Reported by: anonymous Owned by: andrew
Priority: trivial Milestone: 1.0
Component: commands Version: 0.7
Keywords: Cc:

Description

I use virtualenv, and don't have a ./manage.py file: this makes it easy to run commands from anywhere (and DJANGO_SETTINGS_MODULE is always set in my virtualenv shell).

However, the south admin commands still tell me to use ./manage.py migrate.

It would be great if they would know how the management command that is currently running was called, and suggest the call of the next command the same way.

Attachments

Change History

comment:1 Changed 4 years ago by andrew

  • Status changed from new to assigned
  • Milestone set to 1.0

Well, we can tell the name of the current command from sys.argv[0], but if you're using python, e.g. python manage.py, that only contains manage.py.

Still, it's worth implementing. Scheduling for 1.0.

View

Add a comment

Modify Ticket

Action
as assigned
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.