[go: up one dir, main page]
Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Forcing the use of UTF-8 for file I/O to fix errors on Centos 7 #6

Merged
merged 1 commit into from
Jun 19, 2023
Merged

Forcing the use of UTF-8 for file I/O to fix errors on Centos 7 #6

merged 1 commit into from
Jun 19, 2023

Conversation

joosthooz
Copy link
Contributor

I don't know if you'd want to force UTF8 at all of these spots, or if there is even a more elegant way to handle this, but this fixes this type of errors for me on Centos 7:

UnicodeEncodeError: 'ascii' codec can't encode character '\u2026' in position 2658: ordinal not in range(128)

jvanstraten
jvanstraten approved these changes Jun 19, 2023
View reviewed changes
Copy link
Collaborator
@jvanstraten jvanstraten left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

While messing around with vhdmmio again I saw that pylint also complains about this. LGTM anyway. 2 years later...

@jvanstraten jvanstraten merged commit d041792 into abs-tudelft:master Jun 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@jvanstraten jvanstraten jvanstraten approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@joosthooz @jvanstraten