You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've chosen 3.10 as the minimal requirement, aiming to stay two majors below the latest release and take advantage of the new features introduced in 3.10.
Among these features, we currently use:
Structural Pattern Matching (PEP 634)
New Type Union Operator (PEP 604)
TypeAlias (PEP 613)
Therefore, the current code wouldn't work with 3.9. The solution would be to refactor the code, which is not technically difficult but would also require us to maintain two code bases (one for 3.9 and one for >=3.10).
This additional development time won't be allocated to other features, so we'll need to monitor this request to see how many users it impacts and make a decision based on this.
Regarding scikit-learn, they specifiy the Python version in their setup.py (which is 3.9 for scikit-learn 1.3).
To better understand the impact of these restrictions, could you provide more details on why you need to stay on 3.9?
Thanks for the great-looking package!
I have hopefully a small request. Currently you have:
skfolio/pyproject.toml
Line 16 in a1e79d3
Is it possible to change this to
3.9
to reduce the restrictiveness?Sklearn doesn't actually specify a python version in their project.toml. And I don't see a need to restrict from the current dependencies:
The text was updated successfully, but these errors were encountered: