Re: Bugs in CPython 3.1.1 [wave.py]

2010-01-13 Thread Alf P. Steinbach
* Alf P. Steinbach: * Steve Holden: Alf P. Steinbach wrote: * Steven D'Aprano: Nobody is trying to understate the complexity of writing a large application that supports both 2.6 and 3.x, or of taking an existing library written for 2.5 and upgrading it to support 3.1. But the magnitude of the

Re: Bugs in CPython 3.1.1 [wave.py]

2010-01-13 Thread Alf P. Steinbach
* Steve Holden: Alf P. Steinbach wrote: * Steven D'Aprano: Nobody is trying to understate the complexity of writing a large application that supports both 2.6 and 3.x, or of taking an existing library written for 2.5 and upgrading it to support 3.1. But the magnitude of these tasks is no greate

Re: Bugs in CPython 3.1.1 [wave.py]

2010-01-13 Thread Terry Reedy
On 1/13/2010 3:44 AM, Steven D'Aprano wrote: On Wed, 13 Jan 2010 09:34:55 +0100, Alf P. Steinbach wrote: Would it be better to say that it's "hard" or "very hard" or "impractical for the novice"? Yes, but ... I don't even know why you feel the need to discuss 2.x in a book that's about 3

Re: Bugs in CPython 3.1.1 [wave.py]

2010-01-13 Thread Steve Holden
Alf P. Steinbach wrote: > * Steven D'Aprano: >> >> Nobody is trying to understate the complexity of writing a large >> application that supports both 2.6 and 3.x, or of taking an existing >> library written for 2.5 and upgrading it to support 3.1. But the >> magnitude of these tasks is no greater (

Re: Bugs in CPython 3.1.1 [wave.py]

2010-01-13 Thread Stefan Behnel
Terry Reedy, 13.01.2010 04:40: What might be changed more easily is to accept a report but impound it until the confirmation reply. Being able to spit out what one has to say while it is still fresh in the mind should make the email wait more tolerable. What do you think? Sounds like a very g

Re: Bugs in CPython 3.1.1 [wave.py]

2010-01-13 Thread Lie Ryan
Alf P. Steinbach wrote: > * Stefan Behnel: >> Alf P. Steinbach, 13.01.2010 06:39: >>> * Steven D'Aprano: On Tue, 12 Jan 2010 23:42:28 +0100, Alf P. Steinbach wrote: > It is hopeless, especially for a newbie, to create correct Python > 2.x+3.x compatible code, except totally trivial stu

Re: Bugs in CPython 3.1.1 [wave.py]

2010-01-13 Thread Alf P. Steinbach
* Steven D'Aprano: On Wed, 13 Jan 2010 06:55:27 +0100, Alf P. Steinbach wrote: * Steven D'Aprano: On Tue, 12 Jan 2010 23:47:31 +0100, Alf P. Steinbach wrote: PS: Next time it would have helped to include a URL to the issue. http://bugs.python.org/issue7681 FYI there is already some

Re: Bugs in CPython 3.1.1 [wave.py]

2010-01-13 Thread Steven D'Aprano
On Wed, 13 Jan 2010 09:34:55 +0100, Alf P. Steinbach wrote: > * Steven D'Aprano: >> >> Nobody is trying to understate the complexity of writing a large >> application that supports both 2.6 and 3.x, or of taking an existing >> library written for 2.5 and upgrading it to support 3.1. But the >> ma

Re: Bugs in CPython 3.1.1 [wave.py]

2010-01-13 Thread Alf P. Steinbach
* Steven D'Aprano: Nobody is trying to understate the complexity of writing a large application that supports both 2.6 and 3.x, or of taking an existing library written for 2.5 and upgrading it to support 3.1. But the magnitude of these tasks is no greater (and potentially smaller) than supp

Re: Bugs in CPython 3.1.1 [wave.py]

2010-01-13 Thread Steven D'Aprano
On Wed, 13 Jan 2010 06:55:27 +0100, Alf P. Steinbach wrote: > * Steven D'Aprano: >> On Tue, 12 Jan 2010 23:47:31 +0100, Alf P. Steinbach wrote: >> PS: Next time it would have helped to include a URL to the issue. http://bugs.python.org/issue7681 FYI there is alrea

Re: Bugs in CPython 3.1.1 [wave.py]

2010-01-13 Thread Stefan Behnel
Alf P. Steinbach, 13.01.2010 09:00: I'm sorry but as Steven did in the quoted material above you're trying to make people believe something that you know is false: I haven't blamed the world, nor described the bug as terrible or a doom, and you know that. I admit that I took the freedom to re

