-
api-ms-win-core-path-HACK
Implementation of api-ms-win-core-path-l1-1-0.dll for Windows 7 based on Wine code
-
wixsharp
Framework for building a complete MSI or WiX source code by using script files written with C# syntax.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
Python > 3.9 works just fine on Windows 7 with the api-ms-win-core-path-l1-1-0.dll Wine hack: https://github.com/nalexandru/api-ms-win-core-path-HACK
It's interesting because once Win 10 support drops there will no longer be any x86 Windows path for Python, but there's still a lot of x86 Windows hardware that still works.
I suppose that's more an argument to move to Linux/FreeBSD though on that hardware... I can understand dropping support for something but single breaking changes shouldn't merit it.
The functionality in the msilib module is somewhat low-level anyway (it basically just opens the database for you and leaves the arcane incantations required for doing anything as an exercise for the reader) so it probably wouldn't be hugely difficult to replace it with ctypes calling msi.dll directly.
If I were to replace my msilib-based installer, I would migrate to Wix# [1], a fantastic high-level wrapper for WiX that lets you express your installer in a few lines of C# (and then generates the thousands of lines of XML that WiX needs, but you don't need to touch it). I wouldn't have used msilib if I had known about Wix# at the time.
[1] https://github.com/oleg-shilo/wixsharp
Indeed, the uu module is a short Python wrapper around binascii. It's only 206 lines, much of which is comments or docstrings:
https://github.com/python/cpython/blob/a5b7678a67ac99edd5082...
It has three functions: one to encode, one to decode, and one to show usage information and handle arguments. It's only had 3 commits since 2010. There just isn't much to maintain.