[Python-Dev] PEP for adding an sq_index slot so that any object, a or b, can be used in X[a:b] notation (original) (raw)
Guido van Rossum guido at python.org
Mon Feb 13 21:32:15 CET 2006
- Previous message: [Python-Dev] PEP for adding an sq_index slot so that any object, a or b, can be used in X[a:b] notation
- Next message: [Python-Dev] PEP for adding an sq_index slot so that any object, a or b, can be used in X[a:b] notation
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 2/13/06, Jim Jewett <jimjjewett at gmail.com> wrote:
Guido:
> I don't like trueint very much. Personally, > I'm fine with calling it index index is OK, but is there a reason integer would be rejected? int roughly follows the low-level C implementation, and may do odd things on unusual input. integer properly creates a conceptual integer, so it won't lose or corrupt information (unless the class writer does this intentionally).
Given the number of folks who misappreciate the difference between getattr and getattribute, I'm not sure I'd want to encourage using abbreviated and full forms of the same term in the same context. When confronted with the existence of int and integer I can see plenty of confusion ahead.
-- --Guido van Rossum (home page: http://www.python.org/~guido/)
- Previous message: [Python-Dev] PEP for adding an sq_index slot so that any object, a or b, can be used in X[a:b] notation
- Next message: [Python-Dev] PEP for adding an sq_index slot so that any object, a or b, can be used in X[a:b] notation
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]