Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #63345

Re: "More About Unicode in Python 2 and 3"

From Ned Batchelder <ned@nedbatchelder.com>
Subject Re: "More About Unicode in Python 2 and 3"
Date 2014-01-06 16:14 -0500
References (2 earlier) <CAGGBd_qBA0OBELxgzERO4Tfs6quK7oYq8v_2idA=K2ycoiO6Dg@mail.gmail.com> <mailman.5022.1389022306.18130.python-list@python.org> <52cae78d$0$29971$c3e8da3$5496439d@news.astraweb.com> <52CAF722.6010301@stoneleaf.us> <CAMjeLr9w8ZaBO6GaFtfQPs=D7Q0M9M718thyjLDwTico2FC07Q@mail.gmail.com>
Newsgroups comp.lang.python
Message-ID <mailman.5063.1389042912.18130.python-list@python.org> (permalink)

Show all headers | View raw


On 1/6/14 2:30 PM, Mark Janssen wrote:
>>> Chris didn't say "bytes and ascii data", he said "bytes and TEXT".
>>> Text != "ascii data", and the fact that some people apparently think it
>>> does is pretty much the heart of the problem.
>>
>> The heart of a different problem, not this one.  The problem I refer to is
>> that many binary formats have well-defined ascii-encoded text tidbits.
>
> Really?  If people are using binary with "well-defined ascii-encoded
> tidbits", they're doing something wrong.  Perhaps you think escape
> characters "\n" are "well defined tidbits", but YOU WOULD BE WRONG.
> The purpose of binary is to keep things raw.  WTF?  You guys are so
> strange.
>
>>
>>> If you (generic you) don't get that, you'll have a bad time. I mean
>>> *really*
>>> get it, deep down in the bone. The long, bad habit of thinking as
>>> ASCII-encoded bytes as text is the problem here.
>
> I think the whole forking community is confused at because of your own
> arrogance.  Foo(l)s.
>
> markj
>

If you want to participate in this discussion, do so.  Calling people 
strange, arrogant, and fools with no technical content is just rude. 
Typing "YOU WOULD BE WRONG" in all caps doesn't count as technical content.

-- 
Ned Batchelder, http://nedbatchelder.com

Back to comp.lang.python | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Re: "More About Unicode in Python 2 and 3" Ethan Furman <ethan@stoneleaf.us> - 2014-01-06 07:10 -0800
  Re: "More About Unicode in Python 2 and 3" Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-01-07 04:27 +1100
    Re: "More About Unicode in Python 2 and 3" Ethan Furman <ethan@stoneleaf.us> - 2014-01-06 10:34 -0800
      Re: "More About Unicode in Python 2 and 3" Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-01-07 11:42 +1100
    Re: "More About Unicode in Python 2 and 3" Mark Janssen <dreamingforward@gmail.com> - 2014-01-06 13:30 -0600
    Re: "More About Unicode in Python 2 and 3" Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-01-06 19:36 +0000
    Re: "More About Unicode in Python 2 and 3" Mark Janssen <dreamingforward@gmail.com> - 2014-01-06 13:44 -0600
      Re: "More About Unicode in Python 2 and 3" Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-01-07 11:54 +1100
    Re: "More About Unicode in Python 2 and 3" Ned Batchelder <ned@nedbatchelder.com> - 2014-01-06 16:14 -0500
    Re: "More About Unicode in Python 2 and 3" Mark Janssen <dreamingforward@gmail.com> - 2014-01-06 15:23 -0600
    Re: "More About Unicode in Python 2 and 3" Mark Janssen <dreamingforward@gmail.com> - 2014-01-06 15:32 -0600
    Re: "More About Unicode in Python 2 and 3" Chris Angelico <rosuav@gmail.com> - 2014-01-07 10:03 +1100

csiph-web