[Deluge] #3081: Move baseargparser out of deluge/ui

2 views
Skip to first unread message

Deluge

unread,
Jun 28, 2017, 8:24:37 AM6/28/17
to delug...@googlegroups.com
#3081: Move baseargparser out of deluge/ui
-------------------+---------------------------
Reporter: Cas | Owner:
Type: bug | Status: new
Priority: minor | Milestone: 2.0
Component: Core | Version: develop (git)
Keywords: |
-------------------+---------------------------
Currently the baseargparser.py file resides in `deluge/ui` however since
`daemon_entry` imports this I think it would make more sense to move it to
top-level `deluge`. This would remove the reliance of `ui` code in `core`.

Perhaps consider renaming to `argparser_base.py`.

Also `set_dummy_trans` will need moved to `deluge/common.py` or
`baseargparser.py`

--
Ticket URL: <http://dev.deluge-torrent.org/ticket/3081>
Deluge <http://deluge-torrent.org/>
Deluge Project

Deluge

unread,
Oct 12, 2018, 7:13:52 AM10/12/18
to delug...@googlegroups.com
#3081: Move baseargparser out of deluge/ui
--------------------+---------------------------
Reporter: Cas | Owner: DjLegolas
Type: bug | Status: accepted
Priority: minor | Milestone: 2.0.0

Component: Core | Version: develop (git)
Resolution: | Keywords:
--------------------+---------------------------
Changes (by DjLegolas):

* owner: => DjLegolas
* status: new => accepted


Comment:

Look at PR [[https://github.com/deluge-torrent/deluge/pull/217|217]].

--
Ticket URL: <https://dev.deluge-torrent.org/ticket/3081#comment:2>

Deluge

unread,
May 11, 2019, 3:51:20 PM5/11/19
to delug...@googlegroups.com
#3081: Move baseargparser out of deluge/ui
--------------------+---------------------------
Reporter: Cas | Owner: DjLegolas
Type: bug | Status: closed
Priority: minor | Milestone: 2.0.0

Component: Core | Version: develop (git)
Resolution: Fixed | Keywords:
--------------------+---------------------------
Changes (by Cas):

* status: accepted => closed
* resolution: => Fixed


Comment:

Fixed: [d417c4b0f9fd0]

--
Ticket URL: <https://dev.deluge-torrent.org/ticket/3081#comment:3>

Reply all
Reply to author
Forward
0 new messages