Closed trentks closed 4 years ago
From memory the encode
call was there because sometimes field names had weird characters e.g. μF
and otherwise would not render properly.
Can you test this patch against fields with strange chars?
Hi @SchrodingersGat,
I see the issue, this latest commit should allow for UTF-8 encodings out in both python2 and python 3 (like μF
) .
Should be ready to merge now.
Cheers.
Ok I think I am happy with this approach. Thanks for your contribution :)
Hi @SchrodingersGat and @martinjaeger,
I've found this--this should solve #45.
Encoding was causing strings to be wrapped with b'', this appears to represent a binary encoding. Removing the encode removes this wrapping of b'' in python 3.
Tested with python 2.7.15, and 3.7.0, appears to work fine in both, but I don't know what purpose the encode was initially meant to fulfill. So my part names/descriptions/other fields might not have certain problematic characters, which the encode may have been used to sanitise?