-
Notifications
You must be signed in to change notification settings - Fork 184
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
Release for Python 3.11 #1099
Comments
@marscher Not sure how many tries I will have to take for this release. There appears to be a problem with some of the the pinned versions not working with Python3.11. Hopefully unpinning them will work. If not I will have to come up with a new testing solution. |
Looks like the release will clear. I should be able to release tomorrow morning. |
It appears that the linux image does not have 3.11 available. I can distribute the rest and then try to get those built later. |
@marscher It seems like we need to change to manylinux2014 image to get Python 3.11. I can change to this for all future builds. But for now I am just updating the release script for a one off run. I am not sure if I need to split the build so that pre 3.11 goes with the manylinux2010 image. If you have some insight I can get it setup for our future releases. Assuming everything looks good, the ball is in your court to push this to PyPi. Given the level of changes required for 3.11, I don't think one day after the release is too bad given that we have to wait for the azure image to be updated before we can release. |
Thanks! PyPI push of wheels and source dist has been done. |
Conda-forge support for 3.11 will be added by their bot soon. It has to pick up the PyPI push first. |
git checkout release
git checkout -b releases/{version}
git pull origin master
bumpversion release
git push
jpype.release
on azureIf successful, download the artifacts for publication.
git checkout release
git merge releases/<version>
git checkout master
git checkout -b cycle
git merge release
bumpversion patch
The text was updated successfully, but these errors were encountered: