10-28-2019, 02:11 PM
(This post was last modified: 10-28-2019, 02:11 PM by remkonoteboom.)
Python3 eliminated a lot of issues with unicode and strings in general, so that is welcome so I think you are seeing a bug in the Python3 implementation. However, this code was written a long time ago ... a time when json was pretty new and the python version was very slow (was implemented in python) and we used unicode because it was simply a lot faster.
This is no longer true. Json actually is now a lot faster than str() and eval() so I think all of this should all eventually be implemented in JSON. It would be rather simple to convert this however there may be backwards compatibility issues.
This is no longer true. Json actually is now a lot faster than str() and eval() so I think all of this should all eventually be implemented in JSON. It would be rather simple to convert this however there may be backwards compatibility issues.