Add support for Python 3.11 and Python 3.12 #179
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Add support for Python 3.11 and, in turn, 3.12 too.
I completely lifted the upper version cap for the Python version. See:
The side effect of that is that users may attempt to install on Python 3.13, but since there are no precompiled wheels of
pyarrow==17.0.0
it will fail unless the user system has the necessary dependencies. This doesn't mean that it isn't technically possible to usekedro-vertexai
on Python 3.13, it's just that I haven't tried. The user would get a warning coming from Kedro anyway, see kedro-org/kedro#2742 🔶I also added 3.11 and 3.12 to the test matrix.
Resolves #139, resolves #146
I think the errors observed by @Lasica in #146 were due to Poetry bugs and not necessarily dependency incompatibilities. So I ran
pdm import
to migrate the project metadata to PEP 621 (the only reason I chose PDM was because suchimport
command existed, with a trivial change this can be migrated to Hatch or any other PEP 621-compliant workflow tool). This doesn't have user impact.PR Checklist