Skip to content
This repository has been archived by the owner on Mar 10, 2020. It is now read-only.

runserver help output is mangled #102

Closed
davidism opened this issue Jun 15, 2014 · 0 comments
Closed

runserver help output is mangled #102

davidism opened this issue Jun 15, 2014 · 0 comments

Comments

@davidism
Copy link

./manage.py runserver --help shows the following for the -r option:

  -r, --reload          monitor Python files for changes (not 100{'const':
                        True, 'help': 'monitor Python files for changes (not
                        100% safe for production use)', 'option_strings':
                        ['-r', '--reload'], 'dest': 'use_reloader',
                        'required': False, 'nargs': 0, 'choices': None,
                        'default': None, 'prog': 'tick runserver',
                        'container': <argparse._ArgumentGroup object at
                        0x7f6d9f75ab90>, 'type': None, 'metavar': None}afe for
                        production use)

The % in "100% safe" is not escaped properly.

wjt added a commit to wjt/flask-script that referenced this issue Jul 2, 2014
argparse `%`-formats your help strings with a dictionary containing `prog` and a variety of other things. So `% s` is interpreted as "string, padded with spaces to no minimum width".

Fixes smurfix#102.
wjt added a commit to wjt/flask-script that referenced this issue Jul 2, 2014
argparse %-formats your help strings with a dictionary containing 'prog'
and a variety of other things. So '% s' is interpreted as "string,
padded with spaces to no minimum width".

Fixes smurfix#102.
wjt added a commit to wjt/flask-script that referenced this issue Jul 17, 2015
argparse %-formats your help strings with a dictionary containing 'prog'
and a variety of other things. So '% s' is interpreted as "string,
padded with spaces to no minimum width".

Fixes smurfix#102.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants