correct encoding of generated *_ui.py files on windows system#1837
Merged
Conversation
i18n test was failing on windows because generated *_ui.py files from pyside6-uic were not utf-8.
Contributor
|
I tested PySide6 6.11.0 on macOS and got a lot of the log entries: Let's bump the PySide6 version in a separate PR since it requires some more testing and possibly fixing. |
mkrnr
approved these changes
Apr 9, 2026
Contributor
Author
|
I get the same entries about cannot copy-convert but with Not sure what the impact is since keyboard and translation seem to work properly. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 of changes
tox i18n test was failing on windows because generated *_ui.py files from pyside6-uic were not utf-8.
Pull Request Checklist