private variables/methods
Terry Reedy
tjreedy at udel.edu
Sun Oct 12 13:49:54 EDT 2003
More information about the Python-list mailing list
Sun Oct 12 13:49:54 EDT 2003
- Previous message (by thread): private variables/methods
- Next message (by thread): private variables/methods
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
"Alex Martelli" <aleaxit at yahoo.com> wrote in message news:Iseib.204801$hE5.6891483 at news1.tin.it... > Terry Reedy wrote: > >> I think that __current_module__ is perhaps a bit too lengthy > > and redundant ;-) I was slightly wrong since __name__ allows but does not constitute a binding of the module itself. > I disagree. Lengthy it may be, but we do want a 'reserved module > name' to use for this purpose. I believe it would be easily possible to bind a module to <module>.__self__ or <module>. __module__ at the same time <module>__name__, .__file__, and .__doc__ are. ('Current' is no more needed for __module__ than for the other vars.) If their were use cases for self-access nearly as good as those for the others, and not just the cuteness factor, I would support the addition. I would guess that Guido and the other main developers either have not had such needs or have not recognized such needs. Don't know if this addition has been discussed before, and don't have time to search right now. Terry J. Reedy
- Previous message (by thread): private variables/methods
- Next message (by thread): private variables/methods
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list