8000 chore: drop pydantic v1 support by sivanantha321 · Pull Request #4353 · kserve/kserve · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

chore: drop pydantic v1 support #4353

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 12 commits into from
May 29, 2025
Merged

Conversation

sivanantha321
Copy link
Member
@sivanantha321 sivanantha321 commented Apr 2, 2025

What this PR does / why we need it:
Currently both v1 and v2 pydantic is supported, dropped support for v1 for the support overhead.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Type of changes
Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

Release note:

NONE

Re-running failed tests

  • /rerun-all - rerun all failed workflows.
  • /rerun-workflow <workflow name> - rerun a specific failed workflow. Only one workflow name can be specified. Multiple /rerun-workflow commands are allowed per comment.

@sivanantha321 sivanantha321 marked this pull request as ready for review April 3, 2025 06:51
Copy link
Contributor
@spolti spolti left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are we going to replace it?

Or will just pytest be used from now on?

@sivanantha321
Copy link
Member Author

Are we going to replace it?

We are not replacing. This PR just removes pydantic v1 compatibility layer.

Or will just pytest be used from now on?

What do you mean by pytest ?

@spolti
Copy link
Contributor
spolti commented Apr 22, 2025

Are we going to replace it?

We are not replacing. This PR just removes pydantic v1 compatibility layer.

Or will just pytest be used from now on?

What do you mean by pytest ?
because of it: https://github.com/kserve/kserve/pull/4353/files#diff-0165ee7fe5057e5c6e9f2ae4ae3d87d21324f691385cbf51b220a4abe79ce492L108

@sivanantha321
Copy link
Member Author

because of it: https://github.com/kserve/kserve/pull/4353/files#diff-0165ee7fe5057e5c6e9f2ae4ae3d87d21324f691385cbf51b220a4abe79ce492L108

That test is for checking compatibility with pydantic v1. There is already a separate job for kserve unit test with pydantic v2.

Signed-off-by: Sivanantham Chinnaiyan <sivanantham.chinnaiyan@ideas2it.com>
Signed-off-by: Sivanantham Chinnaiyan <sivanantham.chinnaiyan@ideas2it.com>
Signed-off-by: Sivanantham Chinnaiyan <sivanantham.chinnaiyan@ideas2it.com>
Signed-off-by: Sivanantham Chinnaiyan <sivanantham.chinnaiyan@ideas2it.com>
@yuzisun yuzisun merged commit cf4facd into kserve:master May 29, 2025
65 checks passed
@yuzisun yuzisun changed the title Drop Pydantic v1 support chore: drop pydantic v1 support May 29, 2025
israel-hdez pushed a commit to israel-hdez/kserve that referenced this pull request May 29, 2025
Signed-off-by: Sivanantham Chinnaiyan <sivanantham.chinnaiyan@ideas2it.com>
Co-authored-by: Dan Sun <dsun20@bloomberg.net>
Signed-off-by: Edgar Hernández <23639005+israel-hdez@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants
0