Build with Qt 6.7.0 on windows and macos #2420
Closed
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
phw
force-pushed
the
upgrade-qt6-windows-mac-builds
branch
2 times, most recently
from
9f4d2e9
to
80b2075
Compare
|
I don't really understand why the tests are segfaulting on macOS. I can't reproduce this here at all. |
phw
force-pushed
the
upgrade-qt6-windows-mac-builds
branch
from
80b2075
to
091a071
Compare
7 tasks
phw
force-pushed
the
upgrade-qt6-windows-mac-builds
branch
from
091a071
to
064d879
Compare
phw
changed the title
|
I'm closing this as there are currently too many issues with Qt 6.7 overall. We will get back to this, but likely only after we have moved to PySide6 and there is at least a 6.7.1 release available on pypi.. |
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.
Summary
Problem
Build with PyQt 6.6.1 and Qt 6.6.3 on both Windows and macOS.
Previously there have been issues running 6.6 on macOS, hence the version was pinned to 6.5.3 there. This change attempts to unify the version again between the plaforms.