Deluge
I just wanted to add to this that I am very happy with Deluge 2.2.0 + libtorrent 1.2.19. Some quirks I experienced, most notably a portion of torrents coming up as paused on restart in 2.1.x seem to be resolved. and console seems to perform better.
As for libtorrent 2.0.latest, I sticking with 1.2.19 for now, if it isn't broke, don't fix it.
Libtorrent 2.0.8 update.
Re: Libtorrent 2.0.8 update.
This is why I recommend 1.2.x for everyone, qbit, deluge, whichever your taste - 1.2.x just performs and manages things better IMO.
Re: Libtorrent 2.0.8 update.
Can confirm that Libtorrent 2.0.13, the last version of the 2.0.x Libtorrent branch, is drop-in compatible with the current Windows build of Deluge 2.2.
Re: Libtorrent 2.0.8 update.
Nope, it has been working perfectly.
Re: Libtorrent 2.0.8 update.
There havent been any breaking changes, if there were it'd be 3.x, its semantic versioning...
major-version (breaking changes) [dot] minor version (features and additions) [dot] patches/bugfix/"adjustments"
If you wanna find out more, google "semantic version" - I think 1.2.19 is gonna be the last publishing on pypi, but that's the best by my benchmarkings and the memory mapping is just useless and wasteful in my opinion, even if it releases memory when the OS needs it.
There is a 2.1.x now, not sure what the changelog says but it should also be drop-in.
The fact of the matter, though, is that Deluge and it's featureset related to disks and caching as well as ltConfig are 100% compatible with 1.2.x, but they are not with 2.x.x - and I highly recommend if you're not reaching your full potential in Deluge for your internet connection that you check out the plugins section for the ltConfig post, and my stickied libtorrent tweaks, and then try that with 1.2.x
major-version (breaking changes) [dot] minor version (features and additions) [dot] patches/bugfix/"adjustments"
If you wanna find out more, google "semantic version" - I think 1.2.19 is gonna be the last publishing on pypi, but that's the best by my benchmarkings and the memory mapping is just useless and wasteful in my opinion, even if it releases memory when the OS needs it.
There is a 2.1.x now, not sure what the changelog says but it should also be drop-in.
The fact of the matter, though, is that Deluge and it's featureset related to disks and caching as well as ltConfig are 100% compatible with 1.2.x, but they are not with 2.x.x - and I highly recommend if you're not reaching your full potential in Deluge for your internet connection that you check out the plugins section for the ltConfig post, and my stickied libtorrent tweaks, and then try that with 1.2.x
Re: Libtorrent 2.0.8 update.
Yep, just successfully updated to 2.1.2 with no trouble. I was initially expecting to run into serious trouble with the 2.1.x branch, but the Boost.Python bindings (python3-libtorrent) seems to be doing its job and working to translate legacy API calls successfully.
Given the cadence of major change with libtorrent, I expect that Deluge 2.2 shouldn't run into any serious trouble for a long time.
Given the cadence of major change with libtorrent, I expect that Deluge 2.2 shouldn't run into any serious trouble for a long time.