Re: [Python-Dev] Five reviews to get yours reviewed?

2014-03-02 Thread Terry Reedy
On 3/2/2014 1:51 AM, Chris Angelico wrote: On Sun, Mar 2, 2014 at 4:07 PM, Terry Reedy tjre...@udel.edu wrote: On 3/1/2014 7:11 PM, Chris Angelico wrote: I have a couple of patches outstanding, notably issue 20249 [2], which is a small change, has a patch, and has no activity or nosying since

Re: [Python-Dev] Five reviews to get yours reviewed?

2014-03-02 Thread Chris Angelico
On Sun, Mar 2, 2014 at 7:48 PM, Terry Reedy tjre...@udel.edu wrote: On 3/2/2014 1:51 AM, Chris Angelico wrote: On Sun, Mar 2, 2014 at 4:07 PM, Terry Reedy tjre...@udel.edu wrote: On 3/1/2014 7:11 PM, Chris Angelico wrote: I have a couple of patches outstanding, notably issue 20249 [2],

Re: [Python-Dev] Wave module support for floating point data

2014-03-02 Thread Xavier de Gaye
On 03/02/2014 12:04 AM, Terry Reedy wrote: On 3/1/2014 3:25 PM, Antoine Pitrou wrote: On Sat, 01 Mar 2014 15:08:00 -0500 Terry Reedy wrote: On 3/1/2014 2:57 PM, Sebastian Kraft wrote: Hi everybody, more than a year ago I have submitted a patch to enhance the Wave module with read/write

Re: [Python-Dev] Wave module support for floating point data

2014-03-02 Thread Tim Golden
On 02/03/2014 10:25, Xavier de Gaye wrote: The core-mentorship current archive is only available to the list members as stated at the core-mentorship web site at http://pythonmentors.com/. Curious to know why. The thinking behind c-m is to lower the entry bar for contribution. To that end,

Re: [Python-Dev] Wave module support for floating point data

2014-03-02 Thread Sebastian Kraft
Am 01.03.2014 21:25, schrieb Antoine Pitrou: On Sat, 01 Mar 2014 15:08:00 -0500 Terry Reedy tjre...@udel.edu wrote: On 3/1/2014 2:57 PM, Sebastian Kraft wrote: Hi everybody, more than a year ago I have submitted a patch to enhance the Wave module with read/write support for floating point

Re: [Python-Dev] Wave module support for floating point data

2014-03-02 Thread Antoine Pitrou
On Sat, 01 Mar 2014 18:04:09 -0500 Terry Reedy tjre...@udel.edu wrote: Please subscribe to core-mentorship list and post your question there. I don't understand this response. You seem to be assuming that Sebastian is asking for guidance, I am reading what he posted, which ended with

Re: [Python-Dev] Removing doc from pythonhosted.org

2014-03-02 Thread Brett Cannon
Best place for PyPI-related things is distutils-...@python.org. But for bug reports related to PyPI, file them at https://bitbucket.org/pypa/pypi/issues(it's actually linked off of PyPI). On Sat, Mar 1, 2014 at 1:30 PM, Giampaolo Rodola' g.rod...@gmail.comwrote: I'm not sure whether this is

[Python-Dev] unicode_string future, str - basestring, fix or feature

2014-03-02 Thread Terry Reedy
Suppose a 2.7 standard library function is documented as taking a 'string' argument, such as these examples from the turtle module. pencolor(colorstring) Set pencolor to colorstring, which is a Tk color specification string, such as red, yellow, or #33cc8c. turtle.shape(name=None)

Re: [Python-Dev] unicode_string future, str - basestring, fix or feature

2014-03-02 Thread Antoine Pitrou
On Sun, 02 Mar 2014 15:01:01 -0500 Terry Reedy tjre...@udel.edu wrote: Suppose a 2.7 standard library function is documented as taking a 'string' argument, such as these examples from the turtle module. pencolor(colorstring) Set pencolor to colorstring, which is a Tk color

Re: [Python-Dev] unicode_string future, str - basestring, fix or feature

