Versioning question: Is dropping support for an older version of a programming language a major or minor change? I.e. version 2.5 of my software supported Python 3.8-3.12, the next version supports only 3.10-3.12 (but no API/functional changes). What kind of version bump would you expect?
@anteru I'd say it depends on user impact. Py 3.8 and 3.10 are very similar and users may not need to change their code at all -> minor version.
However if your users, for some reason, depend heavily on 3rd party modules which may not be available on 3.10 or require bigger changes, then I'd do a major version bump. This tells users that they'll face some bigger changes
@kwramm The users use it as a CLI program, unless they wrote their own plugin. For "normal" use I'd assume they use a docker container or a recent enough Linux version to not care. For someone already on Python 3.10 there's no difference in most cases, so a patch bump seems fine ...?
@anteru I'd pick minor then. Pretty much all Python 3.8 code should run on 3.10 and newer. Some minor problems might happen on the fringes (like there were some type checking changes - but I think nothing breaking)