> I'm personally leaning slightly towards strings, putting the burden on > bytes-users of json to explicitly use the appropriate encoding, even in > cases where it *must* be utf8. On the other hand, I'm too lazy to dig > back through this large thread, but I seem to recall a suggestion that > using bytes would be significantly faster. Not sure whether it would be *significantly* faster, but yes, Bob wrote an accelerator for parsing out of a byte string to make it really fast; IIRC, he claims that it is faster than pickling. Regards, Martin
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4