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

add test run for 3.13t #1626

Merged
merged 5 commits into from
Feb 6, 2025
Merged

add test run for 3.13t #1626

merged 5 commits into from
Feb 6, 2025

Conversation

davidhewitt
Copy link
Contributor

Change Summary

Initial attempt at testing free-threaded Python. Looks like there's quite a few kinks to work out before we can call this stable. Let's run this here in CI, assess how things look, and decide whether to merge as-is (allowing the failures) or to fix before merging.

cc @Viicos

Related issue number

Xref #1555

Checklist

  • Unit tests for the changes exist
  • Documentation reflects the changes where applicable
  • Pydantic tests pass with this pydantic-core (except for expected changes)
  • My PR is ready to review, please add a comment including the phrase "please review" to assign reviewers

Copy link

codspeed-hq bot commented Feb 6, 2025

CodSpeed Performance Report

Merging #1626 will not alter performance

Comparing dh/3.13t (d1b277d) with main (0862ea5)

Summary

✅ 157 untouched benchmarks

@davidhewitt
Copy link
Contributor Author

@Viicos I will merge this now so that we can have the freelist patch applied in the next pydantic-core release so that downstream pydantic can at least start running tests and see what happens.

@davidhewitt davidhewitt marked this pull request as ready for review February 6, 2025 14:48
@davidhewitt
Copy link
Contributor Author

The test run will fail on every build but does not block merge.

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.

1 participant