| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| pycheck-26.4.5-linux-x64.tar.xz | 2026-04-06 | 12.3 MB | |
| SHA512SUMS.minisig | 2026-04-06 | 276 Bytes | |
| README.txt | 2026-04-06 | 2.3 kB | |
| SHA512SUMS | 2026-04-06 | 483 Bytes | |
| SHA512SUMS.asc | 2026-04-06 | 252 Bytes | |
| pycheck-26.4.5-source.tar.xz | 2026-04-06 | 42.4 kB | |
| pycheck_26.4.5_linux_noarch.deb | 2026-04-06 | 44.5 kB | |
| Totals: 7 Items | 12.4 MB | 0 | |
5 April 2026 Marcus Dean Adams (gerowen@pm.me) - Made several dialogs and messages more clear about what is happening and when. - Moved some comments around to make them easier to spot when reading the source code. - Removed the option to attempt an installation of EasyGUI via pip. I don't think it's a good idea for me to be installing third party packages on somebody else's system in an automated fashion, especially considering how often package repositories for things like pip and npm are targeted with malware. REMINDER AND FINAL NOTICE TO WINDOWS USERS AS OF 26.2.18 ---------------------------------------------------------------- I'm not going to bother building Windows binaries any more. Nobody close to me uses Windows, the binaries get detected as malware by Microsoft Defender because I compile them with PyInstaller, and if you explicitly tell Defender to "allow" it, you then also have to answer a prompt from Windows app control allowing an unsigned/untrusted binary to run. I can't even include a PowerShell script to do the Python venv setup for the plain text Python executable like I do with the Linux bash script, because the execution of unsigned PowerShell scripts is disabled by default in Windows. All this means that in order to ship a Windows release in the same easy-to-use state as the Linux release would require me to pay for a signing certificate instead of using my existing PGP or MiniSign keys, and since this is just a personal project that I maintain mostly for myself and immediate family, I'm not going to spend hundreds of dollars a year to support a platform none of us use. Windows users can still freely use the Python source file with minimal issues. I'll still try to take Windows environment variables and such into account in future development, I'm just not going to bother compiling my own exe files. For the best experience in Windows, when launching the .py file directly, keep in mind a few things: 1) You need to have Python installed. 2) You need the easygui library, and therefore tk as well, for the graphical windows to work properly. After you install Python you can install easygui by running the following in a command prompt/terminal window: python -m pip install --upgrade easygui