Opened 2 years ago

Closed 2 years ago

Last modified 2 years ago

#20256 closed Bug (fixed)

Incorrect text in startproject command line help

Reported by: anonymous Owned by: n0nam3
Component: Core (Management commands) Version: master
Severity: Normal Keywords:
Cc: Triage Stage: Ready for checkin
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: yes UI/UX: no


The command line help for startproject startproject --help is

  --template=TEMPLATE   The dotted import path to load the template from.

The directory need not to be importable and should not be dotted but a path with "/".

--- a/django/core/management/
+++ b/django/core/management/
@@ -43,7 +43,7 @@ class TemplateCommand(BaseCommand):
     option_list = BaseCommand.option_list + (
                     action='store', dest='template',
-                    help='The dotted import path to load the template from.'),
+                    help='The path or url to load the template from.'),
         make_option('--extension', '-e', dest='extensions',
                     action='append', default=['py'],
                     help='The file extension(s) to render (default: "py"). '

Attachments (1)

incorrect_text.diff (737 bytes) - added by n0nam3 2 years ago.
patch for ticket fix

Download all attachments as: .zip

Change History (7)

comment:1 Changed 2 years ago by bmispelon

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Triage Stage changed from Unreviewed to Accepted


Thanks for the report, it does appear that the help text is incorrect.

For reference, here's the method where the project/app template handling happens:

As for your proposed correction, it looks good to me, though I would write "URL" instead of "url".

comment:2 Changed 2 years ago by n0nam3

  • Owner changed from nobody to n0nam3
  • Status changed from new to assigned

Changed 2 years ago by n0nam3

patch for ticket fix

comment:3 Changed 2 years ago by n0nam3

  • Triage Stage changed from Accepted to Ready for checkin

comment:4 Changed 2 years ago by bmispelon

The patch looks good so I'm leaving it as "Ready for checkin" but next time you shouldn't mark your own patch as RFC.



comment:5 Changed 2 years ago by claudep

  • Resolution set to fixed
  • Status changed from assigned to closed

comment:6 Changed 2 years ago by anonymous

I also made a pull request in Github. Should I have marked the patch as "Fixed on branch"? I'll close the pull request now that it's fixed.

Note: See TracTickets for help on using tickets.
Back to Top