"Exploding" (**myvariable) a dict with unicode keys

[Devin]

So Python can have unicode variable names but you can't
"explode" (**myvariable) a dict with unicode keys? WTF?

-Devin

 

[Martin v. Löwis]

So Python can have unicode variable names but you can't
"explode" (**myvariable) a dict with unicode keys? WTF?

That works fine for me.

Regards,
Martin

 

[Peter Otten]

That works fine for me.

The OP probably means
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
TypeError: f() keywords must be strings

Peter

 

[Devin]

The OP probably means


Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: f() keywords must be strings

Peter

Yes, that's exactly what I mean.

 

[Martin v. Löwis]

Yes, that's exactly what I mean.

Hmm. Why did you say that Python can have unicode variable
names? In the version you are using, it can't. In Python
3.0, it can, but then, you can also use Unicode strings
as keys in **arguments, in Python 3.0.

Regards,
Martin

 

[Bruno Desthuilliers]

Devin a écrit :
(snip)

Oh. I read somewhere that UTF-8 variable names we're supported.

utf-8 is *not* unicode.

 

[Devin]

Hmm. Why did you say that Python can have unicode variable
names? In the version you are using, it can't. In Python
3.0, it can, but then, you can also use Unicode strings
as keys in **arguments, in Python 3.0.

Regards,
Martin

Oh. I read somewhere that UTF-8 variable names we're supported. I
thought I even saw a colleague using Kanji.

 

[Martin v. Löwis]

Oh. I read somewhere that UTF-8 variable names we're supported. I

thought I even saw a colleague using Kanji.

In source code (string literals, comments), surely. Not in variable
names, not in 2.x.

To rephrase Bruno's comment: Python supports UTF-8 as a source encoding.
That doesn't mean that you can use all Unicode characters in all places
of the code.

Regards,
Martin