2014-03-02 Thread Guido van Rossum
It looks to me like a defect in the library (*), and you are making a reasonable argument that we should fix it in 2.7 to help people be more prepared for the transition to Python 3. (*) As Antoine points out, pretty much the only time where it's not a good idea to switch from str to basestring

Re: [Python-Dev] Wave module support for floating point data

2014-03-02 Thread Serhiy Storchaka
01.03.14 21:57, Sebastian Kraft написав(ла): more than a year ago I have submitted a patch to enhance the Wave module with read/write support for floating point data. http://bugs.python.org/issue16525 Up till now this patch has not been applied nor did I get feedback if anything needs to be

Re: [Python-Dev] unicode_string future, str - basestring, fix or feature

2014-03-02 Thread Terry Reedy
On 3/2/2014 3:12 PM, Guido van Rossum wrote: It looks to me like a defect in the library (*), and you are making a reasonable argument that we should fix it in 2.7 to help people be more prepared for the transition to Python 3. (*) As Antoine points out, pretty much the only time where it's not

Re: [Python-Dev] unicode_string future, str - basestring, fix or feature

2014-03-02 Thread Serhiy Storchaka
02.03.14 22:01, Terry Reedy написав(ла): Is this a programmer error for passing unicode instead of string, or a library error for not accepting unicode? Is changing 'isinstance(x, str)' in the library (with whatever other changes are needed) a bugfix to be pushed or a prohibited API expansion?

Re: [Python-Dev] unicode_string future, str - basestring, fix or feature

2014-03-02 Thread Berker Peksağ
On Sun, Mar 2, 2014 at 11:23 PM, Serhiy Storchaka storch...@gmail.com wrote: Patches which add support for unicode strings were accepted for one issues (e.g. http://bugs.python.org/issue19099) and rejected for other issues (e.g. http://bugs.python.org/issue20014 and

Re: [Python-Dev] unicode_string future, str - basestring, fix or feature

2014-03-02 Thread Terry Reedy
On 3/2/2014 4:23 PM, Serhiy Storchaka wrote: 02.03.14 22:01, Terry Reedy написав(ла): Is this a programmer error for passing unicode instead of string, or a library error for not accepting unicode? Is changing 'isinstance(x, str)' in the library (with whatever other changes are needed) a bugfix

Re: [Python-Dev] unicode_string future, str - basestring, fix or feature

2014-03-02 Thread Nick Coghlan
On 3 March 2014 10:02, Terry Reedy tjre...@udel.edu wrote: On 3/2/2014 4:23 PM, Serhiy Storchaka wrote: 02.03.14 22:01, Terry Reedy написав(ла): Is this a programmer error for passing unicode instead of string, or a library error for not accepting unicode? Is changing 'isinstance(x, str)'

Re: [Python-Dev] unicode_string future, str - basestring, fix or feature

2014-03-02 Thread Stephen J. Turnbull
Terry Reedy writes: On 3/2/2014 4:23 PM, Serhiy Storchaka wrote: Patches which add support for unicode strings were accepted for one issues (e.g. http://bugs.python.org/issue19099) and rejected for other issues (e.g. http://bugs.python.org/issue20014 and

Re: [Python-Dev] unicode_string future, str - basestring, fix or feature

2014-03-02 Thread Guido van Rossum
AFACT, in that message Victor was only talking about allowing Unicode filenames. Making everything polymorphic is clearly pulling on the thread that will unravel the entire sweater. But... The start of this thread was about changing a few occurrences of isinstance(..., str) to use basestring,

Re: [Python-Dev] unicode_string future, str - basestring, fix or feature

2014-03-02 Thread Serhiy Storchaka
03.03.14 02:02, Terry Reedy написав(ла): On 3/2/2014 4:23 PM, Serhiy Storchaka wrote: 02.03.14 22:01, Terry Reedy написав(ла): Is this a programmer error for passing unicode instead of string, or a library error for not accepting unicode? Is changing 'isinstance(x, str)' in the library (with