Thank you for posting therobin, appreciate that and you're very welcome
Yes, me and petersasi's builds in general are almost identical, and he cleaned up the scripts to be little more professional, and user friendly, plus removed warnings and such, that I didn't care about when not changing anything and just is info really, about e.g changing back to default build-option when none applied, which is what I wanted anyways etc. I'm lazy as said, though only where not matters and not otherwise, obviously. Last, when I say that these builds are not made in professional way, then it's not this I mean, as else had changed obviously, but is because python apps practically always on windows is released as freezed packages, but the tool for freezing is currently incompatible with deluge and the good people working on it(curtesy doadin and Cas), haden't come up with full solution yet, hence, this was just meant as a stop gap measure, if people wanted try it, that's all. It should though have no differing things about it currently, except bigger filesize on my builds, but petersasi did great job in finding which files unused by deluge and removing, but is little tricky because as we seen, breakage can occure, because maybe somewhere a file is needed later on anyway,hence I didn't add that yet. He also made a nice patch making deluge-console work and another to shut it up later, plus better compile option for libtorrent, plus recently found an even better one(LTO, or rather WPO), which I borrowed from him and also used elsewhere through there supported way of declaring these flags(openssl and two older libtorrent's). I borrowed all these from him obviously, except including yarss2 which he also added, which is great plugin, but if wanted include one extra, would have taken ltconfig, which Cas previously stated to planning to include in feature.My dev builds include some unmerged PRs additionally which I found appropriate e.g pretty much only one important, besides a few not so much and just added previously when development was stagnant. The important one, was adding IPv6 support and allowing bind to your VPN or whatever on windows through device name and not needing IP, plus multiple binds if wanted, plus IPv6 geoipv6 support, great work curtesy of Strangelovian. Finally, I instead of normal python, meant for development, use an embedded python zip distribution, meant for either distributed python apps, or if needing add python scripting to non-python app, where the former applies to us, and it include a file which further isolates the used python for deluge only, so as not interferring with rest of system, e.g in certain circumstances deluge could fail to start without such added measures, though isn't often encountered, but better safe than sorry I thought.
Yes, that error indeed comes after using disk and not rebooting as you stated. It's also there when building from source and running, with zero changes from me, and not packed in installer so not me introducing this, I tested. I spent a couple hours on it yesterday, but didn't come further sadly. I read up on pdb debugger and found there was other options for steeping deeper into the code during debugging, as I thought 'next' i.e "line by line", was good enough, but 'step' was even better I found(leaves current line to also step into called functions, and was why before just showed the error was somewhere in run_profiled() from deluge.common and nothing else - I btw bypassed that function, but then deluge doesn't start, and changing various things in it, like save path for output log to 'None' etc , or stopping cprofile importing etc, helps not either), but now it always show other error strangely, when coming through section of pkg_resources pyparsing module, line 367,which just returns a variable 'retobj', and I thought I found the issue from a "suspecious" basedir.py module from pkg_resources I noticed, because had much path lookups therein, but doesn't trigger when run manually this module without deluge. Anyway, as said, good workaround is right click drive in windows explorer and select eject, every time having used the drive and ejected disc, which shows error as no disc, and now deluge issue gone, so just remember "double-eject" on win7 + not use default deluge theme if using windows classic theme, I found from fellow forum member reporting, and I noticed he used classic theme in his posted screenshoot which I tested and found to be the culprit for that.
* Wasent meant to be that long, sorry, but just wanted to be thorough when going into the differences, e.g also since remember previous posts requesting writeup of the diffs between our builds not that I make builds anymore, besides a single special circumstance, but nonetheless.
* Currently there's gtk3 building issues on my win7 repos, though win10 repos work fine, even when specifying same older python, strangely. I'm trying for last few days sort it out i.e. gvsbuild didn't update anything related, so is it a msvc update, msys64 update or windows update breaking this suddently(all was updated recently), right after I just fixed it last, dammit! - lol
Sorry for inconvenience for anybody possibly affected. Currently tediously installing and testing different msvc versions, as many msvc updates in last weeks alone, which possibly related, but takes long time though.
* Sorry, just noticed issue with yarss2 and https feeds in previously posted win7 deluge builds, so fixed and updated previous posted links.
* Cannot find the issue with gtk3 building on win7, and same exact repo works fine for building gtk3 on win10 instead of win7, so untill, or if at all, finding the issue, then the win7 repos need win10 to build gtk3, like x32 repos needs (now win10-)x64 host to build gtk3 in x32 mode as gvsbuild demands that. Sorry for inconvenience.