Victor STINNER wrote:
> RexFi explains me that Python can't guess eval('len(u"é")') charset.
I personally like to see a charset argument for eval() and compile().
exec would not directly support other charsets; you would have to
compile() first to specify a charset.
I have a patch somewhere that
Le mardi 13 septembre 2005 à 17:56 +0900, Hye-Shik Chang a écrit :
> On 9/11/05, Victor STINNER <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > I found a bug in Python interactive command line (program python alone:
> > looks to be code.interact() function in code.py). With UTF-8 locale, the
> > comman
On 9/13/05, Hye-Shik Chang <[EMAIL PROTECTED]> wrote:
> On 9/11/05, Victor STINNER <[EMAIL PROTECTED]> wrote:
> >
> > I found a bug in Python interactive command line (program python alone:
> > looks to be code.interact() function in code.py). With UTF-8 locale, the
> > command << u"é" >> returns <
On 9/11/05, Victor STINNER <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I found a bug in Python interactive command line (program python alone:
> looks to be code.interact() function in code.py). With UTF-8 locale, the
> command << u"é" >> returns << u'\xc3\xa9' >> and not << u'\xE9' >>.
> Remember: the f
Hi,
I found a bug in Python interactive command line (program python alone:
looks to be code.interact() function in code.py). With UTF-8 locale, the
command << u"é" >> returns << u'\xc3\xa9' >> and not << u'\xE9' >>.
Remember: the french e with acute is Unicode 233 (0xE9), encoded \xC3
\xA9 in UTF
