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

update CI to run targeting main #6

Merged
merged 2 commits into from
Oct 10, 2024
Merged

update CI to run targeting main #6

merged 2 commits into from
Oct 10, 2024

Conversation

davidhewitt
Copy link
Member

I made the default branch main as part of the fork process.

@davidhewitt davidhewitt mentioned this pull request Oct 5, 2024
6 tasks
@davidhewitt davidhewitt force-pushed the davidhewitt-patch-1-1 branch from fc69acc to 490f2e6 Compare October 10, 2024 04:48
@cjdsellers
Copy link
Collaborator

We could also consider dropping support for Python 3.7, and 3.8 since they are past end-of-life?

@davidhewitt
Copy link
Member Author

Yes, I think dropping them would be fine. (Main consumer of PyO3's 3.7 / 3.8 extended support is cryptography, which I don't think depends on pyo3-asyncio, cc @alex?)

To avoid too much change in one PR I will just merge this here despite being broken, given it allows other PRs to be tested :)

@davidhewitt davidhewitt merged commit 38e34c5 into main Oct 10, 2024
27 of 34 checks passed
@davidhewitt davidhewitt deleted the davidhewitt-patch-1-1 branch October 10, 2024 05:41
@alex
Copy link

alex commented Oct 10, 2024 via email

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