Guido van Rossum writes:
Given that the claim Python 2 doesn't support Unicode filenames
is factually incorrect (in Python 2.7, most filesystem calls in
fact do support Unicode, at least on some platforms),
I don't understand what support Unicode means. Just that
with open(u\u4e00,
On Tue, Mar 4, 2014 at 5:23 AM, Stephen J. Turnbull step...@xemacs.orgwrote:
Guido van Rossum writes:
Given that the claim Python 2 doesn't support Unicode filenames
is factually incorrect (in Python 2.7, most filesystem calls in
fact do support Unicode, at least on some platforms),
On Sun, Mar 2, 2014 at 6:44 PM, Guido van Rossum gu...@python.org wrote:
AFACT, in that message Victor was only talking about allowing Unicode
filenames.
...
Finally, in most places Python 2.7 *does* handle Unicode filenames just
fine.
I'm a bit confused. In this example:
On Mon, Mar 3, 2014 at 8:37 AM, Chris Barker chris.bar...@noaa.gov wrote:
On Sun, Mar 2, 2014 at 6:44 PM, Guido van Rossum gu...@python.org wrote:
AFACT, in that message Victor was only talking about allowing Unicode
filenames.
...
Finally, in most places Python 2.7 *does* handle Unicode
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)
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
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
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
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?
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
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
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)'
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
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,
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
15 matches
Mail list logo
