#7762: management prints full path to script when command error occurs
--------------------------------------+-------------------------------------
Reporter: miracle2k | Owner: nobody
Status: reopened | Milestone:
Component: django-admin.py | Version: SVN
Resolution: | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
--------------------------------------+-------------------------------------
Changes (by miracle2k):
* status: closed => reopened
* resolution: wontfix =>
Comment:
Hm, are you sure Malcolm? The *basename(sys.argv[0])* approach is also
used in management.__init__ when handling errors not specific to a certain
command:
{{{
[EMAIL PROTECTED]:/$ /usr/bin/django-admin.py help startapp 2>&1| head -n 1
Usage: django-admin.py startapp [options] [appname]
[EMAIL PROTECTED]:/$ /usr/bin/django-admin.py startapp --invalid 2>&1| head -n
1
Usage: /usr/bin/django-admin.py startapp [options] [appname]
[EMAIL PROTECTED]:/$
}}}
That seems like an inconsistency both on Windows and *nix. ''basename()''
should return the actual filename (presumably what we would want) on all
platforms.
--
Ticket URL: <http://code.djangoproject.com/ticket/7762#comment:2>
Django Code <http://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 post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
