Python3 Non-ASCII character Mistery

I try repair this installing a devel packages with: sudo eopkg install -c system.devel

But.. Mmm... Not solve this. 👀

How to...

Simply try print "ñ" cause error....

print("ñ")

python is python2 on Solus. So use #!/usr/bin/env python3

Oh, you are right! Thanks!

... But a other packages from flatpak can use python show this and not execute...

It loads fine for me. 🤷‍♂️

Harvey Change the system languaje to spanish. And review.

This error only works with "special ascii" like "à. ṕ, ñ...".

As the developer said it appears to be an issue with gettext: https://codeberg.org/lo-vely/echo/issues/18

I've never dealt with translations stuff but looking at the translations for other languages in this project I think I found the error. https://codeberg.org/lo-vely/echo/src/branch/master/po/es.po#L8

It is only es.po which has header data in spanish. Every other file uses English in the header so I assume that is what gettext expects. For example see finish: https://codeberg.org/lo-vely/echo/src/branch/master/po/fi.po#L9

Harvey Yes, but.. See this another application:

And I tried to run it on other distributions: Debian, Arch Linux, and Fedora.

Results: Applications runs ok.

This error only works in Solus.

Then I have no idea. We also use gettext for translations including in python3 version of eopkg and to my knowledge they work fine.

EDIT: Additionally I could load Italian translations fine.

It looks common error in Python2 era.

I recommend

reading PEP 263 as error message suggested
Putting next code at top of your code.
# -*- coding: utf-8 -*-
You may also need to put shabang as
# !/opt/local/bin/python
#!/usr/bin/env python3

I installed Fedora 42 in a VM with Spanish as my locale, updated, restarted, installed both Echo and AddWater flatpaks and get the same error.

So I remain unconvinced this is a Solus problem.

You're absolutely right... But I had just tested it on a real machine recently.

But then this error is really new, because I was using addwater a week ago in Fedora 42...

Where could this error be coming from then?

I'll try to investigate to find it, sorry for wasting your time...

DinimixisDEMZ Where could this error be coming from then?

Well, the app, most likely