-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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 Python 3.11 support for runners #6459
Comments
@wbarnha |
We will deploy it as soon as it is in the python-version repo |
@mikhailkoliada , is there are more detailed description of the workflow somewhere?
Is that basically saying that the maintainers of that repo look at these issues and then add what is required there, which will then get picked up here? |
@AntonOfTheWoods we have a number of workflow in the python-versions repo which are responsible for repackaging a specific python version or building it from the source code and publish a new release there, then versions-manifest.json is updated with the new versions. Finally we parse versions-manifest.json to get all the latest python major-minor versions for a specific release. |
As this issue is tagged with |
@mdshw5 similar changes are planned for macOS too. |
… on macOS This way each time a new Python version is installed via Homebrew , we don't get CI failures due to the upstream Python distribution also being installed. Ref: actions/runner-images#6459 Ref: actions/runner-images#2322
… on macOS This way each time a new Python version is installed via Homebrew , we don't get CI failures due to the upstream Python distribution also being installed. Ref: actions/runner-images#6459 Ref: actions/runner-images#2322
… on macOS This way each time a new Python version is installed via Homebrew , we don't get CI failures due to the upstream Python distribution also being installed. Ref: actions/runner-images#6459 Ref: actions/runner-images#2322
… on macOS This way each time a new Python version is installed via Homebrew , we don't get CI failures due to the upstream Python distribution also being installed. Ref: actions/runner-images#6459 Ref: actions/runner-images#2322
… on macOS This way each time a new Python version is installed via Homebrew , we don't get CI failures due to the upstream Python distribution also being installed. Ref: actions/runner-images#6459 Ref: actions/runner-images#2322
… on macOS This way each time a new Python version is installed via Homebrew , we don't get CI failures due to the upstream Python distribution also being installed. Ref: actions/runner-images#6459 Ref: actions/runner-images#2322
… on macOS This way each time a new Python version is installed via Homebrew , we don't get CI failures due to the upstream Python distribution also being installed. Ref: actions/runner-images#6459 Ref: actions/runner-images#6507 Ref: actions/runner-images#2322
… on macOS This way each time a new Python version is installed via Homebrew , we don't get CI failures due to the upstream Python distribution also being installed. Ref: actions/runner-images#6459 Ref: actions/runner-images#6507 Ref: actions/runner-images#2322
We're now hitting immediate |
Failing due to brew link failure. Ref: actions/runner-images#6459 (comment)
Failing due to brew link failure. Ref: actions/runner-images#6459 (comment)
Confirmed.
build.yml was working perfectly fine just a while ago. |
Same issue in llvm-tutor when trying to install lit. |
Hi all, sorry for delays! We will take a closer look to conflict |
Deployed, though in brew python is still not updated to 3.11 on images. |
The github mac runner images added python 3.11 but, unlike 3.10, not via brew. This causes brew install to fail with link conflict errors now that boost-python3 switched over to 3.11. Workaround this, and future python brew link errors, by ovewriting all links for python packages. Homebrew/homebrew-core@8c79089 https://github.com/orgs/Homebrew/discussions/3895 actions/setup-python#577 actions/runner-images#6459 actions/runner-images#6507 actions/runner-images#2322
The github mac runner images added python 3.11 but, unlike 3.10, not via brew. This causes brew install to fail with link conflict errors now that boost-python3 switched over to 3.11. Workaround this, and future python brew link errors, by overwriting all links for python packages. Homebrew/homebrew-core@8c79089 https://github.com/orgs/Homebrew/discussions/3895 actions/setup-python#577 actions/runner-images#6459 actions/runner-images#6507 actions/runner-images#2322
The github mac runner images added python 3.11 but, unlike 3.10, not via brew. This causes brew install to fail with link conflict errors now that boost-python3 switched over to 3.11. Workaround this, and future python brew link errors, by overwriting all links for python packages. Homebrew/homebrew-core@8c79089 https://github.com/orgs/Homebrew/discussions/3895 actions/setup-python#577 actions/runner-images#6459 actions/runner-images#6507 actions/runner-images#2322
… on macOS This way each time a new Python version is installed via Homebrew , we don't get CI failures due to the upstream Python distribution also being installed. Ref: actions/runner-images#6459 Ref: actions/runner-images#6507 Ref: actions/runner-images#2322
… on macOS This way each time a new Python version is installed via Homebrew , we don't get CI failures due to the upstream Python distribution also being installed. Ref: actions/runner-images#6459 Ref: actions/runner-images#6507 Ref: actions/runner-images#2322
Tool name
Python
Tool license
PSF-2.0
Add or update?
Desired version
3.11
Approximate size
No response
Brief description of tool
Python 3.11 was released today on https://www.python.org/downloads/, can we get this added so that it's available in
python-versions
andsetup-python
?URL for tool's homepage
No response
Provide a basic test case to validate the tool's functionality.
No response
Platforms where you need the tool
Runner images where you need the tool
Can this tool be installed during the build?
No response
Tool installation time in runtime
No response
Are you willing to submit a PR?
If I know where to make the necessary changes in the repo, I'd be happy to make a PR.
The text was updated successfully, but these errors were encountered: