docs: clarify Python compatibility and reduce README redundancy

[TURTLE-prog]

This PR improves the README by:

• Removing repeated descriptive text to reduce redundancy
• Making Python version compatibility more visible for new users

No functional changes.

[MoralCode]

Does this PR solve a particluar issue? It seems like you may have been looking at #3441 but it doesnt appear to be referenced/linked here at all

[TURTLE-prog]

Does this PR solve a particluar issue? It seems like you may have been looking at #3441 but it doesnt appear to be referenced/linked here at all

thanks for pointing that out

This PR partially addresses #3441 by clarifying supported Python versions
(3.7–3.11) and making the incompatibility with 3.12+ explicit in the README.

It does not update the environment setup tooling (e.g., switching from venv
to uv). I’m happy to either extend this PR to cover that, or leave that part
for a follow-up PR if you’d prefer to keep changes scoped.

[MoralCode]

making the incompatibility with 3.12+ explicit in the README.

This incompatibility is likely going to be fixed in #3534 so saying this in the README is going to quickly become redundant and need fixing again.

Can you take a look at the other PRs linked in #3441 to see how your changes relate to others that have already been submitted (i.e. please try to work with the contributors of those other issues to make one PR as much as possible)? Having to look across multiple PRs for the same issue massively slows down review time

I will also add some comments in the underlying issue about what I hope to see as a resolution for this issue

[TURTLE-prog]

making the incompatibility with 3.12+ explicit in the README.

This incompatibility is likely going to be fixed in #3534 so saying this in the README is going to quickly become redundant and need fixing again.

Can you take a look at the other PRs linked in #3441 to see how your changes relate to others that have already been submitted (i.e. please try to work with the contributors of those other issues to make one PR as much as possible)? Having to look across multiple PRs for the same issue massively slows down review time

I will also add some comments in the underlying issue about what I hope to see as a resolution for this issue

Thanks for the context! that makes sense.

My intent here was mainly to reduce README redundancy and clarify the current state of Python support as it exists today. I see your point that explicitly calling out the 3.12 incompatibility may become outdated if #3534 lands soon.

I’ll review the other PRs linked to #3441 and the comments you add there. Happy to adjust this PR to better align with the agreed direction (e.g. removing or softening the 3.12 note), or to narrow the scope strictly to redundancy cleanup if that’s preferred.