On 08/01/2014 23:34, rdst...@mac.com wrote:
I'm so sorry for the mess in my post above, I apologize to all, I accidentally
hit return ...
I just meant to say that internet programming using ASCII urls is so common and
important that it hurts that Python 3 makes it so much harder. It sure would
On Thu, Jan 9, 2014 at 10:34 AM, wrote:
> I just meant to say that internet programming using ASCII urls is so common
> and important that it hurts that Python 3 makes it so much harder. It sure
> would be great if Python 3 could be improved to allow such programming to be
> done using ASCII u
I'm so sorry for the mess in my post above, I apologize to all, I accidentally
hit return ...
I just meant to say that internet programming using ASCII urls is so common and
important that it hurts that Python 3 makes it so much harder. It sure would be
great if Python 3 could be improved to al
Chris A wrote:
I'm not sure that there is an "easy way". See, here's the deal. If all
your data is ASCII, you can shut your eyes to the difference between
bytes and text and Python 2 will work perfectly for you. Then some day
you'll get a non-ASCII character come up (or maybe you'll get all of
On Mon, 06 Jan 2014 22:41:26 +, Nicholas Cole wrote:
[...]
> Like everyone else, when Python 3 came out I was nervous. A lot of my
> code broke - but it broke for a good reason. I had been being cavalier
> about strings and ASCII and bytes. A lot of my code was working by
> accident rather
On 1/6/14 11:01 PM, Steven D'Aprano wrote:
On Mon, 06 Jan 2014 16:32:01 -0500, Ned Batchelder wrote:
On 1/6/14 12:50 PM, Steven D'Aprano wrote:
Ned Batchelder wrote:
You are still talking about whether Armin is right, and whether he
writes well, about flaws in his statistics, etc. I'm talki
On 1/6/14 5:30 PM, Mark Lawrence wrote:
On 06/01/2014 22:22, Ned Batchelder wrote:
On 1/6/14 5:08 PM, Mark Lawrence wrote:
On 06/01/2014 21:42, Ned Batchelder wrote:
On 1/6/14 4:33 PM, Mark Lawrence wrote:
That strikes me as being as useful as "The PEP 393 FSR is completely
wrong but I'm not
On Mon, 06 Jan 2014 16:32:01 -0500, Ned Batchelder wrote:
> On 1/6/14 12:50 PM, Steven D'Aprano wrote:
>> Ned Batchelder wrote:
>>
>>> You are still talking about whether Armin is right, and whether he
>>> writes well, about flaws in his statistics, etc. I'm talking about
>>> the fact that an org
On Tue, Jan 7, 2014 at 1:42 PM, Terry Reedy wrote:
> I am pleased to see that the bug-fix releases get downloaded so heavily.
That's a tricky one, though. It's impossible to say how many 3.3.1
downloads were upgrading from 3.3.0, and how many were simply "I want
Python, give me the latest". But e
On 1/6/2014 6:24 PM, Chris Angelico wrote:
On Tue, Jan 7, 2014 at 10:06 AM, Antoine Pitrou wrote:
Terry Reedy udel.edu> writes:
On 1/6/2014 11:29 AM, Antoine Pitrou wrote:
People don't use? According to available figures, there are more
downloads of
Python 3 than downloads of Python 2 (W
On Tue, Jan 7, 2014 at 1:15 PM, Rhodri James wrote:
> Sorry, I assumed we were talking about threads in general. Py2 vs Py3
> threads that aren't interminable trolling don't show up often enough to
> register for me; the current set is something of an exception.
Sure. In that case, I would agree
On 1/6/2014 5:25 PM, Ned Batchelder wrote:
I do respect you, and all the core developers. As I've said elsewhere
in the thread, I greatly appreciate everything you do. I dedicate a
great deal of time and energy to the Python community, primarily because
of the amazing product that you have all
On Tue, 07 Jan 2014 01:35:54 -, Chris Angelico
wrote:
On Tue, Jan 7, 2014 at 12:26 PM, Rhodri James
wrote:
On Mon, 06 Jan 2014 21:17:06 -, Gene Heskett
wrote:
On Monday 06 January 2014 16:16:13 Terry Reedy did opine:
On 1/6/2014 9:32 AM, Gene Heskett wrote:
> And from my lur
On Tue, Jan 7, 2014 at 12:26 PM, Rhodri James wrote:
> On Mon, 06 Jan 2014 21:17:06 -, Gene Heskett wrote:
>
>> On Monday 06 January 2014 16:16:13 Terry Reedy did opine:
>>
>>> On 1/6/2014 9:32 AM, Gene Heskett wrote:
>>> > And from my lurking here, its quite plain to me that 3.x python has a
On Mon, 06 Jan 2014 21:17:06 -, Gene Heskett wrote:
On Monday 06 January 2014 16:16:13 Terry Reedy did opine:
On 1/6/2014 9:32 AM, Gene Heskett wrote:
> And from my lurking here, its quite plain to me that 3.x python has a
> problem with everyday dealing with strings.
Strings of what? An
On Tue, Jan 7, 2014 at 11:23 AM, Dennis Lee Bieber
wrote:
>>Uhh, I think you're the only one here who has that nightmare, like
>>Chris Knight with his sun-god robes and naked women throwing pickles
>>at him.
>>
>
> Will somebody please wash out my brain... "Pickles straight from the
> jar,
Mark Janssen wrote:
>> Looks like another bad batch, time to change your dealer again.
>
> ??? Strange, when the debate hits bottom, accusations about doing
> drugs come up. This is like the third reference (and I don't even
> drink alcohol).
It is an oblique reference to the fact that your pos
Ethan Furman wrote:
> On 01/06/2014 09:27 AM, Steven D'Aprano wrote:
>> Ethan Furman 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
On Tue, Jan 7, 2014 at 10:06 AM, Antoine Pitrou wrote:
> Terry Reedy udel.edu> writes:
>>
>> On 1/6/2014 11:29 AM, Antoine Pitrou wrote:
>>
>> > People don't use? According to available figures, there are more
> downloads of
>> > Python 3 than downloads of Python 2 (Windows installers, mostly):
>
On 06/01/2014 23:14, Ben Finney wrote:
Mark Lawrence writes:
You arrogance really has no bounds. If you'd have done the job that
you should have done in the first place and stopped that blithering
idiot 16 months ago, we wouldn't still be putting up with him now.
That is a misdirection; Ned
On Tue, Jan 7, 2014 at 7:32 AM, Antoine Pitrou wrote:
> Chris Angelico gmail.com> writes:
>>
>> On Tue, Jan 7, 2014 at 3:29 AM, Antoine Pitrou pitrou.net>
> wrote:
>> > People don't use? According to available figures, there are more
> downloads of
>> > Python 3 than downloads of Python 2 (Windo
Mark Lawrence writes:
> You arrogance really has no bounds. If you'd have done the job that
> you should have done in the first place and stopped that blithering
> idiot 16 months ago, we wouldn't still be putting up with him now.
That is a misdirection; Ned's request that you stop bad behaviou
Terry Reedy udel.edu> writes:
>
> On 1/6/2014 11:29 AM, Antoine Pitrou wrote:
>
> > People don't use? According to available figures, there are more
downloads of
> > Python 3 than downloads of Python 2 (Windows installers, mostly):
> > http://www.python.org/webstats/
>
> While I would like the
On 06/01/2014 22:41, Nicholas Cole wrote:
I hardly know which of the various threads on this topic to reply to!
No one is taking Python 2.7 away from anyone. It is going to be on the
net for years to come. Goodness! I expect if I wanted to go and
download Python 1.5 I could find it easily enou
On Tue, Jan 7, 2014 at 8:32 AM, Mark Janssen wrote:
>>> 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 t
On 06/01/2014 22:35, Antoine Pitrou wrote:
Mark Lawrence yahoo.co.uk> writes:
[...]
And as I started this thread, I'll say what I please, throwing my toys
out of my pram in just the same way that your pal Armin is currently doing.
I'll join Ned here: please stop it. You are doing a disservi
On Tue, Jan 7, 2014 at 7:42 AM, Tim Chase wrote:
> On 2014-01-06 22:20, Serhiy Storchaka wrote:
>> data = b"\x43\x6c\x67\x75\x62\x61" # is there an easier way to
>> turn a hex dump into a bytes literal?
>>
>> >>> bytes.fromhex('43 6c 67 75 62 61')
>> b'Clguba'
>
> Very nice new function
>> I would still point out that "Kenneth and Armin" are not the whole Python
>> community.
>
> I never said they were the whole community, of course. But they are not
> outliers either. [...]
>
>> Your whole argument seems to be that a couple "revered" (!!)
>> individuals should see their complain
On 1/6/2014 11:29 AM, Antoine Pitrou wrote:
People don't use? According to available figures, there are more downloads of
Python 3 than downloads of Python 2 (Windows installers, mostly):
http://www.python.org/webstats/
While I would like the claim to be true, I do not see 2 versus 3
download
I hardly know which of the various threads on this topic to reply to!
No one is taking Python 2.7 away from anyone. It is going to be on the net
for years to come. Goodness! I expect if I wanted to go and download
Python 1.5 I could find it easily enough.
Like everyone else, when Python 3 came
Mark Lawrence yahoo.co.uk> writes:
> [...]
>
> And as I started this thread, I'll say what I please, throwing my toys
> out of my pram in just the same way that your pal Armin is currently doing.
I'll join Ned here: please stop it. You are doing a disservice to
everyone.
Thanks in advance
An
On 06/01/2014 22:22, Ned Batchelder wrote:
On 1/6/14 5:08 PM, Mark Lawrence wrote:
On 06/01/2014 21:42, Ned Batchelder wrote:
On 1/6/14 4:33 PM, Mark Lawrence wrote:
On 06/01/2014 21:17, Gene Heskett wrote:
On Monday 06 January 2014 16:16:13 Terry Reedy did opine:
On 1/6/2014 9:32 AM, Gene
On 1/6/14 5:16 PM, Antoine Pitrou wrote:
Ned Batchelder nedbatchelder.com> writes:
I never said they were the whole community, of course. But they are not
outliers either. By your own statistics above, 23% of respondents think
Python 3 was a mistake. Armin and Kenneth are just two very visib
On 1/6/14 5:08 PM, Mark Lawrence wrote:
On 06/01/2014 21:42, Ned Batchelder wrote:
On 1/6/14 4:33 PM, Mark Lawrence wrote:
On 06/01/2014 21:17, Gene Heskett wrote:
On Monday 06 January 2014 16:16:13 Terry Reedy did opine:
On 1/6/2014 9:32 AM, Gene Heskett wrote:
And from my lurking here, it
Ned Batchelder nedbatchelder.com> writes:
>
>
> I never said they were the whole community, of course. But they are not
> outliers either. By your own statistics above, 23% of respondents think
> Python 3 was a mistake. Armin and Kenneth are just two very visible
> people.
Indeed, they are
On 06/01/2014 21:42, Ned Batchelder wrote:
On 1/6/14 4:33 PM, Mark Lawrence wrote:
On 06/01/2014 21:17, Gene Heskett wrote:
On Monday 06 January 2014 16:16:13 Terry Reedy did opine:
On 1/6/2014 9:32 AM, Gene Heskett wrote:
And from my lurking here, its quite plain to me that 3.x python has a
On 1/6/2014 7:39 AM, Ned Batchelder wrote:
You are still talking about whether Armin is right, and whether he
writes well, about flaws in his statistics, etc.
That is how *I* decide whether someone is worth attending to. He failed.
> I'm talking about the fact that an organization
of volunte
On 1/6/14 4:33 PM, Mark Lawrence wrote:
On 06/01/2014 21:17, Gene Heskett wrote:
On Monday 06 January 2014 16:16:13 Terry Reedy did opine:
On 1/6/2014 9:32 AM, Gene Heskett wrote:
And from my lurking here, its quite plain to me that 3.x python has a
problem with everyday dealing with strings.
On Mon, Jan 6, 2014 at 1:02 PM, Mark Lawrence wrote:
> I find all this intriguing. People haven't found time to migrate from
> Python 2 to Python 3, but now intend finding time to produce a fork of
> Python 2 which will ease the migration to Python 3. Have I got that
> correct?
Keeping old, uns
On 1/6/14 11:29 AM, Antoine Pitrou wrote:
Ned Batchelder nedbatchelder.com> writes:
You can look through his problems and decide that he's "wrong," or that
he's "ranting," but that doesn't change the fact that Python 3 is
encountering friction. What happens when a significant fraction of your
On 06/01/2014 21:17, Gene Heskett wrote:
On Monday 06 January 2014 16:16:13 Terry Reedy did opine:
On 1/6/2014 9:32 AM, Gene Heskett wrote:
And from my lurking here, its quite plain to me that 3.x python has a
problem with everyday dealing with strings.
Strings of what? And what specific 'ev
>> 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?
>
> If you want to participate i
On 1/6/14 12:50 PM, Steven D'Aprano wrote:
Ned Batchelder wrote:
You are still talking about whether Armin is right, and whether he
writes well, about flaws in his statistics, etc. I'm talking about the
fact that an organization (Python core development) has a product
(Python 3) that is gettin
>> 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?
> If you want to participate in
On Monday 06 January 2014 16:16:13 Terry Reedy did opine:
> On 1/6/2014 9:32 AM, Gene Heskett wrote:
> > And from my lurking here, its quite plain to me that 3.x python has a
> > problem with everyday dealing with strings.
>
> Strings of what? And what specific 'everyday' problem are you referrin
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
On 06/01/2014 20:49, Terry Reedy wrote:
On 1/6/2014 8:44 AM, Mark Lawrence wrote:
On 06/01/2014 12:39, Ned Batchelder wrote:
I'm not talking about the technical details of bytes and Unicode. I'm
talking about making customers happy.
Simply scrap PEP 404
Not necessary.
and the currently
On 1/6/2014 10:10 AM, Ethan Furman wrote:
The argument is that a very important, if small, subset a data
manipulation become very painful in Py3. Not impossible, and not
difficult, but painful because the mental model and the contortions
needed to get things to work don't sync up anymore.
Tha
On 1/6/2014 8:44 AM, Mark Lawrence wrote:
On 06/01/2014 12:39, Ned Batchelder wrote:
I'm not talking about the technical details of bytes and Unicode. I'm
talking about making customers happy.
Simply scrap PEP 404
Not necessary.
and the currently unhappy customers will be happy
as they'
On 06/01/2014 20:42, Tim Chase wrote:
On 2014-01-06 22:20, Serhiy Storchaka wrote:
data = b"\x43\x6c\x67\x75\x62\x61" # is there an easier way to
turn a hex dump into a bytes literal?
>>> bytes.fromhex('43 6c 67 75 62 61')
b'Clguba'
Very nice new functionality in Py3k, but 2.x doesn't seem
On 2014-01-06 22:20, Serhiy Storchaka wrote:
> data = b"\x43\x6c\x67\x75\x62\x61" # is there an easier way to
> turn a hex dump into a bytes literal?
>
> >>> bytes.fromhex('43 6c 67 75 62 61')
> b'Clguba'
Very nice new functionality in Py3k, but 2.x doesn't seem to have such
a meth
On 06/01/2014 20:31, Serhiy Storchaka wrote:
06.01.14 15:44, Mark Lawrence написав(ла):
Simply scrap PEP 404 and the currently unhappy customers will be happy
as they'll be free to do all the work they want on Python 2.8, as my
understanding is that the vast majority of the Python core developer
Chris Angelico gmail.com> writes:
>
> On Tue, Jan 7, 2014 at 3:29 AM, Antoine Pitrou pitrou.net>
wrote:
> > People don't use? According to available figures, there are more
downloads of
> > Python 3 than downloads of Python 2 (Windows installers, mostly):
> > http://www.python.org/webstats/
> >
06.01.14 15:44, Mark Lawrence написав(ла):
Simply scrap PEP 404 and the currently unhappy customers will be happy
as they'll be free to do all the work they want on Python 2.8, as my
understanding is that the vast majority of the Python core developers
won't do it for them.
It's not necessary.
06.01.14 06:41, Tim Chase написав(ла):
from codecs import getencoder
getencoder("rot-13")(s2.decode('utf-8'))[0]
'Python'
codecs.decode('rot13', s2.decode())
--
https://mail.python.org/mailman/listinfo/python-list
06.01.14 06:51, Chris Angelico написав(ла):
data = b"\x43\x6c\x67\x75\x62\x61" # is there an easier way to turn a hex dump
into a bytes literal?
>>> bytes.fromhex('43 6c 67 75 62 61')
b'Clguba'
--
https://mail.python.org/mailman/listinfo/python-list
On 1/6/2014 9:32 AM, Gene Heskett wrote:
And from my lurking here, its quite plain to me that 3.x python has a
problem with everyday dealing with strings.
Strings of what? And what specific 'everyday' problem are you referring to?
--
Terry Jan Reedy
--
https://mail.python.org/mailman/listinf
> Looks like another bad batch, time to change your dealer again.
??? Strange, when the debate hits bottom, accusations about doing
drugs come up. This is like the third reference (and I don't even
drink alcohol).
mark
--
https://mail.python.org/mailman/listinfo/python-list
On 06/01/2014 19:30, 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
>> 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
> The argument is that a very important, if small, subset a data manipulation
> become very painful in Py3. Not impossible, and not difficult, but painful
> because the mental model and the contortions needed to get things to work
> don't sync up anymore.
You are confused. Please see my reply to
On 01/06/2014 09:27 AM, Steven D'Aprano wrote:
Ethan Furman 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
Ned Batchelder wrote:
> You are still talking about whether Armin is right, and whether he
> writes well, about flaws in his statistics, etc. I'm talking about the
> fact that an organization (Python core development) has a product
> (Python 3) that is getting bad press. Popular and vocal custom
Gene Heskett wrote:
> And from my lurking here, its quite plain to me that 3.x python has a
> problem with everyday dealing with strings.
I've been using Python 3.x since Python 3.1 came out, and I haven't come
across any meaningful problems with the everyday dealing with strings.
Quite the oppos
Ethan Furman wrote:
> On 01/05/2014 06:37 PM, Dan Stromberg wrote:
>>
>> The argument seems to be "3.x doesn't work the way I'm accustomed to,
>> so I'm not going to use it, and I'm going to shout about it until
>> others agree with me."
>
> The argument is that a very important, if small, subset
On 06/01/2014 16:46, Gene Heskett wrote:
On Monday 06 January 2014 11:42:55 Mark Lawrence did opine:
On 06/01/2014 14:32, Gene Heskett wrote:
On Monday 06 January 2014 08:52:42 Ned Batchelder did opine:
[...]
You are still talking about whether Armin is right, and whether he
writes well, abo
On 06/01/2014 16:43, Steven D'Aprano wrote:
Ethan Furman wrote:
For me this is simply a major annoyance, but I
only have a handful of places where I have to deal with this. Dealing
with protocols where bytes is the norm and embedded ascii is prevalent --
well, I can easily imagine the nightmar
On Tue, Jan 7, 2014 at 3:43 AM, Steven D'Aprano
wrote:
>> For me this is simply a major annoyance, but I
>> only have a handful of places where I have to deal with this. Dealing
>> with protocols where bytes is the norm and embedded ascii is prevalent --
>> well, I can easily imagine the nightmar
On 01/06/2014 07:46 AM, Chris Angelico wrote:
None of this changes the fact that there are bytes used to
store/transmit stuff, and abstract concepts used to manipulate them.
Just like nobody expects to be able to write a dict to a file without
some form of encoding (pickle, JSON, whatever), you
Ethan Furman wrote:
> Using my own project [1] as a reference: good ol' dbf files -- character
> fields, numeric fields, logic fields, time fields, and of course the
> metadata that describes these fields and the dbf as a whole. The
> character fields I turn into unicode, no sweat. The metadata
On Monday 06 January 2014 11:42:55 Mark Lawrence did opine:
> On 06/01/2014 14:32, Gene Heskett wrote:
> > On Monday 06 January 2014 08:52:42 Ned Batchelder did opine:
> > [...]
> >
> >> You are still talking about whether Armin is right, and whether he
> >> writes well, about flaws in his statis
On Tue, Jan 7, 2014 at 3:29 AM, Antoine Pitrou wrote:
> People don't use? According to available figures, there are more downloads of
> Python 3 than downloads of Python 2 (Windows installers, mostly):
> http://www.python.org/webstats/
>
Unfortunately, that has a massive inherent bias, because th
On Tue, Jan 7, 2014 at 2:53 AM, Grant Edwards wrote:
> Yea, I think laying out a book with something like MS Word or
> LibreOffice is nuts. Depending on her formatting needs, a
> lighter-weight mark-up language (something like asciidoc) might suite:
>
> http://asciidoc.org/
> http://en.wikip
On Tue, Jan 7, 2014 at 3:24 AM, Steven D'Aprano
wrote:
> If you don't want to use the codec, you can do it by hand:
>
> def rot13(astring):
> result = []
> for c in astring:
> i = ord(c)
> if ord('a') <= i <= ord('m') or ord('A') <= i <= ord('M'):
> i += 13
>
Ned Batchelder nedbatchelder.com> writes:
>
> You can look through his problems and decide that he's "wrong," or that
> he's "ranting," but that doesn't change the fact that Python 3 is
> encountering friction. What happens when a significant fraction of your
> customers are "wrong"?
Well, y
Roy Smith wrote:
> In article ,
> Chris Angelico wrote:
>
>> It can't be both things. It's either bytes or it's text.
>
> I've never used Python 3, so forgive me if these are naive questions.
> Let's say you had an input stream which contained the following hex
> values:
>
> $ hexdump data
>
On 2014-01-06, Chris Angelico wrote:
>> Right. I think shifting people to LibreOffice is an excellent and
>> realistic step toward imcreasing people's software and data freedom.
>
> Yeah. Which is why I do it. But the other night, my mum was trying to
> lay out her book in LO, and was having some
On Tue, Jan 7, 2014 at 2:10 AM, Ethan Furman wrote:
> On 01/05/2014 06:55 PM, Chris Angelico wrote:
>>
>>
>> It can't be both things. It's either bytes or it's text.
>
>
> Of course it can be:
>
> 000: 0372 0106 6100 1d00 .r..a...
> 010: 000
On 01/05/2014 06:37 PM, Dan Stromberg wrote:
The argument seems to be "3.x doesn't work the way I'm accustomed to,
so I'm not going to use it, and I'm going to shout about it until
others agree with me."
The argument is that a very important, if small, subset a data manipulation become very pa
On 06/01/2014 14:32, Gene Heskett wrote:
On Monday 06 January 2014 08:52:42 Ned Batchelder did opine:
[...]
You are still talking about whether Armin is right, and whether he
writes well, about flaws in his statistics, etc. I'm talking about the
fact that an organization (Python core developmen
On Monday 06 January 2014 08:52:42 Ned Batchelder did opine:
[...]
> You are still talking about whether Armin is right, and whether he
> writes well, about flaws in his statistics, etc. I'm talking about the
> fact that an organization (Python core development) has a product
> (Python 3) that is
On 06/01/2014 12:39, Ned Batchelder wrote:
I'm not talking about the technical details of bytes and Unicode. I'm
talking about making customers happy.
Simply scrap PEP 404 and the currently unhappy customers will be happy
as they'll be free to do all the work they want on Python 2.8, as my
On 1/5/14 11:26 PM, Terry Reedy wrote:
On 1/5/2014 8:16 PM, Ned Batchelder wrote:
OK, let's see what we got from three core developers on this list:
To me, the following is a partly unfair summary.
I apologize, I'm sure there were details I skipped in my short summary.
- Antoine dismiss
On 2014-01-06 15:51, Chris Angelico wrote:
> >>> data = b"\x43\x6c\x67\x75\x62\x61" # is there an easier way to
> >>> turn a hex dump into a bytes literal?
Depends on how you source them:
# space separated:
>>> s1 = "43 6c 67 75 62 61"
>>> ''.join(chr(int(pair, 16)) for pair in s1.split())
'Clgu
On 01/05/2014 06:23 PM, Ethan Furman wrote:
Using my own project [1] as a reference
[1] https://pypi.python.org/pypi/dbf
--
https://mail.python.org/mailman/listinfo/python-list
On Mon, Jan 6, 2014 at 3:49 PM, Roy Smith wrote:
> Thanks. But, I see I didn't formulate my problem statement well. I was
> (naively) assuming there wouldn't be a built-in codec for rot-13. Let's
> assume there isn't; I was trying to find a case where you had to treat
> the data as integers in
On Mon, Jan 6, 2014 at 3:24 PM, Roy Smith wrote:
> I've never used Python 3, so forgive me if these are naive questions.
> Let's say you had an input stream which contained the following hex
> values:
>
> $ hexdump data
> 000 d7 a8 a3 88 96 95
>
> That's EBCDIC for "Python". What would I writ
In article ,
Tim Chase wrote:
> On 2014-01-05 23:24, Roy Smith wrote:
> > $ hexdump data
> > 000 d7 a8 a3 88 96 95
> >
> > That's EBCDIC for "Python". What would I write in Python 3 to read
> > that file and print it back out as utf-8 encoded Unicode?
> >
> > Or, how about a slightly diff
On 2014-01-05 23:24, Roy Smith wrote:
> $ hexdump data
> 000 d7 a8 a3 88 96 95
>
> That's EBCDIC for "Python". What would I write in Python 3 to read
> that file and print it back out as utf-8 encoded Unicode?
>
> Or, how about a slightly different example:
>
> $ hexdump data
> 000 43 6
On 1/5/2014 8:16 PM, Ned Batchelder wrote:
OK, let's see what we got from three core developers on this list:
To me, the following is a partly unfair summary.
- Antoine dismissed the post as "a rant".
He called it a rant while acknowledging that there is a unsolved issue
with transforms.
In article ,
Chris Angelico wrote:
> It can't be both things. It's either bytes or it's text.
I've never used Python 3, so forgive me if these are naive questions.
Let's say you had an input stream which contained the following hex
values:
$ hexdump data
000 d7 a8 a3 88 96 95
That's E
In article ,
Mark Janssen wrote:
> I honestly think Python3 will have to be regressed despite all the
> [obscenity elided] about how "everyone's moving to Python 3 now".
This forum has seen a lot honest disagreement about issues, sometimes
hotly debated. That's OK. Sometimes the discussion
On Mon, Jan 6, 2014 at 1:23 PM, Ethan Furman wrote:
> The metadata fields are simple ascii, and in Py2 something like `if
> header[FIELD_TYPE] == 'C'` did the job just fine. In Py3 that compares an
> int (67) to the unicode letter 'C' and returns False. For me this is simply
> a major annoyance,
On 01/05/2014 05:48 PM, Chris Angelico wrote:
On Mon, Jan 6, 2014 at 12:16 PM, Ned Batchelder wrote:
So now we have two revered developers vocally having trouble with Python 3.
You can dismiss their concerns as niche because it's only network
programming, but that would be a mistake.
IMO, net
On Sun, Jan 5, 2014 at 4:46 PM, Ethan Furman wrote:
> While I don't agree with his assessment of Python 3 in total, I definitely
> feel his pain with regards to bytestrings in Py3 -- because they don't
> exist. 'bytes' /looks/ like a bytestring, but really it's just a bunch of
> integers:
>
> -->
>> Most of the complaints about Py3 are "it's harder to get something
>> started (or port from Py2)". My answer is that it's easier to get
>> something finished.
>
> I like all of this logic, it makes sense to me. But Armin and Kenneth have
> more experience than I do actually writing networking s
On 1/5/14 8:48 PM, Chris Angelico wrote:
On Mon, Jan 6, 2014 at 12:16 PM, Ned Batchelder wrote:
So now we have two revered developers vocally having trouble with Python 3.
You can dismiss their concerns as niche because it's only network
programming, but that would be a mistake.
IMO, network
In article ,
Chris Angelico wrote:
> One time I implemented Oauth manually rather than using a library
Me too. You have my sympathy. What a mess.
--
https://mail.python.org/mailman/listinfo/python-list
On Mon, Jan 6, 2014 at 12:16 PM, Ned Batchelder wrote:
> So now we have two revered developers vocally having trouble with Python 3.
> You can dismiss their concerns as niche because it's only network
> programming, but that would be a mistake.
IMO, network programming (at least on the internet)
On 01/05/2014 05:14 AM, Mark Lawrence wrote:
Please don't shoot the messenger :)
While I don't agree with his assessment of Python 3 in total, I definitely feel his pain with regards to bytestrings in
Py3 -- because they don't exist. 'bytes' /looks/ like a bytestring, but really it's just a
1 - 100 of 119 matches
Mail list logo
