Re: [Python-Dev] Terminology for PEP 343

2005-07-02 Thread Ron Adam
Raymond Hettinger wrote: > Hmm, that got me to thinking a bit more. Here's another subjective two > cents worth. "exit" seems to be a more global concept and "leave" seems > more local. For instance, I leave a room but exit a building. In > Python, sys.exit and os._exit are grand exits rather

Re: [Python-Dev] Terminology for PEP 343

2005-07-02 Thread Jeff Rush
On Friday 01 July 2005 10:45 am, Fred L. Drake, Jr. wrote: > On Friday 01 July 2005 11:44, Phillip J. Eby wrote: > > Resource managers. > > Yeah, I was thinking that, but was somewhat ambivalent. But I definately > like it better than anything else proposed so far. I like that as well. My hat i

Re: [Python-Dev] Money module

2005-07-02 Thread Aahz
On Sat, Jul 02, 2005, Facundo Batista wrote: > On 7/1/05, Raymond Hettinger <[EMAIL PROTECTED]> wrote: >> >> * Time value of money computations are typically dimensionless (not >> sensitive to currency type or formatting) and they often have algorithm >> specific rounding needs (round at the end o

Re: [Python-Dev] reducing self.x=x; self.y=y; self.z=z boilerplate code

2005-07-02 Thread Ralf W. Grosse-Kunstleve
Aahz wrote: > This is off-topic for python-dev. Please take it to comp.lang.python. > (It's not immediately obvious that this is off-topic, I know, but please > take my word for it.) Done: http://mail.python.org/pipermail/python-list/2005-July/288292.html Sorry for creating so much noise he

Re: [Python-Dev] Money module

2005-07-02 Thread Facundo Batista
On 7/1/05, Raymond Hettinger <[EMAIL PROTECTED]> wrote: > [Facundo] > > The pre-PEP is almost done, and the corresponding > > test cases are all written. > > What is the part about the pre-PEP? Something like this probably > shouldn't go in the standard library until it has been proven in the >

Re: [Python-Dev] reducing self.x=x; self.y=y; self.z=z boilerplate code

2005-07-02 Thread Terry Reedy
"Ralf W. Grosse-Kunstleve" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > I'd also be happy with > > def __init__(self, self.x, self.y, self.z): > > which wouldn't be too different from unpacking tuples If you are willing to require that the args be passed as a tuple (ext

Re: [Python-Dev] reducing self.x=x; self.y=y; self.z=z boilerplate code

2005-07-02 Thread Josiah Carlson
"Ralf W. Grosse-Kunstleve" <[EMAIL PROTECTED]> wrote: > Josiah Carlson wrote: > > Now, don't get me wrong, definining __slots__ can be a pain in the > > tookus, but with a proper metaclass, that metaclass can define the > > __slots__ attribute based on the argument list for __init__(). > > > > Th

Re: [Python-Dev] reducing self.x=x; self.y=y; self.z=z boilerplate code

2005-07-02 Thread Reinhold Birkenfeld
Nick Coghlan wrote: [...] > If the right hand side of 'as' permitted the same forms as are going > to be permitted for the 'as' clause in 'with' statements, then Ralf's > situation could be handled via: > >def __init__(self as s, x as s.x, y as s.y, z as s.z): > pass > > Essentially