Am 11.01.2014 09:43, schrieb Nick Coghlan: > On 11 January 2014 12:28, Ethan Furman <et...@stoneleaf.us> wrote: >> On 01/10/2014 06:04 PM, Antoine Pitrou wrote: >>> >>> On Fri, 10 Jan 2014 20:53:09 -0500 >>> "Eric V. Smith" <e...@trueblade.com> wrote: >>>> >>>> >>>> So, I'm -1 on the PEP. It doesn't address the cases laid out in issue >>>> 3892. See for example http://bugs.python.org/issue3982#msg180432 . >>> >>> >>> Then we might as well not do anything, since any attempt to advance >>> things is met by stubborn opposition in the name of "not far enough". >> >> >> Heh, and here I thought it was stubborn opposition in the name of purity. >> ;) > > No, it's "the POSIX text model is completely broken and we're not > letting people bring it back by stealth because they want to stuff > their esoteric use case back into the builtin data types instead of > writing their own dedicated type now that the builtin types don't > handle it any more". > > Yes, we know we changed the text model and knocked wire protocols off > their favoured perch, and we're (thoroughly) aware of the fact that > wire protocol developers don't like the fact that the default model > now strongly favours the vastly more common case of application > development. > > However, until Benno volunteered to start experimenting with > implementing an asciistr type yesterday, there have been *zero* > meaningful attempts at trying to solve the issues with wire protocol > manipulation outside the Python 3 core
Can we please also include pseudo-binary file formats? It's not "just" wire protocols. Georg _______________________________________________ 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
