Sorry, found a couple more comments in a different thread. Here's what I added:
+Objections +========== + +The objections raised against this PEP were mainly variations on two themes:: + + - the ``bytes`` and ``bytearray`` types are for pure binary data, with no + assumptions about encodings + - offering %-interpolation that assumes an ASCII encoding will be an + attractive nuisance and lead us back to the problems of the Python 2 + ``str``/``unicode`` text model + +As was seen during the discussion, ``bytes`` and ``bytearray`` are also used +for mixed binary data and ASCII-compatible segments: file formats such as +``dbf`` and ``pdf``, network protocols such as ``ftp`` and ``email``, etc. + +``bytes`` and ``bytearray`` already have several methods which assume an ASCII +compatible encoding. ``upper()``, ``isalpha()``, and ``expandtabs()`` to name +just a few. %-interpolation, with its very restricted mini-language, will not +be any more of a nuisance than the already existing methdods. + + _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
