Re: [Python-3000] Mini Path object

2006-11-26 Thread Mike Orr
Status update and questions about root splitting. I've got a path module written (called unipath) and am in the middle of the unit tests. When they're done I'll release it for review. It's been slow coz I was setting up two computers at the same time. I tried to make a separate PathAlgebra clas

Re: [Python-3000] Special methods and interface-based type system

2006-11-26 Thread Jim Jewett
On 11/25/06, Phillip J. Eby <[EMAIL PROTECTED]> wrote: > However, in the normal use cases for generic functions, > you don't often put the methods directly in the classes! I think this gets to the core of my biggest worry. When I'm doing sysadmin-type maintenance (which at my employer does not m

Re: [Python-3000] Mini Path object

2006-11-26 Thread Jim Jewett
On 11/26/06, Mike Orr <[EMAIL PROTECTED]> wrote: > I tried to make a separate PathAlgebra class and FSPath class, but it > got so unweildly to use I made the latter a subclass. They're now > called PathName and Path. This makes sense to me. An FSPath without path algebra is basically a "director

Re: [Python-3000] Mini Path object

2006-11-26 Thread Mike Orr
On 11/26/06, Jim Jewett <[EMAIL PROTECTED]> wrote: > On 11/26/06, Mike Orr <[EMAIL PROTECTED]> wrote: > > I tried to make a separate PathAlgebra class and FSPath class, but it > > got so unweildly to use I made the latter a subclass. They're now > > called PathName and Path. > > This makes sense t

Re: [Python-3000] Mini Path object

2006-11-26 Thread Jim Jewett
On 11/26/06, Mike Orr <[EMAIL PROTECTED]> wrote: > On 11/26/06, Jim Jewett <[EMAIL PROTECTED]> wrote: > > On 11/26/06, Mike Orr <[EMAIL PROTECTED]> wrote: > > > I tried to make a separate PathAlgebra class and > > > FSPath class, but it got so unweildly to use I made > > > the latter a subclass. T

Re: [Python-3000] Mini Path object

2006-11-26 Thread Paul Moore
On 11/26/06, Jim Jewett <[EMAIL PROTECTED]> wrote: > On 11/26/06, Mike Orr <[EMAIL PROTECTED]> wrote: > > On 11/26/06, Jim Jewett <[EMAIL PROTECTED]> wrote: > > > C: without a slash is effectively a mount point into > > > the current directory. > > > That's what I always thought "C:foo" is. But G

Re: [Python-3000] optional argument annotations

2006-11-26 Thread Brett Cannon
On 11/24/06, Tony Lownds <[EMAIL PROTECTED]> wrote: > Obviously signature objects would grow support for annotations, but I > still need the information to be carried on the code object to > incorporate into signature objects. > Signature objects still need a way to know the nested parameters,

Re: [Python-3000] Mini Path object

2006-11-26 Thread Greg Ewing
Mike Orr wrote: > They're now called PathName and Path. Not a sane choice of names, since in this context, "path" and "pathname" are synonymous in ordinary language. -- Greg ___ Python-3000 mailing list [email protected] http://mail.python.org/mail

Re: [Python-3000] Abilities / Interfaces

2006-11-26 Thread Jim Jewett
On 11/22/06, Guido van Rossum <[EMAIL PROTECTED]> wrote: > On 11/22/06, Walter Dörwald <[EMAIL PROTECTED]> wrote: > > Another effect of __special__ methods is that they divide > > the class namespace into two parts: The __special__ names > > are those that have to be implemented to support core > >

Re: [Python-3000] Abilities / Interfaces

2006-11-26 Thread Jim Jewett
On 11/22/06, Phillip J. Eby <[EMAIL PROTECTED]> wrote: > At 08:36 AM 11/22/2006 -0500, Benji York wrote: > >It seems to me that not all interfaces coincide with > >something the object can _do_. ... > Aren't these also *operations* being performed? ISafeForThreading may boil down to certain oper

Re: [Python-3000] Abilities / Interfaces

2006-11-26 Thread Phillip J. Eby
At 04:52 PM 11/26/2006 -0500, Jim Jewett wrote: >On 11/22/06, Phillip J. Eby <[EMAIL PROTECTED]> wrote: > > At 08:36 AM 11/22/2006 -0500, Benji York wrote: > > >It seems to me that not all interfaces coincide with > > >something the object can _do_. ... > > > Aren't these also *operations* being p

Re: [Python-3000] optional argument annotations

2006-11-26 Thread Tony Lownds
On Nov 26, 2006, at 1:10 PM, Brett Cannon wrote: On 11/24/06, Tony Lownds <[EMAIL PROTECTED]> wrote: > Obviously signature objects would grow support for annotations, but I > still need the information to be carried on the code object to > incorporate into signature objects. > Signature obj

Re: [Python-3000] Abilities / Interfaces

2006-11-26 Thread Jim Jewett
On 11/22/06, Guido van Rossum <[EMAIL PROTECTED]> wrote: > I'd much rather have a few "big" interfaces (Number, > RealNumber, Integer) than lots of small ones > Pedroni-style (number-that-support-exponentiation, > number-that-supports-bitwise-and, > number-that-supports-left-shift, ...?). My under

Re: [Python-3000] Fwd: defop ?

2006-11-26 Thread Guido van Rossum
On 11/25/06, Calvin Spealman <[EMAIL PROTECTED]> wrote: > I will make only one more comment and then ill drop my comments > without direct questions. > > On 11/25/06, Guido van Rossum <[EMAIL PROTECTED]> wrote: > > Hm. The double colon rubs me the wrong way (Perl and/or C++). But > > apart from tha

Re: [Python-3000] Abilities / Interfaces

2006-11-26 Thread Guido van Rossum
On 11/25/06, Jim Jewett <[EMAIL PROTECTED]> wrote: > Personally, I stand by my assessment that they can make metaclasses > look straightforward -- but that is partly because metaclasses have > had their roughest edges worn off already. (For example, they no > longer require compiling a C class so

Re: [Python-3000] Special methods and interface-based type system

2006-11-26 Thread Bill Janssen
> > I'll still drop off a copy (of Common Lisp the Language, version 2), > > but there's no need to wait. It's on the Web at > > http://www.supelec.fr/docs/cltl/clm/node260.html. See in particular > > the "change-class" operation at > > http://www.supelec.fr/docs/cltl/clm/node305.html. > > > > I

Re: [Python-3000] Abilities / Interfaces

2006-11-26 Thread Bill Janssen
> It may also be that only a good unified solution to "A" is needed in order to > allow library and user code to be written "easier" to address "B","C" and > "D". > It may even be just doing "A" is a good enough 95% solution (works well > enough > for 95% of actual use cases) and nothing more

Re: [Python-3000] Special methods and interface-based type system

2006-11-26 Thread Bill Janssen
> I had thought that you (Bill), (along with PJE) were assuming that the > generic function or interface itself would serve to distinguish the > namespace. Instead of > > class A(object): > def magic_meth_foo(self, ...): > > I would write > > class A(object): > defop foo

[Python-3000] Generic function queries

2006-11-26 Thread Ross Jekel
Hi, I've been reading the discussions on interfaces and generic functions with much interest. Some people have expressed concerns that readability and code discovery (where is the code that this call is going to run) may suffer. Could someone please address some simple questions for me about th

Re: [Python-3000] Fwd: defop ?

2006-11-26 Thread Calvin Spealman
On 11/26/06, Guido van Rossum <[EMAIL PROTECTED]> wrote: > On 11/25/06, Calvin Spealman <[EMAIL PROTECTED]> wrote: > > I will make only one more comment and then ill drop my comments > > without direct questions. > > > > On 11/25/06, Guido van Rossum <[EMAIL PROTECTED]> wrote: > > > Hm. The double

Re: [Python-3000] Special methods and interface-based type system

2006-11-26 Thread Fredrik Lundh
Bill Janssen wrote: > Now, I don't see why the connection to the > underlying VM implementation needs name-mangling -- it would be > reasonable just to define a distinguished module (call it, say, for > tradition's sake, "__VM__" :-), and put them in that module. putting methods in a module? how