Open ErikKalkoken opened 3 years ago
@ErikKalkoken thank you for reporting. Internal issue EO-12177 has been created.
Just encountered this as well. Here's an additional scenario if that helps:
curl -X GET "https://esi.evetech.net/latest/characters/96829083/?datasource=tranquility" -H "accept: application/json"
"description": "u'<font size=\"13\" color=\"#b3ffffff\"></font><font size=\"13\" color=\"#ffff0000\"> (\\\\/) (\\\\/)<br> \\\\\\\\ ( \\xb0 ,,,, \\xb0 ) //<br> /\\u203e/|\\\\ /|\\\\\\u203e\\\\<br>-------------------------<br>https://i.imgur.com/2PTRn0i.gif</font>'"
I work around this issue by directly altering the string and removing content between "description:" and the fields that come after. Then parse the JSON.
Unless you want to keep the description content for some reason, remove the problem.
Unfortunately, I'm specifically looking for the description.
Any update on when this bug will be fixed?
Here is another recent example that has this bug: https://esi.evetech.net/latest/characters/96344624
Sadly, this bug is still not fixed as of today.
Bug
When requesting the characters information for certain characters, the string returned for the
description
attribute appears to be in Python format. Instead of a normal string like"Zuverlässigkeit"
you get"u'Zuverlässigkeit'"
.This looks like the Python notation for UTF-8 strings. This currently only happens for some characters. We suspect it maybe related to
description
strings that contain Unicode letters.The strings returned by the endpoint should not contain Python identifiers. In the current form any app has to manually resolve those strings. (Fun fact: Python apps can resolve those strings with
ast.literal_eval(text)
)Request
Response
Status Code
200
Headers
Body
Expected
Checklist
Check all boxes that apply to this issue: