I'm as big a fan as ujson as the next but it would be nice to have json parsing/serialization degrade gracefully if you can't fullfill the requirement. Be happy to submit a PR, would look more or less would like what bottle does
abuckenheimer
All 6 comments
What's the issue with ujson?
seemethere
on 16 Feb 2017
it's just slightly less portable than the stdlib verison, for example I hit a
ImportError: /lib64/libc.so.6: version 'GLIBC_2.14' not found
on rhel6 but it works fine on rhel7. I'll probably find a way to work around that somehow but be an easy change if here if it makes sense to you.
abuckenheimer
on 16 Feb 2017
I'm fine with using that logic but let's leave it in requirements.txt imo.
r0fls
on 16 Feb 2017
awesome, thanks all
abuckenheimer
on 16 Feb 2017
ujson is great but looks like it has lost steam, including open issues and PRs about segfaults and memory leaks. Rapidjson looks more healthy these days, though ideally the json codec used by Sanic should be configurable. I can work on a PR if you agree.
gsakkis
on 23 Apr 2017
it would be much better to use rapidjson instead ujson.
SiDChik
on 13 Mar 2018
Related issues
davidtgq
路
3Comments
olalonde
路
3Comments
sirex
路
4Comments
aiurlano
路
4Comments
eseglem
路
4Comments
Most helpful comment
ujsonis great but looks like it has lost steam, including open issues and PRs about segfaults and memory leaks. Rapidjson looks more healthy these days, though ideally the json codec used by Sanic should be configurable. I can work on a PR if you agree.