Re: Bugs in CPython 3.1.1 [wave.py]

2010-01-13 Thread Alf P. Steinbach
* Stefan Behnel: Alf P. Steinbach, 13.01.2010 06:55: * Steven D'Aprano: I think you need to chill out and stop treating a simple bug report as a personal slight on you. I'm sorry but you're again trying to make people believe something that you know is false, which is commonly called lying:

Re: Bugs in CPython 3.1.1 [wave.py]

2010-01-12 Thread Alf P. Steinbach
* Stefan Behnel: Alf P. Steinbach, 13.01.2010 06:39: * Steven D'Aprano: On Tue, 12 Jan 2010 23:42:28 +0100, Alf P. Steinbach wrote: It is hopeless, especially for a newbie, to create correct Python 2.x+3.x compatible code, except totally trivial stuff of course. So you allege, but André poin

Re: Bugs in CPython 3.1.1 [wave.py]

2010-01-12 Thread Steven D'Aprano
On Wed, 13 Jan 2010 06:39:53 +0100, Alf P. Steinbach wrote: > Then be a little critical and think about, what problems could it be > that, in spite of that to you apparent simplicity, hinders the > widespread adoption of Python 3.x? (1) Most Linux distributions still come standard with Python 2.

Re: Bugs in CPython 3.1.1 [wave.py]

2010-01-12 Thread Stefan Behnel
Alf P. Steinbach, 13.01.2010 06:55: * Steven D'Aprano: I think you need to chill out and stop treating a simple bug report as a personal slight on you. I'm sorry but you're again trying to make people believe something that you know is false, which is commonly called lying: it is not the cas

Re: Bugs in CPython 3.1.1 [wave.py]

2010-01-12 Thread Stefan Behnel
Alf P. Steinbach, 13.01.2010 06:39: * Steven D'Aprano: On Tue, 12 Jan 2010 23:42:28 +0100, Alf P. Steinbach wrote: It is hopeless, especially for a newbie, to create correct Python 2.x+3.x compatible code, except totally trivial stuff of course. So you allege, but André points out that there

Re: Bugs in CPython 3.1.1 [wave.py]

2010-01-12 Thread Alf P. Steinbach
* Terry Reedy: On 1/12/2010 6:31 PM, Alf P. Steinbach wrote: Perhaps change to CAPTCHA instead of mail confirmation. I disagree. The point of mail confirmation is not just to assure that a human is registering, but that we have a valid email for responses to be sent to. Many issues are file

Re: Bugs in CPython 3.1.1 [wave.py]

2010-01-12 Thread Alf P. Steinbach
* Steven D'Aprano: On Tue, 12 Jan 2010 23:47:31 +0100, Alf P. Steinbach wrote: PS: Next time it would have helped to include a URL to the issue. http://bugs.python.org/issue7681 FYI there is already some feedback in the tracker. Yeah, someone who had the bright idea that maybe there

Re: Bugs in CPython 3.1.1 [wave.py]

2010-01-12 Thread Alf P. Steinbach
* Steven D'Aprano: On Tue, 12 Jan 2010 23:42:28 +0100, Alf P. Steinbach wrote: * André: On Jan 12, 9:33 am, "Alf P. Steinbach" wrote: Well, this is for my Python (actually, beginning programmer) writings, at http://tinyurl.com/programmingbookP3 Thanks for writing this book. I just h

Re: Bugs in CPython 3.1.1 [wave.py]

2010-01-12 Thread Steven D'Aprano
On Tue, 12 Jan 2010 23:42:28 +0100, Alf P. Steinbach wrote: > * André: >> On Jan 12, 9:33 am, "Alf P. Steinbach" wrote: >> >>> Well, this is for my Python (actually, beginning programmer) writings, >>> at >>> >>>http://tinyurl.com/programmingbookP3 >>> >>> >> Thanks for writing this book. I

Re: Bugs in CPython 3.1.1 [wave.py]

2010-01-12 Thread Steven D'Aprano
On Tue, 12 Jan 2010 23:47:31 +0100, Alf P. Steinbach wrote: >> PS: Next time it would have helped to include a URL to the issue. >> >> http://bugs.python.org/issue7681 >> >> FYI there is already some feedback in the tracker. > > Yeah, someone who had the bright idea that maybe there isn

Re: Bugs in CPython 3.1.1 [wave.py]

2010-01-12 Thread Terry Reedy
On 1/12/2010 6:31 PM, Alf P. Steinbach wrote: Perhaps change to CAPTCHA instead of mail confirmation. I disagree. The point of mail confirmation is not just to assure that a human is registering, but that we have a valid email for responses to be sent to. Many issues are filed with inadaquat

Re: Bugs in CPython 3.1.1 [wave.py]

2010-01-12 Thread Alex Clifford
2010/1/13 Alf P. Steinbach > > Received: from mr1.start.no (unknown [195.159.73.42]) >by mail6.start.no (Postfix) with ESMTP id 54EFE1534F8 >for ; Tue, 12 Jan 2010 12:56:05 +0100 (CET) > Received: from psf.upfronthosting.co.za (bugs.python.org [88.198.142.26]) >by mr1.star

Re: Bugs in CPython 3.1.1 [wave.py]

2010-01-12 Thread Steve Holden
Alf P. Steinbach wrote: > * Steve Holden: >> Alf P. Steinbach wrote: >> >> If you have any suggestions for improving things (and the same goes for >> any other readers) I will be happy to listen to them. I do agree that >> the bug tracker is a rather high hurdle for people to have to jump over >> j

Re: Bugs in CPython 3.1.1 [wave.py]

2010-01-12 Thread Alf P. Steinbach
* Steve Holden: Alf P. Steinbach wrote: * Steve Holden: [...] FYI there is already some feedback in the tracker. Yeah, someone who had the bright idea that maybe there isn't a bug, thinking instead that maybe a "wrong" name in *a comment* might be the culprit -- of all things! He was p

Re: Bugs in CPython 3.1.1 [wave.py]

2010-01-12 Thread Steve Holden
Alf P. Steinbach wrote: > * Steve Holden: [...] >> FYI there is already some feedback in the tracker. > > Yeah, someone who had the bright idea that maybe there isn't a bug, > thinking instead that maybe a "wrong" name in *a comment* might be the > culprit -- of all things! > > He was proba

Re: Bugs in CPython 3.1.1 [wave.py]

2010-01-12 Thread Alf P. Steinbach
* Steve Holden: Alf P. Steinbach wrote: If you have any suggestions for improving things (and the same goes for any other readers) I will be happy to listen to them. I do agree that the bug tracker is a rather high hurdle for people to have to jump over just to offer feedback on software faults,

Re: Bugs in CPython 3.1.1 [wave.py]

2010-01-12 Thread Alf P. Steinbach
* Steve Holden: Alf P. Steinbach wrote: * Stefan Behnel: Alf P. Steinbach, 12.01.2010 12:51: Well how f*g darn patient do they expect me to be? I've decided: I'm not. Oh sh**, just as I typed the period above the mail finally arrived. It's been, let's see, about 20+ minutes! And still

Re: Bugs in CPython 3.1.1 [wave.py]

2010-01-12 Thread Alf P. Steinbach
* André: On Jan 12, 9:33 am, "Alf P. Steinbach" wrote: Well, this is for my Python (actually, beginning programmer) writings, at http://tinyurl.com/programmingbookP3 Thanks for writing this book. I just had a quick look at the beginning of it where you write: === As of this writing two

Re: Bugs in CPython 3.1.1 [wave.py]

2010-01-12 Thread Malte Dik
I totally second Alf in this regard. There were times you could report a bug by mail (to Debian e.g.) and it worked perfectly (for me, the reporter). Once I went into the maze of bug reporting software and I almost didn't find back to the problem I tried to fix while stumbling upon the to-be-re

Re: Bugs in CPython 3.1.1 [wave.py]

2010-01-12 Thread Steve Holden
Alf P. Steinbach wrote: > * Stefan Behnel: >> Alf P. Steinbach, 12.01.2010 12:51: >>> Well how f*g darn patient do they expect me to be? >>> >>> I've decided: I'm not. >>> >>> Oh sh**, just as I typed the period above the mail finally arrived. >>> It's been, let's see, about 20+ minutes! >>> >

Re: Bugs in CPython 3.1.1 [wave.py]

2010-01-12 Thread Steve Holden
Alf P. Steinbach wrote: > * Alf P. Steinbach: >> * Steve Holden: >>> Alf P. Steinbach wrote: >>> [...] PS: It would be nice if someone(TM) could describe here in detail how to properly report errors like this. Of course I'm not going to do it if it involves establishing Yet

Re: Bugs in CPython 3.1.1 [wave.py]

2010-01-12 Thread André
On Jan 12, 9:33 am, "Alf P. Steinbach" wrote: > > Well, this is for my Python (actually, beginning programmer) writings, at > >    http://tinyurl.com/programmingbookP3 > Thanks for writing this book. I just had a quick look at the beginning of it where you write: === As of this writing two main

Re: Bugs in CPython 3.1.1 [wave.py]

