On Thu, May 1, 2008 at 2:15 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> Torsten, I agree. Let's just rename ugettext() to gettext() and have it
> return unicodes. That's the cleanest API we can do for Python.
I have a patch for something like this at issue 2512.
--
Cheers,
Benjamin Peters
> Sounds like you agree that we should just rename the u-variants and
> forget about deprecation, correct?
Exactly.
Regards,
Martin
___
Python-3000 mailing list
Python-3000@python.org
http://mail.python.org/mailman/listinfo/python-3000
Unsubscribe:
htt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 1, 2008, at 2:59 PM, Martin v. Löwis wrote:
Are we going to want to keep the "u" variants of the gettext APIs
around in 3.0? Also, the unicode parameters (for .install methods)
don't make much sense in 3.0.
I don't see how we could remove th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Apr 30, 2008, at 2:41 PM, Torsten Bronger wrote:
Indeed. From today's perspective, I see no use case for getting
human text snippets in byte strings encoded with the same encoding
that just happened to be used in the .mo file, or with the
"prefe
> Are we going to want to keep the "u" variants of the gettext APIs
> around in 3.0? Also, the unicode parameters (for .install methods)
> don't make much sense in 3.0.
>
> I don't see how we could remove them in 3.0, but perhaps rename then
> to their non-"u" variants and deprecate?
I think the
Hallöchen!
Barry Warsaw writes:
> On Apr 24, 2008, at 6:18 PM, Guido van Rossum wrote:
>
>> [...]
>>
>> -- Forwarded message --
>> From: Benjamin Peterson <[EMAIL PROTECTED]>
>> Date: Wed, Apr 23, 2008 at 7:32 AM
>> S
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Apr 24, 2008, at 6:18 PM, Guido van Rossum wrote:
Care to comment? Or know who should comment?
-- Forwarded message --
From: Benjamin Peterson <[EMAIL PROTECTED]>
Date: Wed, Apr 23, 2008 at 7:32 AM
Subject: [Python-3000] g
[I'm not a gettext expert, so sorry if the following is totally wrong. :)]
Are we going to want to keep the "u" variants of the gettext APIs
around in 3.0? Also, the unicode parameters (for .install methods)
don't make much sense in 3.0.
I don't see how we could remove them in 3.0, but perhaps re
