Opened 15 years ago

Closed 15 years ago

#823 closed bug (Fixed)

deluge -u console -a "config --set [attribute] -1.0" fails

Reported by: Owned by: andar
Priority: minor Milestone:
Component: Unknown Version: 1.1.2
Keywords: Cc:


Attempting to use the proposed work around for lack of scheduling as found here: Adapting the technique to set attributes unlimited (ie, -1 or -1.0 depending on data type) fails. Easy enough to just use a ridiculously large value, but behaviour should match with GUI and the core.conf contents. Following output to the console:

File "/usr/bin/deluge", line 8, in <module>

load_entry_point('deluge==1.1.3', 'console_scripts', 'deluge')()

File "/var/lib/python-support/python2.5/deluge/", line 120, in start_ui

UI(options, args, options.args)

File "/var/lib/python-support/python2.5/deluge/ui/", line 63, in init

ui = ConsoleUI(ui_args).run()

File "/var/lib/python-support/python2.5/deluge/ui/console/", line 127, in init


File "/var/lib/python-support/python2.5/deluge/ui/console/", line 191, in onecmd

options, args = parser.parse_args(args)

File "/usr/lib/python2.5/", line 1387, in parse_args


File "/usr/lib/python2.5/", line 1385, in parse_args

stop = self._process_args(largs, rargs, values)

File "/usr/lib/python2.5/", line 1429, in _process_args

self._process_short_opts(rargs, values)

File "/usr/lib/python2.5/", line 1512, in _process_short_opts

raise BadOptionError?(opt)

optparse.BadOptionError?: no such option: -1

Change History (2)

comment:1 Changed 15 years ago by

  • Cc added

comment:2 Changed 15 years ago by andar

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

Fixed in [6023]

Note: See TracTickets for help on using tickets.