-
-
Notifications
You must be signed in to change notification settings - Fork 12.5k
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
[email protected]: promote to default python3 #150390
Conversation
So far without Linux
|
Might be worth revision bumping so the user doesn't end up in a scenario where they have Python 3.12 already installed but no |
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. |
What is blocking this PR right now? I can lend a hand. |
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. |
This appears to still be good. |
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. |
This appears to still be good. I'm still not sure why we wouldn't want to migrate to the newest version, especially considering the typing improvements. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awaiting #150390 (comment)
Which may also depend on #157500 if we decide to drop majority of |
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. |
tkinter is no longer included with this formula, but it is available separately: | ||
brew install python-tk@#{version.major_minor} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did we want to remove this caveat? There is also the python-gdbm
caveat in [email protected]
that didn't carry over to [email protected]
.
[email protected]
and [email protected]
will remain as they are part of base Python but we just put them into separate formulae (given that Homebrew doesn't support sub/split-packages).
Not important to handle here but may want to add caveats in follow up.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree that it makes sense to handle this in a followup syntax PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I removed that line because it now felt useless. We had it for a few years now I think. I hope our users have adjusted their workflows, and my hope was to stop telling obvious things in the caveats.
But if you think we need to add it back: this can be done in a syntax-only follow-up pull request.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It doesn't matter to me whether we keep or remove it.
Homebrew's way of separate formulae is a bit odd since we don't support sub/split-packages. Most repositories would either install everything together (e.g. Arch Linux) or use subpackages (which colocates the related packages that use the same source distribution).
Failures that can be followed up on:
|
Thanks for all the work here @branchvincent! |
And thanks @iMichka for all the doc updates! |
relates to Homebrew/homebrew-core#150390 Signed-off-by: Rui Chen <[email protected]>
acc06bc ci, macos: Use `--break-system-packages` with Homebrew's python (Hennadii Stepanov) ae5f720 ci: Add workaround for Homebrew's python link error (Hennadii Stepanov) Pull request description: Homebrew [promoted](Homebrew/homebrew-core#150390) `[email protected]` to the default `python3`. Now, our "macOS native" CI job is facing the following issues: 1. Installing `qt@5` [requires](https://github.com/bitcoin/bitcoin/actions/runs/8216848118/job/22471875454#step:4:51) re-installing `[email protected]`: ``` ==> Fetching dependencies for qt@5: readline, [email protected] and gettext ``` 2. Re-installing `[email protected]` [fails](https://github.com/bitcoin/bitcoin/actions/runs/8216848118/job/22471875454#step:4:127) due to symbolic link conflicts on macOS `x86_64`: ``` ==> Pouring [email protected]_1.ventura.bottle.tar.gz Error: The `brew link` step did not complete successfully ``` 3. Homebrew's `[email protected]` is marked as externally managed (according to PEP 668), necessitating different approaches for installing Python packages. This pull request resolves all the issues mentioned above. ACKs for top commit: m3dwards: reACK acc06bc to get the CI passing again. Tree-SHA512: 82cf72bff328f1e0725342431ac14ad4bae7a758186d97db6c7a558e4b661dcbf3fabe536978e26e709c5f6f7f5c11aac46642634c6685f1291592d8d825ad87
HOMEBREW_NO_INSTALL_FROM_API=1 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 doingHOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>
)? If this is a new formula, does it passbrew audit --new <formula>
?Hopefully this is a smoother transition than last year since all formulae should now be using fully-qualified python binaries like
python3.11