Support Python 3.10 again?

[kylejcaron]

This package requires python >= 3.12 which is quite restrictive. It seems like it was originally necessary due to using Path.walk, but I'm not seeing that used anymore.

Is it possible for testing be added for backwards compatibility and the python version requirements go back to >= 3.10?

[lagru]

I wouldn't extending support to 3.10 again as long as we don't sacrifice too much. Let me check that that is the case. But eventually we will want to leave older versions behind.

Since docstub is a command line application that doesn't need to import the target package it is run on, it can theoretically use it's own environment. However, we might go for dynamic analysis in the future and then wider support would be useful.

SPEC 0 — Minimum Supported Dependencies, linked in your referenced issue arviz-devs/arviz-base#87, is also somewhat relevant here.

[kylejcaron]

SPEC 0 — Minimum Supported Dependencies

Thanks for sharing! I'm still working on the tox file and seeing if there would need to be any github action changes, but this is roughly the required changes to go back to >= 310

#74

[kylejcaron]

Since docstub is a command line application that doesn't need to import the target package it is run on, it can theoretically use it's own environment. However, we might go for dynamic analysis in the future and then wider support would be useful.

I see what youre saying now about how it can use its own environment - it turns out this change isnt quite necessary for arviz either since its only used in the development cycle, not the actual arviz package install requirements.

Up to you if you still think this is useful, the PR is ready for review (I wasnt able to kick off the ci workflow with my PR)

[lagru]

Closing. See #74 (comment) for context. Thank you @kylejcaron!