On Jun 20, 2010, at 6:21 PM, Terry Reedy <tjreedy at udel.edu> wrote: > On 6/20/2010 4:10 PM, Jesse Noller wrote: >> On Sun, Jun 20, 2010 at 2:40 PM, P.J. Eby<pje at telecommunity.com> >> wrote: > >>> While reading over this thread, I'm wondering whether at least my >>> (WSGI-related) problems in this area would be solved by the >>> availability of >>> a type (say "bstr") that was simply a wrapper providing string- >>> like behavior >>> over an underlying bytes, byte array, or memoryview, that would >>> produce >>> objects of compatible type when combined with strings (by encoding >>> them to >>> match). > >> I hate to reply with a simple +1 - but I've heard this pain and >> proposal from a frightening number of people, something which allowed >> you to use bytes with some of the sting methods would go a really >> long >> way to solving a lot of peoples python 3 pain. I don't relish the >> idea >> that once people start moving over, there might be a billion >> implementations of "things like this". > > Given that the 3.x bytes and bytearray classes do retain text > methods like .capitalize(), which are meaningless for arbitrary > binary data, it is not clear to me what you are asking for or what > problem a new class would solve. I am curious though. > Ask the web-sig and wsgi folks for starters. I know they've experienced non-zero pain.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4