Re: [Python-Dev] Replacement for print in Python 3.0

2005-09-12 Thread Andrew Durdin
On 9/6/05, Guido van Rossum <[EMAIL PROTECTED]> wrote: > > My hypothesis is that there are actually only two use cases that > matter enough to be supported directly: > > (a) quickly print a bunch of items with spaces in between them and a > trailing newline > > (b) print one or more items with p

Re: [Python-Dev] Simplify the file-like-object interface

2005-09-12 Thread Andrew Durdin
On 9/6/05, Antoine Pitrou <[EMAIL PROTECTED]> wrote: > > One could use "class decorators". For example if you want to define the > method foo() in a file-like class, you could use code like: I like the sound of this. Suppose there were a function textstream() that decorated a file-like object (su

Re: [Python-Dev] Python 3 executable name (was: Re: PEP 3000 and iterators)

2005-09-12 Thread Bill Janssen
> Perhaps the renaming should be more radical, to indicate the extent of > the change. Another possiblity would be to use the new name to indicate a position in a spectrum of programming languages. For instance, "beryl", "topaz", "steel" and "jade" are (on the Mohs scale) all sturdier than pearl

Re: [Python-Dev] Python 3 executable name (was: Re: PEP 3000 and iterators)

2005-09-12 Thread Bill Janssen
> perhaps the Python 3 executable should have a different name as part > of the standard distribution? I suggest "py" / "py.exe" Perhaps the renaming should be more radical, to indicate the extent of the change. I suggest "second", to commemorate "Second City" in Chicago, another famous comedy tr

Re: [Python-Dev] unintentional and unsafe use of realpath()

2005-09-12 Thread Peter Jones
On Mon, 2005-09-12 at 17:23 +1200, Greg Ewing wrote: > Peter Jones wrote: > > > Another problem (which I have not fixed) is that when realpath() is > > used, in some cases MAXPATHLEN is smaller than the system's > > PATH_MAX/pathconf(path, _PC_PATH_MAX). > > The linux man page for realpath() has

Re: [Python-Dev] PEP 3000 and iterators

2005-09-12 Thread Guido van Rossum
On 9/11/05, Delaney, Timothy (Tim) <[EMAIL PROTECTED]> wrote: > James Y Knight wrote: > > > Just to be clear, I do not want nor expect this. I wish to be able to > > specifically modify code with full knowledge of what has changed in > > Py3.0 such that it will work with both Py2.X and Py3.0. > >

Re: [Python-Dev] Tools directory (Was RE: Replacement for print in Python 3.0)

2005-09-12 Thread Reinhold Birkenfeld
Brett Cannon wrote: > On 9/8/05, Tony Meyer <[EMAIL PROTECTED]> wrote: >> [finding Tools/i18n/pygettext.py] >> > You're right, I think Tools is probably a bad place for >> > anything. If it's not part of the stdlib, I'll likely never >> > find it. >> >> Agreed. Maybe with the introduction of -m

Re: [Python-Dev] Python 3 executable name

2005-09-12 Thread Paul Moore
On 9/12/05, Greg Ewing <[EMAIL PROTECTED]> wrote: > Oren Tirosh wrote: > > > I suggest an explicitly and permanently different name for the > > interpreter executable of this new and incompatible branch of the > > language. I want Python 3 scripts starting with #! to have an average > > shelf life

Re: [Python-Dev] Python 3 executable name

2005-09-12 Thread Greg Ewing
Oren Tirosh wrote: > I suggest an explicitly and permanently different name for the > interpreter executable of this new and incompatible branch of the > language. I want Python 3 scripts starting with #! to have an average > shelf life longer than 18 months. That makes sense, but I'd prefer some