Deluge
Custom Query (2445 matches)
Results (163 - 165 of 2445)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #3083 | Fixed | utf8_encoded missing for backward compatibility | stokbaek | |
| Description |
Trying to use YaRSS2 with deluge 2.0b2.dev10 gives following error when trying to activate plugin Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/deluge/pluginmanagerbase.py", line 145, in enable_plugin
instance = cls(plugin_name.replace('-', '_'))
File "build/bdist.linux-x86_64/egg/yarss2/__init__.py", line 40, in __init__
from core import Core as CorePluginClass
File "build/bdist.linux-x86_64/egg/yarss2/core.py", line 15, in <module>
File "build/bdist.linux-x86_64/egg/yarss2/rssfeed_scheduler.py", line 19, in <module>
File "build/bdist.linux-x86_64/egg/yarss2/torrent_handling.py", line 17, in <module>
ImportError: cannot import name utf8_encoded
|
|||
| #3082 | Fixed | Use translated strings from 1.X in 2.X | jony0008 | |
| Description |
Hi, I saw that it is possible to start to translate deluge 2.0 (https://translations.launchpad.net/deluge/2.0/+translations) but zero strings are translated. Could already translated strings from 1.X be used so that not all strings have to be translated again for 2.0? |
|||
| #3081 | Fixed | Move baseargparser out of deluge/ui | DjLegolas | Cas |
| Description |
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 |
|||
Note: See TracQuery
for help on using queries.
