[Python-Dev] object capability; func_closure; subclasses (original) (raw)
Phillip J. Eby pje at telecommunity.com
Thu Jun 28 17:44:16 CEST 2007
- Previous message: [Python-Dev] object capability; func_closure; __subclasses__
- Next message: [Python-Dev] object capability; func_closure; __subclasses__
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
At 04:14 PM 6/28/2007 +0100, tav wrote:
> Well, there's no self in 2.3 or 2.4; I guess that was added in 2.5. Darn.
anyone know why it was added? > >Or, setting call.doc ? > > What does that do? ah, i just wanted a way of providing documentation, and call's doc isn't writable... > If it works, you could probably do the same thing to remove call.self. will look into that too... > In 3.0, I don't mind if the access method moves, I just want to keep > the access. OTOH, I don't really care about call.self, since > I got along fine without it in 2.3/2.4 and didn't know it had been > added in 2.5. :) w00p! so, suggestions as to how one can go about getting those 2 access methods moved?
Post a proposal on the Python-3000 list and supply patches to do the moves.
- Previous message: [Python-Dev] object capability; func_closure; __subclasses__
- Next message: [Python-Dev] object capability; func_closure; __subclasses__
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]