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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test Python 3.11 beta #539

Merged
merged 1 commit into from May 18, 2022
Merged

Test Python 3.11 beta #539

merged 1 commit into from May 18, 2022

Conversation

hugovk
Copy link
Member

@hugovk hugovk commented May 18, 2022

Python 3.11.0 beta 1 has been released 馃殌

This means it's now time for projects to start testing 3.11:

We strongly encourage maintainers of third-party Python projects to test with 3.11 during the beta phase and report issues found to the Python bug tracker as soon as possible. While the release is planned to be feature complete entering the beta phase, it is possible that features may be modified or, in rare cases, deleted up until the start of the release candidate phase (Monday, 2021-08-02). Our goal is have no ABI changes after beta 4 and as few code changes as possible after 3.11.0rc1, the first release candidate. To achieve that, it will be extremely important to get as much exposure for 3.11 as possible during the beta phase.

On GitHub Actions, 3.11-dev tracks the latest available alpha/beta/RC.

Let's start testing now. Wheels can come later, perhaps during the release candidate phase or after beta 4.

@hugovk hugovk added testing Unit tests, linting, CI, etc. changelog: Added For new features labels May 18, 2022
@hugovk hugovk merged commit 80d0bd4 into ultrajson:main May 18, 2022
28 checks passed
@hugovk hugovk deleted the add-3.11 branch May 18, 2022 18:58
@bwoodsend
Copy link
Collaborator

Let's start testing now. Wheels can come later, perhaps during the release candidate phase or after beta 4.

I vaguely remember reading somewhere that we should never release wheels for beta candidates in case the Python ABI changes and we end up with bogus wheels on PyPI.

@hugovk
Copy link
Member Author

hugovk commented May 18, 2022

Yes, I think that was the case until fairly recently? With at least 3.10, they are aiming for longer ABI stability, as the release manager said above:

Our goal is have no ABI changes after beta 4 and as few code changes as possible after 3.11.0rc1, the first release candidate.

So I think the risk will be low and the benefits high: enabling others to easily install ujson and test their own software and fix issues before 3.11.0 final.

We can put out new releases quickly and easily, and yank bad releases if needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changelog: Added For new features testing Unit tests, linting, CI, etc.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants