Conflicting 'verbose' and 'verbosity' since django r9110

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Get django r9110
(http://code.djangoproject.com/changeset?new=django%2Ftrunk%2Fdjango%409110&old=
django%2Ftrunk%2Fdjango%409103)
2. Try to run ./manage runjobs --help

My patch fixes this issue, by removing all conflicted options from the 'app'.

Original issue reported on code.google.com by svetlyak...@gmail.com on 3 Oct 2008 at 4:12

Attachments:

• 0001-Fixed-errors-on-duplicate-verbose-options-caused.patch

[GoogleCodeExporter]

Original comment by v.oostv...@gmail.com on 15 Oct 2008 at 8:38

• Changed state: Accepted

[GoogleCodeExporter]

i would like to solve this in a version agnostic way if possible.

just removing the 'verbose' options would not play nice with django-1.0 users.
besides r9110 stores it as a 'verbosity' keyword where most commands use 
'verbose'.

Original comment by v.oostv...@gmail.com on 15 Oct 2008 at 11:03

[GoogleCodeExporter]

fixed in svn r141

including backwards compatibility

Original comment by v.oostv...@gmail.com on 15 Oct 2008 at 11:04

[GoogleCodeExporter]

Original comment by v.oostv...@gmail.com on 15 Oct 2008 at 11:04

• Changed state: Fixed

[GoogleCodeExporter]

I'm still seeing this error, kind of.  When I run:

./manage.py runscript --help I get

"""
Traceback (most recent call last):
  File "./manage.py", line 11, in <module>
    execute_manager(settings)
  File "/Users/phaedo/django_src/django/core/management/__init__.py", line 340, in execute_manager
    utility.execute()
  File "/Users/phaedo/django_src/django/core/management/__init__.py", line 295, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/Users/phaedo/django_src/django/core/management/base.py", line 192, in run_from_argv
    parser = self.create_parser(argv[0], argv[1])
  File "/Users/phaedo/django_src/django/core/management/base.py", line 175, in create_parser
    option_list=self.option_list)
  File "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/optparse.py", line 1208, in 
__init__
    add_help=add_help_option)
  File "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/optparse.py", line 1250, in 
_populate_option_list
    self.add_options(option_list)
  File "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/optparse.py", line 1033, in 
add_options
    self.add_option(option)
  File "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/optparse.py", line 1014, in 
add_option
    self._check_conflict(option)
  File "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/optparse.py", line 989, in 
_check_conflict
    option)
optparse.OptionConflictError: option --verbosity: conflicting option string(s): 
--verbosity
"""

Original comment by clintec...@gmail.com on 20 Oct 2008 at 8:47

[GoogleCodeExporter]

It looks like the Runscript command was simply missed.  I've attached a patch

Original comment by clintec...@gmail.com on 20 Oct 2008 at 9:30

Attachments:

• django_extensions_runscript.diff

[GoogleCodeExporter]

fixed in svn

Original comment by v.oostv...@gmail.com on 23 Oct 2008 at 6:38