Skip to content

Always use Pydantic v1 API, test using v1 and v2#358

Draft
mattwthompson wants to merge 1 commit intomainfrom
pydantic-always-v1
Draft

Always use Pydantic v1 API, test using v1 and v2#358
mattwthompson wants to merge 1 commit intomainfrom
pydantic-always-v1

Conversation

@mattwthompson
Copy link
Copy Markdown
Member

No description provided.

@codecov
Copy link
Copy Markdown

codecov bot commented Sep 9, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.33%. Comparing base (54d9dbd) to head (310cf90).

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@mattwthompson mattwthompson changed the title Always use Pydantic v1 API Always use Pydantic v1 API, test using v1 Sep 9, 2024
@mattwthompson
Copy link
Copy Markdown
Member Author

The failures here are genuine, but could be due to hard-coded parts of the tests. I can't tell at the moment, but note that the traceback includes only files from upstreams.

@mattwthompson mattwthompson changed the title Always use Pydantic v1 API, test using v1 Always use Pydantic v1 API, test using v1 and v2 Sep 9, 2024
@SimonBoothroyd
Copy link
Copy Markdown
Contributor

seems like this could related to fastapi/fastapi#10360?

@mattwthompson
Copy link
Copy Markdown
Member Author

Could be - I haven't used the V1 API backdoor in a project that also uses fastAPI and it wouldn't surprise me if that's not possible.

I don't see any reason why this couldn't use V2, but it'd be some work

@hmacdope
Copy link
Copy Markdown

hmacdope commented Feb 4, 2025

We are in the process of migrating for asap and are at the bespokefit part. I can try and help with migration if it would assist @mattwthompson @SimonBoothroyd

@mattwthompson
Copy link
Copy Markdown
Member Author

cc @j-wags

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants