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


Groups > comp.lang.python > #62489

Re: bytearray inconsistencies?

From Mark Lawrence <breamoreboy@yahoo.co.uk>
Subject Re: bytearray inconsistencies?
Date 2013-12-21 12:29 +0000
References <l92phr$3b2$1@ger.gmane.org> <l92sju$ugd$1@ger.gmane.org>
Newsgroups comp.lang.python
Message-ID <mailman.4469.1387628971.18130.python-list@python.org> (permalink)

Show all headers | View raw


On 21/12/2013 01:58, Ned Batchelder wrote:
>
> If you have a zero, you can split on it with:
> bytestring.split(bytes([0])), but that doesn't explain why find can take
> a simple zero, and split has to take a bytestring with a zero in it.
>

Create a bytearray(range(256)) and partition it on 128.  I'd expect to 
see the original effectively cut in half with 128 as the separator.  You 
actually get the original with two empty bytearrays, which makes no 
sense to me at all.

I also looked in test_bytes.py, read as far as "XXX This is a mess" and 
promptly gave up.

-- 
My fellow Pythonistas, ask not what our language can do for you, ask 
what you can do for our language.

Mark Lawrence

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


Thread

Re: bytearray inconsistencies? Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-12-21 12:29 +0000
  Re: bytearray inconsistencies? Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-12-21 13:13 +0000

csiph-web