Home › Forums › Help and Support › JSONEncoder.__init__() got an unexpected keyword argument ‘encoding’
- This topic has 4 replies, 2 voices, and was last updated 3 months, 1 week ago by
Tech.
-
AuthorPosts
-
2026-02-23 at 22:54 #145492
I spent about 8 hours today trying to get this to work and no matter what, I get this error.
I’m on EndeavourOS – It is up to date as of today and so are the 9070xt drivers
I’m normally running wayland, but I tried x11 also and no difference
I have a i1 Display (pro I think) meter
Here is the error. Please help! Thanks
JSONEncoder.__init__() got an unexpected keyword argument 'encoding' Traceback (most recent call last): File "/usr/lib/python3.14/site-packages/wx/core.py", line 3425, in <lambda> lambda event: event.callable(*event.args, **event.kw) ) ~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.14/site-packages/DisplayCAL/wxwindows.py", line 1383, in finish_processing state = self.get_app_state("plain") File "/usr/lib/python3.14/site-packages/DisplayCAL/wxwindows.py", line 1218, in get_app_state response = format_ui_element(win, format) File "/usr/lib/python3.14/site-packages/DisplayCAL/wxwindows.py", line 8015, in format_ui_element (child.Label and " " + demjson.encode(child.Label)), ~~~~~~~~~~~~~~^^^^^^^^^^^^^ File "/usr/lib/python3.14/site-packages/DisplayCAL/demjson_compat.py", line 153, in encode return json.dumps( ~~~~~~~~~~^ obj, ^^^^ ...<3 lines>... encoding=encoding or "utf-8", ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ) ^ File "/usr/lib/python3.14/json/__init__.py", line 238, in dumps return cls( ~~~^ skipkeys=skipkeys, ensure_ascii=ensure_ascii, ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ check_circular=check_circular, allow_nan=allow_nan, indent=indent, ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ separators=separators, default=default, sort_keys=sort_keys, ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ **kw).encode(obj) ^^^^^ TypeError: JSONEncoder.__init__() got an unexpected keyword argument 'encoding'2026-02-24 at 0:56 #145493I tried it again on my other rig running cachyos and nvidia with the same result
Attached is the entire process of installing, running, erroring, everything
Attachments:
You must be logged in to view attached files.2026-02-24 at 1:14 #145495In my opinion Windows version of displaycal 3.9.17 seems more stable than on linux. Maybe find a issue report that was fixed and use that version of displaycal. https://github.com/eoyilmaz/displaycal-py3/issues . If you have the 3.9.17 version Eoyilmaz is the developer and has some helpers. Thanks for the bug report. You need to send it to github. Maybe you can find the issue listed on github. My only guess is to change python version. There was one version that did not work. I dont know why his homepage is gone. https://eoyilmaz.github.io/displaycal-py3/ . It had the py3 versions that worked.
2026-02-24 at 1:22 #145496Python 3.9 to 3.13 is supported. https://github.com/eoyilmaz/displaycal-py3/commit/0a5f3cbb8573d78418d8315d9e0b9c204dfb002b
2026-02-24 at 3:50 #145497Thank you so much for the reply. You nailed it; I’m on py 3.14. I just ran the Flatpak to get past it (which worked) until I have the ambition setup to run it on 3.13.
I looked for a git earlier but didn’t find it so apparently I did try hard enough. Thank you for the link. I will post there too. I think if they just support 3.14 all should be good but they will know better than I.
I may also setup a win dualboot tomorrow and test that out as well.
Thanks again for the help!!
-
AuthorPosts