Is it really futuristic on Windows? All CPUs are 64bits nowadays and running a 32bit OS on top of them is just a waste. For people actually living in our century, running a 64bit qBittorrent on a 64bit Windows actually makes a lot of sense for performance and functionality. Forcing people that have a 64bit OS to run a 32bit qBittorrent does not make any sense.
Belive it or not, the short answer is: yes.
If there would be an app that could measure the installed 64-bit and 32-bit applications, you would be surprised. I'm using this install for a year or so, and I've installed a lot of applications during this time. The only 64-bit native applications on my system are: Oracle Java JDK, Adobe Flash (it's a mess on 64-bit), and Adobe Photoshop.
That's it. To be honest, I don't mind. Windows handles 32-bit different. While on Linux, you need a whole bunch of i686/i386 packages just to have the sub-system (and it will or won't work), and it loads for seconds sometimes (loading all the libs), it works perfectly on Windows. Also, 32-bit applications come with a smaller memory footprint, which is a nice feature to have. Speed? 64-bit only means faster execution if the task is REALLY, REALLY CPU-intensive. For example: Rendering, calculating. But for userland apps like qBittorrent? No benefits, just the extra work of testing. You only install a 64-bit Windows if you have 4gb+ RAM. Unlike Linux, where you install 64-bit if your CPU supports it.
Even uTorrent ships 32-bit binaries. They plan on releasing a 64-bit build, but I guess it'll take years. (Just like the whole transition to 64-bit thing.)
If you want to ship it, and someone will take the maintainer role, it would worth checking the XChat-WDK project
. A free XChat for Windows. It may provide some useful information about how to do it nice and clean. (That project 32-bit and 64-bit Windows builds from every release, so I guess it's possible.)
I'm not sure there is any benefit for us to use ActiveState Python compared to the regular Windows installer from python.org.
Sorry I didn't notice the official package. Hmm... we should go with the portable one then. Just grab it (like Pidgin does with GTK), and unpack it inside qBittorent's folder.