Closed nbraud closed 3 months ago
wrt homf, I opened: https://github.com/duckinator/homf/issues/9
I'm fine dropping 3.8 support a bit early, but let's revisit the Python 3.9 decision after I've had some sleep and things settle down a bit here.
https://versions.do1g.com/ shows the big distro families all seem to be on 3.10+, though, fwiw.
the big distro families all seem to be on 3.10+
Yes, that was my thinking: all major distros have long updated to 3.10 or later, and bork
is a dev tool so we can presumably expect users not to run oldoldoldoldstable or such.
For some reason, selecting a specific commit or branch with a dependency pulled from git
does not seem to work, so I just pointed it at my fork of homf, and changed its default branch >_>'
Hopefully Thankfully that works
This should be good to merge once:
Found some more dead code with vulture and the diff stats are really pleasing now~ :heart:
Homf v1.1.1 is released. (There was a slight technical issue with v1.1.0 lol)
Thanks again Ellen :heart: I marked the PR as ready, since all that's missing is deciding whether we are fine dropping Py3.9 support
Given that Python 3.9 is in "source-only security updates" mode and most things are on 3.10+, I'm fine with dropping 3.8 + 3.9 support.
bork.api.download
out tohomf
, removed the individual downloadersNot strictly-necessary, but minor improvements made things easier:
pyproject.toml
bork.api.download
withmatch
statement Using pattern matching induces a dependency on Python 3.10 or later; 3.8 is end-of-life in October, but technically 3.9 receives security fixes until next year.