python - Why do I still have optparse being used in Django v1.7.4? -

argparse is the device Django (allegedly) to parse the command line, and according to .

However, now nine months have elapsed, and when I see the base demand announcement, see:

  Make_option, optionParser ... Option_list = (make_option ('- v', '--verbosity', action = 'store', destination = 'verbosity', default = '1', type = 'option', option = ['0', '1 0 = Minimum output, 1 = normal output, 2 = verbose output, 3 = very verbose output '), make-options (' - settings', help = '' Python path for a settings module, such as "myproject.settings. Main ". If this is not provided, then the DNANGOSSTISMAAMAMDE environment variable will be used. '), Make-option (' - PythonPoth ',' help '= DIREAC Make_option ('- traceback', verb = 'store_true', help = 'rais e exception'), make_option ('- no-color'), to add the character to the Python path, such as "/ home / djangoprojects / myproject" , Action = 'store_true', dest = 'no_color', default = false, help = "do not color the command output."),)  

when using Django argparse 1.7 in ?

v1.8b2 has been tagged to your commitment to the stable and for the branches Looking at the source code it looks like the argparse v1.8 will be presented as the default. However, see also for v1.8.

However, optparse will be created as a fallback option (to allow support released before version 2.7 / 3.2 for Python versions) until Django v2 will not be there. According to:

optparse should be supported during the release of Django 1.8 / 1.9