3 ms·
I’ve worked in a variety of Django codebases, and the last time I had trouble with string encoding/decoding was with Python 2. Since moving to Python 3, I have
by CaptainMarvel 7y ago
I’ve worked in a variety of Django codebases, and the last time I had trouble with string encoding/decoding was with Python 2. Since moving to Python 3, I have rarely needed to manually encode or decode, and I genuinely can't remember the last time I did.
Perhaps there’s something about a port that requires encoding/decoding bytes/strings?
- takeda 7y agoThe encoding/decoding is heavy in codebases that have to run on Python 2 and Python 3 at the same time, and authors are worried about handling unicode correctly on python 2. Ironically when your python 2 app doesn't care about unicode, the porting to python 3 is actually much easier.