tweak messaging re incompatible python versions

[dimbleby]

A probably futile attempt to slow the steady drip of people reporting that they don't understand what poetry is telling them about python versions.

switching from "the current project's Python requirement" to "the current project's supported Python range" is intended:

• to encourage readers to realise that poetry has to think not only about the current environment but about the whole range for which their project declares support
• to de-emphasise "requirement", I can see why people read that and think "but my environment does satisfy that requirement"

[github-actions]

Deploy preview for website ready!

✅ Preview
https://website-rlg1ibw0h-python-poetry.vercel.app

Built with commit cbc1db9.
This pull request is being automatically deployed with vercel-action

[radoering]

There is one more `python` requirement in pyproject.md that probably should be replaced.

[dimbleby]

There is one more python requirement in pyproject.md that probably should be replaced.

I'd decided to leave that one alone on the grounds that it wasn't really relevant to the confusion that I'm trying to address.

In that place, I think it's more helpful to be consistent with the pyproject.toml terminology, perhaps "requirement" -> "dependency" would make sense

[radoering]

I don't care much. Since you have thought about it, that's fine with me.

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.