On 30. januar 2008 14:31, Gabriel Genellina wrote:
>On 30 ene, 07:54, <[EMAIL PROTECTED]> wrote:
>> On 30. januar 2008 10:48, Marc 'BlackJack' Rintsch wrote:
>>
>> >On Wed, 30 Jan 2008 09:57:55 +0100, David.Reksten wrote:
>>
>> >> How can
On 30. januar 2008 10:48, Marc 'BlackJack' Rintsch wrote:
>On Wed, 30 Jan 2008 09:57:55 +0100, David.Reksten wrote:
>
>> How can I convert a string read from a database containing unicode
>> literals, such as "Fr\u00f8ya" to the latin-1 equivalent, "F
On 30. januar 2008 10:21, Berteun Damman wrote:
>On Wed, 30 Jan 2008 09:57:55 +0100, <[EMAIL PROTECTED]>
><[EMAIL PROTECTED]> wrote:
>> How can I convert a string read from a database containing unicode
>> literals, such as "Fr\u00f8ya" to the latin-1 equivalent, "Frøya"?
>>
>> I have tried vari
How can I convert a string read from a database containing unicode literals,
such as "Fr\u00f8ya" to the latin-1 equivalent, "Frøya"?
I have tried variations around
"Fr\u00f8ya".decode('latin-1')
but to no avail.
.david
--
http://mail.python.org/mailman/listinfo/python-list
Torsten Bronger writes:
>[EMAIL PROTECTED] writes:
>
>> Torsten Bronger wrote:
>>
>>> [...]
>>>
>>> Right, that's because I've used "__" where not all returning
>>> values are interesing to me such as
>>>
>>> a, b, __ = function_that_returns_three_values(x, y)
>>
>> Variable name "dummy" serves the
Torsten Bronger wrote:
>Hallöchen!
>
>Ben Finney writes:
>
>> "Diez B. Roggisch" <[EMAIL PROTECTED]> writes:
>>
>>> The underscore is used as "discarded" identifier. So maybe
>>>
>>> for _ in xrange(10):
>>> ...
>>
>> The problem with the '_' name is that it is already well-known and
>> long-u