On Thu, Jan 16, 2014 at 3:06 PM, Jan Kaliszewski <z...@chopin.edu.pl> wrote: > I'd treat the format()+.__format__()+str.format()-"ecosystem" as > a nice text-data-oriented, *complete* Py3k feature, backported to > Python 2 to share the benefits of the feature with it as well as > to make the 2-to-3 transition a bit easier. > > IMHO, the PEP-3101's note cited above just describes a workaround > over the flaws of the Py2's obsolete text model. Moving such > complications into Py3k would make the feature (and especially the > ability to implement your own .__format__()) harder to understand > and make use of -- for little profit. > > Such a move is not needed for compatibility. And, IMHO, the > format()/__format__()/str.format()-matter is all about nice and > flexible *text* formatting, not about binary data interpolation.
[disclaimer: I personally don't have many use cases for any bytes formatting.] Yet there is still a strong symmetry between str and bytes that makes bytes easier to use. I don't always use formatting, but when I do I use .format(). :) never-been-a-fan-of-mod-formatting-ly yours, -eric _______________________________________________ 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
