Inconsistent Python version constraints in documentation

[mhauru]

It seems that Python 3.10 is currently the highest Python version supported. However, there are a few places in the documentation that still say 3.8 or 3.9 is the highest. Not sure if the lower version bounds are more up to date, some places say 3.6, others 3.8, but not sure what the right one is. Here's a list of places where I saw this. I might have missed some, so might be worth a grep.

https://github.com/chaoss/augur/blob/a786ac5a506ffac31931f40c2a58056b7c1f073c/docs/source/getting-started/installation.rst?plain=1#L28 https://github.com/chaoss/augur/blob/a786ac5a506ffac31931f40c2a58056b7c1f073c/docs/source/getting-started/installation.rst?plain=1#L24 https://github.com/chaoss/augur/blob/a786ac5a506ffac31931f40c2a58056b7c1f073c/README.md?plain=1#L40 https://github.com/chaoss/augur/blob/a786ac5a506ffac31931f40c2a58056b7c1f073c/setup.py#L33 https://github.com/chaoss/augur/blob/a786ac5a506ffac31931f40c2a58056b7c1f073c/augur/tasks/git/util/facade_worker/setup.py#L45 https://github.com/chaoss/augur/blob/a786ac5a506ffac31931f40c2a58056b7c1f073c/augur/tasks/data_analysis/pull_request_analysis_worker/setup.py#L44 https://github.com/chaoss/augur/blob/a786ac5a506ffac31931f40c2a58056b7c1f073c/augur/tasks/data_analysis/contributor_breadth_worker/setup.py#L42 https://github.com/chaoss/augur/blob/a786ac5a506ffac31931f40c2a58056b7c1f073c/augur/tasks/data_analysis/discourse_analysis/setup.py#L50 https://github.com/chaoss/augur/blob/a786ac5a506ffac31931f40c2a58056b7c1f073c/augur/tasks/data_analysis/clustering_worker/setup.py#L43 https://github.com/chaoss/augur/blob/a786ac5a506ffac31931f40c2a58056b7c1f073c/augur/tasks/data_analysis/message_insights/setup.py#L55 https://github.com/chaoss/augur/blob/a786ac5a506ffac31931f40c2a58056b7c1f073c/augur/tasks/data_analysis/insight_worker/setup.py#L46 https://github.com/chaoss/augur/blob/a786ac5a506ffac31931f40c2a58056b7c1f073c/augur/tasks/git/util/facade_worker/setup.py#L45 https://github.com/chaoss/augur/blob/a786ac5a506ffac31931f40c2a58056b7c1f073c/scripts/install/checks.sh#L43 https://github.com/chaoss/augur/blob/a786ac5a506ffac31931f40c2a58056b7c1f073c/docs/source/development-guide/make/testing.rst?plain=1#L52

[PredictiveManish]

Hi @sgoggins sir,

I saw the discussion about Python version inconsistencies in Augur (3.6–3.10) in this issue. I wanted to check whether this still causes practical problems for users today.

If it does, do you have thoughts on possible ways to resolve it? For example, clarifying documentation, updating setup scripts, or enforcing a minimum/maximum Python version. My ideas includes ranging of versions for easy understanding of users as well as checks and adding a note for newcomers to get understanding what's this variety of version is. I want your suggestions what you believe is best way out?

Thanks!

[MoralCode]

https://github.com/chaoss/augur/blob/7e07c1dbba6f206c1a2c8f567d08058191aa49c2/.python-version#L1

https://github.com/chaoss/augur/blob/7e07c1dbba6f206c1a2c8f567d08058191aa49c2/pyproject.toml#L7

These are the python versions that actually matter from a technical perspective. Nearly all the rest of them seem like 1) documentation and 2) out of date.

#3266 was another issue that was identified along basically these exact same lines and was resolved with a docs fix.

For the .rst and .md docs i think we should just remove the references to specific python versions as those will get out of date quickly - information on current python support (or reasons it cant go higher) IMO belongs in the README or some other central place thats more likely to be updated regularly.

the Programming Language :: Python :: 3.7-style docs seem to mostly be in workers whose packages we arent really individually publishing to PyPi. for those i would say we should maybe make them just generic python 3 markers if that is a valid option, or remove them.

Hope that helps!