can compile function have a bug?

[ygao]

compile('U"ÖÐ"','c:/test','single')

why is the result different?
a bug or another reason?

 

[Peter Otten]

why is the result different?
a bug or another reason?

How that particular output came to be I don't know, but you should be able
to avoid the confusion by either passing a unicode string to compile() or
specifying the encoding:
u'\u4e2d'

Peter

PS: In and all-UTF-8 environment I would have /expected/ to see
u'\xe4\xb8\xad'

and that's indeed what I get over here:
u'\xe4\xb8\xad'

 

[John Machin]

How that particular output came to be I don't know, but you should be able
to avoid the confusion by either passing a unicode string to compile() or
specifying the encoding:

u'\u4e2d'

Peter

PS: In and all-UTF-8 environment I would have /expected/ to see

u'\xe4\xb8\xad'

and that's indeed what I get over here:

u'\xe4\xb8\xad'

But it's not an all-UTF-8 environment; his_encoding = 'gb2312' or one
of its heirs/successors

Cheers,
John

 

[Peter Otten]

But it's not an all-UTF-8 environment; his_encoding = 'gb2312' or one
of its heirs/successors

Ouch. Almost understanding a problem hurts more than not understanding it at
all. I just had a refresher of the experience...

Peter

 

[ygao]

How that particular output came to be I don't know, but you should be able
to avoid the confusion by either passing a unicode string to compile() or
specifying the encoding:

u'\u4e2d'

this is what I want!
many thanks!