Skip to content

Commit

Permalink
Python: Fix syntax for pinned pydantic package. (#9789)
Browse files Browse the repository at this point in the history
### Motivation and Context

The current pydantic pinned syntax is `"pydantic ~= 2.0<2.10",`; however
on package publish, Pypi throws a 400. The correct syntax should be:
`"pydantic >=2.0,<2.10",`

<!-- Thank you for your contribution to the semantic-kernel repo!
Please help reviewers and future users, providing the following
information:
  1. Why is this change required?
  2. What problem does it solve?
  3. What scenario does it contribute to?
  4. If it fixes an open issue, please link to the issue here.
-->

### Description

Updates pyproject.toml syntax for pinned pydantic version.

<!-- Describe your changes, the overall approach, the underlying design.
These notes will help understanding how your code works. Thanks! -->

### Contribution Checklist

<!-- Before submitting this PR, please make sure: -->

- [X] The code builds clean without any errors or warnings
- [X] The PR follows the [SK Contribution
Guidelines](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
and the [pre-submission formatting
script](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md#development-scripts)
raises no violations
- [X] All unit tests pass, and I have added new tests where possible
- [X] I didn't break anyone 😄
  • Loading branch information
moonbox3 authored Nov 21, 2024
1 parent 05f9a98 commit 44222f5
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 4 deletions.
2 changes: 1 addition & 1 deletion python/pyproject.toml
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ classifiers = [
dependencies = [
"aiohttp ~= 3.8",
"cloudevents ~=1.0",
"pydantic ~= 2.0<2.10",
"pydantic >=2.0,<2.10",
"pydantic-settings ~= 2.0",
"defusedxml ~= 0.7",
# azure identity
Expand Down
4 changes: 1 addition & 3 deletions python/uv.lock

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

0 comments on commit 44222f5

Please sign in to comment.