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 pitrou
Recipients ajaksu2, amaury.forgeotdarc, collinwinter, eric.smith, ezio.melotti, gvanrossum, jafo, jimjjewett, lemburg, orivej, pitrou, rhettinger
Date 2009-06-03.20:41:34
SpamBayes Score 2.25516e-09
Marked as misclassified No
Message-id <1244061829.5505.23.camel@localhost>
In-reply-to <1244048805.07.0.393821899189.issue1943@psf.upfronthosting.co.za>
Content
> Still, I expect that a vanishingly small number of users will actually
> use that feature. 

Apart from the example Marc-André just posted (and which is a 0.0.1
proof of concept he apparently just wrote), the number of users is,
AFAICT, zero.
Unless there's some closed source extension which happens to extend
unicode as a C subtype.

Now, as for easing the subclassing of unicode in C, there are probably
several possibilities which range from devising a clever set of macros
to abusing the ob_size field for a tagged pointer. People who really
care should do a concrete proposal (and I don't know who these people
are, apart from Marc-André).
History
Date User Action Args
2009-06-03 20:41:36pitrousetrecipients: + pitrou, lemburg, gvanrossum, collinwinter, rhettinger, jafo, jimjjewett, amaury.forgeotdarc, eric.smith, ajaksu2, orivej, ezio.melotti
2009-06-03 20:41:35pitroulinkissue1943 messages
2009-06-03 20:41:34pitroucreate