The WinPython 2025-03 build4 is out.
Special attention is on the "whl" version, that ships with the standard "non-installed" wheels from pypi (at the time of build, to be mathematically precise), to install per the user
Changes from WinPython 2025-03 b3 :
Infrastructure:
- AI use:
- significantly augment the use of AIs:
- the more you use them, the more you learn to use them for a global benefit,
- the [your] job of maintainance is drifting to higher level thanks to the AI workforce:
- done: snippets of code, re-engineering a program with constraints
- ongoing: features, documentation
- future: infrastructure work, test work, release work, security work
- will remain: the board, ideas, directions, guidelines, control
- danger: feature bloat, user eyes bloating, as it's now too easy to "add" or "generate" content
- think yourself as that IT department n'vidia is speaking of :
- "the IT department is going to become the HR department of your digital workforce"
- "
https://x.com/slow_developer/status/1902842588392198570"
- Markdowns
- wppm can now generates the Markdown of a WinPython release: "wppm -md"
- wppm can diff between installed wheels and wheels in the WheelHouse: "wppm -md -ws ."
- "Python" is listed in the "Tools" Category now
- WheelHouse:
- wppm can nagivate in the WheelHouse(s) by adding "-ws .": "wppm -ws . -ls" , "wppm -ws . -p pandas", ...
- "wppm -i" installs package(s) from designated Wheelhouse, default is the local one: "wppm -i pandas duckdb"
- a Wiki page explains WheelHouse features:
https://github.com/winpython/winpython/wiki/WheelHouse - sourceforge:
- with all these requirements and lockfile... better to split betas in sub-directories starting b4, rather than a big betas
- re-arrange hash in one packet per type of files: binaries, requirement files, lock files