[Python-3000] bytes & Py_TPFLAGS_BASETYPE (original) (raw)
Greg Ewing greg.ewing at canterbury.ac.nz
Mon Sep 17 06:08:31 CEST 2007
- Previous message: [Python-3000] bytes & Py_TPFLAGS_BASETYPE
- Next message: [Python-3000] bytes & Py_TPFLAGS_BASETYPE
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Guido van Rossum wrote:
It is possible to compromise the integrity of a built-in type by subclassing it if the type wasn't carefully written to expect subclassing.
Disallowing subclassing in Python may make sense, but it seems unreasonable not to allow subclassing by consenting C code that is careful not to compromise any integrity.
Maybe there should be two flags for this instead of just one?
-- Greg Ewing, Computer Science Dept, +--------------------------------------+ University of Canterbury, | Carpe post meridiem! | Christchurch, New Zealand | (I'm not a morning person.) | greg.ewing at canterbury.ac.nz +--------------------------------------+
- Previous message: [Python-3000] bytes & Py_TPFLAGS_BASETYPE
- Next message: [Python-3000] bytes & Py_TPFLAGS_BASETYPE
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]