| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| README.txt | 2026-02-18 | 2.2 kB | |
| SHA512SUMS.asc | 2026-02-18 | 253 Bytes | |
| SHA512SUMS.minisig | 2026-02-18 | 277 Bytes | |
| pycheck-26.2.18-linux-x64.tar.xz | 2026-02-18 | 12.3 MB | |
| pycheck_26.2.18_linux_noarch.deb | 2026-02-18 | 44.5 kB | |
| SHA512SUMS | 2026-02-18 | 486 Bytes | |
| pycheck-26.2.18-source.tar.xz | 2026-02-18 | 42.2 kB | |
| Totals: 7 Items | 12.4 MB | 0 | |
18 February 2026 Marcus Dean Adams (gerowen@pm.me) - Added more rigorous checks for EasyGUI and an automated install process on non-Linux systems. Linux users will get a notice telling them to install it via their package manager. - Updated Reame with a note about the cessation of Windows builds, and methods for verifying the integrity of a download. - Updated build script to sign SHA512SUMS with Minisign as well as PGP - Replaced all images with more modern and professional looking ones 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 propelry. If you're not using the Debian package, after you install Python you can install easygui with: python -m pip install --upgrade easygui