Pedro Algarvio 6c99204828 The GtkUi's connection manager now has the ability to edit existing host entries besides adding and deleting them. ...

It also asks for a password prior to attemting to connect in case the password is null, this alows host entries not to store the passwords on file like it has done so far.
NOTE: This is not yet the desired behaviour, ie, the daemon should simply complain if the authentication details are incomplete and the client should act accordingly. I had an issue with this though, I catched the errback the daemon was sending, asked the user for the password and re-tried to authenticate again. However, twisted always locked when I tried this. I'm investigating it.

2011-04-22 11:22:19 +01:00

..

core

The GtkUi's connection manager now has the ability to edit existing host entries besides adding and deleting them.

2011-04-22 11:22:19 +01:00

data

Sidebar: Enabled strings for translation and added icons to Trackers filter

2011-02-11 22:10:00 +00:00

i18n

Update translation template

2010-05-03 11:50:16 -07:00

plugins

Let's use what the stdlib provides us. Use email.utils.formatdate instead of strftime() a datetime object.

2011-04-14 09:29:40 +01:00

scripts

Swhiched the old style logging, ie, a single logger for all logging output to several loggers. This brings the ability to tweak the logging levels for each of the loggers, ie, we can have the "deluge" logger be at the ERROR level while having "deluge.core" at the DEBUG level, meaning we will only see log message for all of the deluge loggers above the ERROR level while still having all messages above the DEBUG level for the "deluge.core" logger and it's children. This kind of tweak can be achieved by adding a file named "logging.conf" to deluge's config dir and this is explained on the deluge.log.tweak_logging_levels function.

2010-12-06 11:20:22 +00:00

tests

fix the client tests albeit in an ultra hacky way

2011-04-21 10:41:00 +01:00

ui

The GtkUi's connection manager now has the ability to edit existing host entries besides adding and deleting them.

2011-04-22 11:22:19 +01:00

__init__.py

Big code clean-up and some refactoring. Added docstrings but more are

2007-08-26 14:34:50 +00:00

__rpcapi.py

remove the docs/build folder

2009-07-22 20:50:06 +00:00

_libtorrent.py

update the required libtorrent version to 0.14.9 to match 1.2-stable

2010-02-22 11:59:09 +00:00

bencode.py

Fix bdecoding some torrent files

2009-01-14 01:15:00 +00:00

common.py

Remove some imports that are no longer neccessary

2011-02-23 11:21:47 -08:00

component.py

Swhiched the old style logging, ie, a single logger for all logging output to several loggers. This brings the ability to tweak the logging levels for each of the loggers, ie, we can have the "deluge" logger be at the ERROR level while having "deluge.core" at the DEBUG level, meaning we will only see log message for all of the deluge loggers above the ERROR level while still having all messages above the DEBUG level for the "deluge.core" logger and it's children. This kind of tweak can be achieved by adding a file named "logging.conf" to deluge's config dir and this is explained on the deluge.log.tweak_logging_levels function.

2010-12-06 11:20:22 +00:00

config.py

Merge branch 'master' into improved-logging

2010-12-13 12:31:20 +00:00

configmanager.py

Added missing import.

2010-12-28 01:26:25 +00:00

decorators.py

Add decorators module and test file

2010-05-04 04:33:21 +10:00

error.py

Add get_free_space() to core

2009-07-24 23:36:43 +00:00

event.py

Revert "Fixed "PluginEnabledEvent" and "PluginDisabledEvent" the argument cannot be called name since that should contain the event name."

2011-02-23 11:01:59 -08:00

httpdownloader.py

Swhiched the old style logging, ie, a single logger for all logging output to several loggers. This brings the ability to tweak the logging levels for each of the loggers, ie, we can have the "deluge" logger be at the ERROR level while having "deluge.core" at the DEBUG level, meaning we will only see log message for all of the deluge loggers above the ERROR level while still having all messages above the DEBUG level for the "deluge.core" logger and it's children. This kind of tweak can be achieved by adding a file named "logging.conf" to deluge's config dir and this is explained on the deluge.log.tweak_logging_levels function.

2010-12-06 11:20:22 +00:00

log.py

Add "none" as a log level to support quieting the logging messages. Refs #1470.

2011-01-02 16:06:28 +00:00

main.py

add patch from #1473

2011-02-04 19:43:27 +00:00

maketorrent.py

Remove some imports that are no longer neccessary

2011-02-23 11:21:47 -08:00

metafile.py

Swhiched the old style logging, ie, a single logger for all logging output to several loggers. This brings the ability to tweak the logging levels for each of the loggers, ie, we can have the "deluge" logger be at the ERROR level while having "deluge.core" at the DEBUG level, meaning we will only see log message for all of the deluge loggers above the ERROR level while still having all messages above the DEBUG level for the "deluge.core" logger and it's children. This kind of tweak can be achieved by adding a file named "logging.conf" to deluge's config dir and this is explained on the deluge.log.tweak_logging_levels function.

2010-12-06 11:20:22 +00:00

pluginmanagerbase.py

Swhiched the old style logging, ie, a single logger for all logging output to several loggers. This brings the ability to tweak the logging levels for each of the loggers, ie, we can have the "deluge" logger be at the ERROR level while having "deluge.core" at the DEBUG level, meaning we will only see log message for all of the deluge loggers above the ERROR level while still having all messages above the DEBUG level for the "deluge.core" logger and it's children. This kind of tweak can be achieved by adding a file named "logging.conf" to deluge's config dir and this is explained on the deluge.log.tweak_logging_levels function.

2010-12-06 11:20:22 +00:00

rencode.py

Remove some imports that are no longer neccessary

2011-02-23 11:21:47 -08:00