Check pyproject requirements before running unit tests

[janbuchar]

See https://github.com/apify/crawlee-python/actions/runs/13078683861/job/36501197341 for a practical application

• closes CI can use wrong Python version in some cases crawlee-python#931

Since it doesn't seem to be possible to reuse code in reusable workflows, I just added this to unit tests...

[Pijukatel]

I was hoping this would be possible to solve on Poetry level. Looking into Poetry code that prints The currently activated Python version ... is not supported by the project it seems that it can raise exception if we explicitly specify executable (and not look for another Python version). I didn't dig deeper, but maybe we can start Poetry with explicitly passing Python executable and thus trigger this exception if the executable is not compatible?

https://github.com/python-poetry/poetry/blob/main/src/poetry/utils/env/env_manager.py#L421

[janbuchar]

I was hoping this would be possible to solve on Poetry level. Looking into Poetry code that prints The currently activated Python version ... is not supported by the project it seems that it can raise exception if we explicitly specify executable (and not look for another Python version). I didn't dig deeper, but maybe we can start Poetry with explicitly passing Python executable and thus trigger this exception if the executable is not compatible?

Well, I was hoping that you could turn off the autodetection via config 🤷 I also found that code you referenced, but it didn't feel right to depend on undocumented behavior found by digging in the code.

[vdusek]

Really? The script should check both possible locations for the python version constraint. Is there anything else to handle?

Oh, you're right, I overlooked that, thanks.

[vdusek]

LGTM

[Pijukatel]

I was hoping this would be possible to solve on Poetry level. Looking into Poetry code that prints The currently activated Python version ... is not supported by the project it seems that it can raise exception if we explicitly specify executable (and not look for another Python version). I didn't dig deeper, but maybe we can start Poetry with explicitly passing Python executable and thus trigger this exception if the executable is not compatible?

Well, I was hoping that you could turn off the autodetection via config 🤷 I also found that code you referenced, but it didn't feel right to depend on undocumented behavior found by digging in the code.

I think we can use this documented feature: https://python-poetry.org/docs/managing-environments/

I did quick local test with multiple Python versions available and some constraint in Pytproject.toml and it seems to be doing what we want. For example doing it in two steps:

poetry env use python3.10.12
poetry install

-> This will raise error if the requirements do not match selected version

Current Python version (3.10.12) is not allowed by the project (>3.10.12).
Please change python executable via the "env use" command.

[janbuchar]

@Pijukatel Since this is non-intrusive and not a huge priority, I'll merge this now. If you want to propose a different solution, feel free to open another PR.