Re: [Python-3000] Support for PEP 3131

2007-05-22 Thread Jim Jewett
On 5/22/07, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote: > That's why Java and C++ use \u, so you would write L\u00F6wis > as an identifier. ... > I think you are really arguing for \u escapes in identifiers here. Yes, that is effectively what I was suggesting. > *This* is truly unambiguous. I c

Re: [Python-3000] Support for PEP 3131

2007-05-22 Thread Jim Jewett
On 5/22/07, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote: [Referring to my alternate alternative proposal -- user-controlled transliteration, rather than unicode escapes in identifiers] > >> Then I don't understand your above proposal. I thought you were > >> proposing to replace all non-ASCII cha

Re: [Python-3000] [Python-Dev] Introduction and request for commit access to the sandbox.

2007-05-22 Thread Alexandre Vassalotti
On 5/21/07, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote: > > With that said, I would to request svn access to the sandbox for my > > work. I will use this access only for modifying stuff in the directory > > I will be assigned to. I would like to use the username "avassalotti" > > and the attached

Re: [Python-3000] PEP 3131 accepted

2007-05-22 Thread Ka-Ping Yee
On Thu, 17 May 2007, Guido van Rossum wrote: > I have accepted PEP 3131. I'm surprised that this happened so quickly. I oppose this proposal quite strongly. Currently Python has the property that the character set is a fully known quantity. There currently exists a choice of keyboard, a choice

Re: [Python-3000] PEP 3131 accepted

2007-05-22 Thread Leonardo Santagada
Em 22/05/2007, às 19:08, Ka-Ping Yee escreveu: > > Currently Python has the property that the character set is a fully > known quantity. There currently exists a choice of keyboard, a choice > of editor, and a set of literacy skills that is sufficient for any > Python code in the world. > No, an

Re: [Python-3000] PEP 3131 accepted

2007-05-22 Thread Ka-Ping Yee
On Tue, 22 May 2007, Leonardo Santagada wrote: > > Today, if a non-English speaker asks you how to learn Python, you can > > answer that question. You can explain Python's syntax and semantics, > > and tell them they need to know the 26 letters of the Roman alphabet. > Have you ever explained that

[Python-3000] please keep open() as a builtin, and general concerns about Py3k complexity

2007-05-22 Thread Steve Howell
Hi, this is my first post to the list. My name is Steve Howell, and I currently work on a system, largely written in Python, that processes a billion transactions per year. On the opposite side of the sprectrum, I've also had experience in classrooms using Python as a teaching tool. In the syste

Re: [Python-3000] PEP 3131 accepted

2007-05-22 Thread Guido van Rossum
On 5/22/07, Ka-Ping Yee <[EMAIL PROTECTED]> wrote: > Python fits your brain. Let's keep it that way. I'm sorry, Ping, but you sound just like I was feeling about the PEP at the start (and many others were too). You missed a bunch of enlightening posts from people with quite a different perspectiv

Re: [Python-3000] [Python-Dev] Introduction and request for commit access to the sandbox.

2007-05-22 Thread Neal Norwitz
On 5/22/07, Alexandre Vassalotti <[EMAIL PROTECTED]> wrote: > > As you see, cStringIO's code also needs a good cleanup to make it, > at least, conforms to PEP-7. Alexandre, It would be great if you could break up unrelated changes into separate patches. Some of these can go in sooner rather than

Re: [Python-3000] Support for PEP 3131

2007-05-22 Thread Stephen J. Turnbull
Jim Jewett writes: > On 5/22/07, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote: > > > That's why Java and C++ use \u, so you would write L\u00F6wis > > as an identifier. ... > > I think you are really arguing for \u escapes in identifiers here. > > Yes, that is effectively what I was sugges

Re: [Python-3000] please keep open() as a builtin, and general concerns about Py3k complexity

2007-05-22 Thread Neal Norwitz
On 5/22/07, Steve Howell <[EMAIL PROTECTED]> wrote: > > In the system I've worked on for the last three years, > we have at least 200 calls to the builtin open() > method. This number is meaningless by itself. 200 calls in how many lines of code? How many files total and how many files use open?

Re: [Python-3000] please keep open() as a builtin, and general concerns about Py3k complexity

2007-05-22 Thread Steve Howell
--- Neal Norwitz <[EMAIL PROTECTED]> wrote: > On 5/22/07, Steve Howell <[EMAIL PROTECTED]> > wrote: > > > > In the system I've worked on for the last three > years, > > we have at least 200 calls to the builtin open() > > method. > > This number is meaningless by itself. 200 calls in > how many

Re: [Python-3000] please keep open() as a builtin, and general concerns about Py3k complexity

2007-05-22 Thread Guillaume Proux
On 5/23/07, Steve Howell <[EMAIL PROTECTED]> wrote: > 17.7% of the files I searched have calls to open(). My understand is that the mythical "python 2.x -> 3.0" tool will automatically migrate your code by using the AST to find all references to "open" and when finding one, add the correct import

Re: [Python-3000] please keep open() as a builtin, and general concerns about Py3k complexity

2007-05-22 Thread Steve Howell
--- Guillaume Proux <[EMAIL PROTECTED]> wrote: > On 5/23/07, Steve Howell <[EMAIL PROTECTED]> > wrote: > > 17.7% of the files I searched have calls to > open(). > > My understand is that the mythical "python 2.x -> > 3.0" tool will > automatically migrate your code by using the AST to > find all

Re: [Python-3000] please keep open() as a builtin, and general concerns about Py3k complexity

2007-05-22 Thread Neal Norwitz
On 5/22/07, Guillaume Proux <[EMAIL PROTECTED]> wrote: > On 5/23/07, Steve Howell <[EMAIL PROTECTED]> wrote: > > 17.7% of the files I searched have calls to open(). > > My understand is that the mythical "python 2.x -> 3.0" tool will > automatically migrate your code by using the AST to find all >

Re: [Python-3000] please keep open() as a builtin, and general concerns about Py3k complexity

2007-05-22 Thread Neal Norwitz
On 5/22/07, Steve Howell <[EMAIL PROTECTED]> wrote: > > But since you mentioned conversion, our system is a > good example of a shop that will be running multiple > versions of Python side by side for many years. We'll > cut over new components to Py3k, and then we'll > gradually upgrade legacy co

Re: [Python-3000] please keep open() as a builtin, and general concerns about Py3k complexity

2007-05-22 Thread Georg Brandl
Steve Howell schrieb: > --- Guillaume Proux <[EMAIL PROTECTED]> wrote: > >> On 5/23/07, Steve Howell <[EMAIL PROTECTED]> >> wrote: >> > 17.7% of the files I searched have calls to >> open(). >> >> My understand is that the mythical "python 2.x -> >> 3.0" tool will >> automatically migrate your co

Re: [Python-3000] please keep open() as a builtin, and general concerns about Py3k complexity

2007-05-22 Thread Steve Howell
--- Georg Brandl <[EMAIL PROTECTED]> wrote: > ISTM that many modules using open() do also use > os.path > utilities to create the filename given to open(). In > that > case, you have an import statement in any case. > Not the case for us: 154 modules call only open() 11 modules call only o