Plugin debugging workflow?

[PlanetLotus]

I'm new to Deluge and I'm trying to create a plugin for the first time. I'm having trouble finding a convenient way of debugging my plugin. Does anyone recommend a workflow for this? So far, troubleshooting a bug in my code involves the following steps:

1. Make a code change
2. Run

Code: Select all

python setup.py bdist_egg

3. Re-copy the output egg to my deluge daemon's plugin directory
4. Restart the deluge daemon
5. Look at daemon's logs for errors

Is there an easier way? I could probably script this somewhat, but I figured I'm probably just not seeing an easier way to do this.

I'm also interested in Deluge development in general. I figured I'd try writing a plugin first before I got more involved in the source. Looks like 2.0 is in development which is exciting. Are more developers needed? Depending on how difficult it is to get started, I may be interested in dedicating some time to this. Thanks!

[Cas]

There should be a script called create_dev_link.sh which will install a plugin link in the plugins directory that will help you with development.

We always welcome more developers

[PlanetLotus]

Oh nice, thanks much!

I'll keep hacking away and see how far I get. Off-topic, but after I got this far, I noticed the ThinClient isn't doing so hot on my RPi3 with ~550 torrents on it not sure if this can be easily improved. I'd certainly be interested in working on performance optimizations...sounds fun! But if it's impractical, I may have to switch torrent clients...will see! I hope deluge works out!

I know one of the goals of 2.0 is performance improvements. Is there a rough timeline (say, weeks/months/years) on a 2.0 release?

Thanks again!