[REQUEST]: Improve requires-python resolution

[richieadler]

Prerequisites

• I have searched the issues and believe that it has not already been requested (and possibly rejected)
• I have made sure that this feature isn't possible with this project's plugin system and/or configuration; core changes must be made to make this happen.
• I agree to follow the Code of Conduct

Feature description

Improve the logic to re-use existing venvs for valid requires-python clauses.

Rationale

Currently requires-python tries to find the higher Python available and creates a venv accordingly, even if the clause would be satisfied by an existing venv.

Scenario:

• Windows 11
• Python 3.11.9 and 3.12.3 installed
• requires-python = ">=3.11,<3.12"

Script runs with 3.11.9 correctly.

• Changed to requires-python = ">=3.11"

It creates a new 3.12.3 venv instead of using the pre-existing 3.11.9 for which the requires-python clause is still valid.

[richieadler]

-i is not what I expected... If I use # requires-python = ">=3.10,<3.12" running *idae* without any switches creates a 3.11.9 environment, but using *idae -i* doesn't reuse the existing environ, it creates a 3.10.6 environment (the minimal specification complying with the requires-python line. (I would expect idae to reuse the 3.11.9 environment.) El sáb, 25 may 2024 a las 18:45, ThatXliner ***@***.***>) escribió:

…

Sorry for the late response! Can you try out the latest PR? — Reply to this email directly, view it on GitHub <#14 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACD5STBBKYNRYV6NG3YVCPLZEEA7BAVCNFSM6AAAAABHWEYTAOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZRGUYDAMBSGY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- o-=< Marcelo >=-o

[ThatXliner]

Yea, it’s still in progress