Python comes to the Casio fx-CG 50

[bxparks]

(12-26-2024 09:37 PM)StephenG1CMZ Wrote:  One consequence of the lack of Unicode is there is no copyright ©️ symbol. The documentation does mention that ASCII must be used, but never makes clear what to expect if the source contains one.
Leaving one wondering whether to expect an alternative symbol printed, a compilation error or a factory reset?

Just to make sure that we are on the same page: When I say "unicode support" in MicroPython, I looking at whether the internal implementation of the `str` type in the Python interpreter supports unicode characters. Not whether the Python interpreter supports unicode characters embedded in the source file.

Generally, I never use unicode characters within the source code. I stick to ASCII characters only. Because too many programming tools don't work correctly with unicode (e.g. searching for text inside or outside editors) And I really hate seeing emojis, flags icons, and other such things inside the source code. The darned things are often unrecognizable due to the fonts used by text editors on various computers. So in your example, the copyright symbol would be replaced with (c) in the source file.

But any modern programming language ought to be able to read, manipulate, and write unicode characters. The CG50 MicroPython v1.9.4 cannot do that, because its internal `str` type cannot represent unicode characters.