python: make python@3.11 the new default for python3#114154
Conversation
|
Please provide a better issue/pull request title and/or description! |
|
Also needs changes in See #107517. |
@carlocab, thank you for clarifying, I didn't thought about that but it's certainly mandatory, I've applied the sensible changes, hopefully nothing missed. |
carlocab
left a comment
There was a problem hiding this comment.
Nice work! Could you split your commit so that you have at least two commits:
- one that modifies
python@3.11.rb - one that modifies
python@3.10.rb
Adding a third commit only for the symlinks works fine too.
Let me know if you need help with this.
|
https://github.com/Homebrew/homebrew-core/actions/runs/3349533474/jobs/5549658710
|
|
@ryenus the "long build" label indicates to maintainers that this build will need a "CI-long-timeout" label and they will add one when it's available. |
|
Got it, thank you for the clarification @SMillerDev. |
|
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
|
Hi @ryenus , is there any progress on this? I was paying attention to this to make sure I could release MacVim with the correct pinned Python 3 version and was wondering if this was going to be merged considering the PR was filed more than a month ago. Thanks! |
|
Kicking off a run |
Update formula **tsduck** to use python@3.11 instead of python@3.10 see the related pr #114154
Update formula **udis86** to use python@3.11 instead of python@3.10 see the related pr #114154
|
Can I ask what the status on this PR might be? The specific issue I face is that I accidentally upgraded |
|
We need to run tests to merge this PR, but explicit approval from a maintainer ( |
|
The load on CI is pretty light right now. I will rebase and rerun this with the long timeout this evening unless @chenrui333 beats me to it 😉 |
|
Thanks @p-linnane! :) |
Failures on all platform
DetailsFailures on some platform
Details
|
|
At this point, I wonder whether the issue with |
|
I rebased and tweaked the commit messages to follow our commit style. This should be good to merge after one more run, we can handle |
|
Kicking off a run. |
I checked the |
branchv
left a comment
There was a problem hiding this comment.
Couple new failures are from a flaky network, merging
|
|
Switch python3 aliases from python@3.10 to python@3.11, following up #113811
brew install --build-from-source <formula>, where<formula>is the name of the formula you're submitting?brew test <formula>, where<formula>is the name of the formula you're submitting?brew audit --strict <formula>(after doingbrew install --build-from-source <formula>)? If this is a new formula, does it passbrew audit --new <formula>?Query for related formulae pr(s):
is:pr label:python-3.11-migration is:open