Skip to content

Fix UTF-8 file I/O on IronPython by using codecs.open instead of io.open - #41

Open
pstoeckli wants to merge 3 commits into
greenforge-labs:mainfrom
pstoeckli:fix/ironpython-utf8-file-io
Open

pstoeckli wants to merge 3 commits into
greenforge-labs:mainfrom
pstoeckli:fix/ironpython-utf8-file-io

Conversation

@pstoeckli

Copy link
Copy Markdown

open_utf8() used io.open(path, mode, encoding="utf-8"). On the IronPython 2.7 runtime CODESYS's ScriptEngine uses, encoding resolution for io.open is unreliable and can silently fall back to the OS ANSI code page instead of true UTF-8. This corrupts any non-ASCII character (umlauts, accented letters, smart punctuation, Cyrillic) on export, and the next Import From Files then fails with UnicodeDecodeError: 'unknown' codec can't decode byte ....

Switching to codecs.open(path, mode, encoding="utf-8"), the long-standing, well-supported way to do UTF-8 text I/O on Python 2 / IronPython, fixes a full export → import round-trip that previously failed as soon as the project contained non-ASCII text (e.g. German comments with umlauts).

Tested locally: export → import round-trip now succeeds on a project with German-language comments (previously failed with the UnicodeDecodeError above).
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant