Skip to content
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

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

Draft
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

mattwthompson
Copy link
Member

No description provided.

Copy link

codecov bot commented Sep 9, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.70%. Comparing base (9176d73) to head (3cb1d65).

Additional details and impacted files

@mattwthompson mattwthompson changed the title Always use Pydantic v1 API Always use Pydantic v1 API, test using v1 Sep 9, 2024
try with interchange-rc label packages

unpin other openff deps

actually order channels correctly

remove interchange-rc channel

Revert toolkit change

Just use Pydantic v1 API, test both versions
@mattwthompson
Copy link
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
Contributor

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

@mattwthompson
Copy link
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

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