Running the latest 1.3 version through virustotal hits 23/70 antivirus engines that there is a trojan in this code, so I am curious as to what is causing all these engines to trigger this:
https://www.virustotal.com/gui/file/0e4ad7f9c493fa2acf5388eb34469f50862d49b56f24...
I use a program called PyInstaller that turns Python code into a runnable Windows EXE. Actual malware authors decided it was a useful tool, and the companies that make antivirus software don't bother to discriminate between malware EXEs made with PyInstaller and legitimate programs. There are dozens upon dozens of closed issues about this on the PyInstaller project page: https://github.com/pyinstaller/pyinstaller/issues?q=is%3Aissue+virus+
If I had any reason to believe that my Windows machine was compromised and might be passing on a virus or trojan via builds it created, I would not release anything until I was certain it was gone. But this is not, nor has ever been, the case. It's frustrating, I wish I could do more. Windows Defender at least has a process by which you can submit your code and tell it to not flag it as a false positive, but most other AV software houses are not transparent.