2010-01-12 Thread Daniel Fetchinson
PS: It would be nice if someone(TM) could describe here in detail how to properly report errors like this. Of course I'm not going to do it if it involves establishing Yet Another Account somewhere. But hopefully it doesn't? >>> That's not very public-spirited, is it? Pytho

Re: Bugs in CPython 3.1.1 [wave.py]

2010-01-12 Thread Alf P. Steinbach
* Stefan Behnel: Alf P. Steinbach, 12.01.2010 13:10: * Stefan Behnel: Maybe you should just stop using the module. Writing the code yourself is certainly going to be faster than reporting that bug, don't you think? It's part of the standard Python distribution. Don't you think bugs in the s

Re: Bugs in CPython 3.1.1 [wave.py]

2010-01-12 Thread Steven D'Aprano
On Tue, 12 Jan 2010 12:51:06 +0100, Alf P. Steinbach wrote: > Oh sh**, just as I typed the period above the mail finally arrived. It's > been, let's see, about 20+ minutes! Aren't you a little old to be suffering from the every decreasing attention spans of the MTV generation? Email is not guar

Re: Bugs in CPython 3.1.1 [wave.py]

2010-01-12 Thread Stefan Behnel
Alf P. Steinbach, 12.01.2010 13:10: * Stefan Behnel: Maybe you should just stop using the module. Writing the code yourself is certainly going to be faster than reporting that bug, don't you think? It's part of the standard Python distribution. Don't you think bugs in the standard library sho

Re: Bugs in CPython 3.1.1 [wave.py]

2010-01-12 Thread Alf P. Steinbach
* Stefan Behnel: Alf P. Steinbach, 12.01.2010 12:51: Well how f*g darn patient do they expect me to be? I've decided: I'm not. Oh sh**, just as I typed the period above the mail finally arrived. It's been, let's see, about 20+ minutes! And still some miles to go. Somebody should say T

Re: Bugs in CPython 3.1.1 [wave.py]

2010-01-12 Thread Stefan Behnel
Alf P. Steinbach, 12.01.2010 12:51: Well how f*g darn patient do they expect me to be? I've decided: I'm not. Oh sh**, just as I typed the period above the mail finally arrived. It's been, let's see, about 20+ minutes! And still some miles to go. Somebody should say THANK YOU for all t

Re: Bugs in CPython 3.1.1 [wave.py]

2010-01-12 Thread Alf P. Steinbach
* Alf P. Steinbach: * Steve Holden: Alf P. Steinbach wrote: [...] PS: It would be nice if someone(TM) could describe here in detail how to properly report errors like this. Of course I'm not going to do it if it involves establishing Yet Another Account somewhere. But hopefully it doesn't? Th

Re: Bugs in CPython 3.1.1 [wave.py]

2010-01-12 Thread Alf P. Steinbach
* Steve Holden: Alf P. Steinbach wrote: [...] PS: It would be nice if someone(TM) could describe here in detail how to properly report errors like this. Of course I'm not going to do it if it involves establishing Yet Another Account somewhere. But hopefully it doesn't? That's not very public-

Re: Bugs in CPython 3.1.1 [wave.py]

2010-01-12 Thread Steve Holden
Alf P. Steinbach wrote: [...] > PS: It would be nice if someone(TM) could describe here in detail how to > properly report errors like this. Of course I'm not going to do it if it > involves establishing Yet Another Account somewhere. But hopefully it > doesn't? > That's not very public-spirited,

Re: Bugs in CPython 3.1.1 [wave.py]

2010-01-12 Thread Chris Withers
Alf P. Steinbach wrote: PS: It would be nice if someone(TM) could describe here in detail how to properly report errors like this. http://tinyurl.com/yemcdy7 Of course I'm not going to do it if it involves establishing Yet Another Account somewhere. Of course that means no-one else will

Re: Bugs in CPython 3.1.1 [wave.py]

2010-01-12 Thread Terry Reedy
On 1/12/2010 3:25 AM, Alf P. Steinbach wrote: Argh! This was really annoying! Much time wasted (one naturally thinks that silly error must be one's own). But, anyway: Lines: 244 nitems = (chunk.chunksize - chunk.size_read) / self._sampwidth 464 self._nframes = initlength / (self._nchannels * s

Bugs in CPython 3.1.1 [wave.py]

2010-01-12 Thread Alf P. Steinbach
Argh! This was really annoying! Much time wasted (one naturally thinks that silly error must be one's own). But, anyway: Lines: 244 nitems = (chunk.chunksize - chunk.size_read) / self._sampwidth 464 self._nframes = initlength / (self._nchannels * self._sampwidth) Need to use Python 3.x