4 ms·
I feel like Python 3 has largely resolved the bytes vs characters problem. Byte arrays and strings are different classes in Py3. File and socket I/O deals onl
by Sohcahtoa82 7y ago
I feel like Python 3 has largely resolved the bytes vs characters problem. Byte arrays and strings are different classes in Py3. File and socket I/O deals only in byte arrays which are treated more like lists than strings. To perform a lot of string-like operations, you have to explicitly decode the byte array into a string. If you get it wrong, you'll likely get either a TypeError.
- jrockway 7y agoThis is good, but I'd prefer the error to occur at compile time. Consider the case where you do something like creating an error message because you can't open a file, and want to include the filename. The filename is bytes, the error message is a string, so instead of being able to print the error message, you instead throw an undebuggable exception. Dunno if that in particular is a problem in Python or not... but it is the sort of thing to watch out for.
- Sohcahtoa82 7y agoIn Python, filenames can be either bytes or string. Also, I made a mistake in my previous post. File I/O can deal with bytes OR strings depending on the parameters sent to the `open()` function. file_handle = open('somefile.txt') This opens the file in text mode (so `file_handle.read()` returns strings) using a platform-dependent encoding. On Windows, this will probably be CP-1252. On Linux, UTF-8. Of course, you can always explicitly choose the encoding: file_handle = open('somefile.txt', encoding='utf8') If you know you want to only deal with bytes, you can explicitly set that: file_handle = open('somefile.ext', mode='rb') I agree that it'd be nice to be able to see bytes vs strings errors at compile time, but this is difficult or even impossible with a duck-typed interpreted language like Python. IDEs and linters can make a good attempt at it, but they're not perfect.
- Eli_P 7y agoThere's another issue with Unicode: the same string can be encoded in many ways, which affects at least collation. On server side I deal with it with normalization[1]. I'm sure I can do it on the client with js but that just doesn't feel right. While rendering unsafe content still can be useful, I think Google better off added trusted-types as a tag attribute for WebComponents, like per-component CSP, and not into CSP header. [1] https://docs.python.org/3/library/unicodedata.html#unicodedata.normalize https://docs.python.org/3/library/unicodedata.html#unicodeda...