PR: Use Python 3.9.14 for x86_64 macOS application build #21770
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mrclary
force-pushed
the
x86-fix
branch
2 times, most recently
from
ed9609d to
17ddd62
Compare
|
@ccordoba12, the x86_64 artifact works properly on my local machine. I think we're good to go. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of Changes
Spyder 5.5.1rc0 macOS x86_64 exhibits
This exhibited previously for local arm64 builds and seemed to be the result of incorrect tcl-tk Python build flags. However, this did not exhibit for Python 3.9.14 x86_64. I suspect that there is a change in the
setup-pythonbuild flags between 3.9, 3.10, x86_64, and arm64. Nevertheless, the easiest fix right now is to revert to 3.9.14 for x86_64. 🤞🏼