This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author gvanrossum
Recipients ajaksu2, amaury.forgeotdarc, collinwinter, eric.smith, ezio.melotti, gvanrossum, jafo, jimjjewett, lemburg, orivej, pitrou, rhettinger
Date 2009-06-03.17:06:42
SpamBayes Score 1.67839e-07
Marked as misclassified No
Message-id <1244048805.07.0.393821899189.issue1943@psf.upfronthosting.co.za>
In-reply-to
Content
Hm, so the extra pointer is a feature.  I guess a compromise would be to
keep the extra indirection but make it point into the same object in the
base class.  Thinking about how memory caching in modern CPUs work, this
would probably be quite fast but it would still cost 8 bytes on most
future (i.e., 64-bit) architectures.

Still, I expect that a vanishingly small number of users will actually
use that feature.  Is it worth to make everyone pay for that
flexibility, for what must be the first- or second-most commonly used
type in Python 3.x (the other being int), which is still significantly
slower than the common (8-bit) string type in 2.x?
History
Date User Action Args
2009-06-03 17:06:45gvanrossumsetrecipients: + gvanrossum, lemburg, collinwinter, rhettinger, jafo, jimjjewett, amaury.forgeotdarc, pitrou, eric.smith, ajaksu2, orivej, ezio.melotti
2009-06-03 17:06:45gvanrossumsetmessageid: <1244048805.07.0.393821899189.issue1943@psf.upfronthosting.co.za>
2009-06-03 17:06:43gvanrossumlinkissue1943 messages
2009-06-03 17:06:42gvanrossumcreate