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 loewis
Recipients amaury.forgeotdarc, eckhardt, loewis, rpetrov
Date 2008-10-09.18:36:55
SpamBayes Score 1.6026328e-06
Marked as misclassified No
Message-id <48EE4F45.3040609@v.loewis.de>
In-reply-to <1223542171.62.0.443285152015.issue4075@psf.upfronthosting.co.za>
Content
> If the CE can't work with char why the compiler don't threat strings as
> wide characters always ?

I think this question is pointless - we don't have the power to change
how CE works. You might question whether Ulrich's analysis of the issue
is accurate (I think it is), or whether Python should support CE at all
(I think it should). FWIW, the compiler *does* "work with char", and it
needs to do so to support a byte type. It's just that the CE APIs don't
support char (at least, some of them apparently don't).
History
Date User Action Args
2008-10-09 18:37:00loewissetrecipients: + loewis, amaury.forgeotdarc, rpetrov, eckhardt
2008-10-09 18:37:00loewislinkissue4075 messages
2008-10-09 18:36:59loewiscreate