Glenn Linderman <[EMAIL PROTECTED]> writes:
> In this message I'll discuss a scheme for handling complex
> translations with multiple numeric parameters.
Have you had a look at the ngettext function?
http://docs.python.org/dev/library/gettext.html#gettext.ngettext
I think it does most of what
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all.
Sorry for spamming several mailing list.
After many hours of hard work, I'm proud to present a preview of pybsddb
4.7.3, able to compile and work under Python 2.3, 2.4, 2.5, 2.6b2 and 3.0b2.
You can try it out downloading it directly from m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin v. Löwis wrote:
|> So, I'm thinking seriously in accepting *ONLY* "bytes" in the bsddb API
|> (when working under Python 3.0), and do the proxy thing *ONLY* in the
|> testsuite, to be able to reuse it.
|>
|> What do you think?.
|
| I think you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mike Klaas wrote:
| You may find this thread to be relevant:
|
| http://mail.python.org/pipermail/python-3000/2007-August/009197.html
Very relevant, indeed.
I will think about the "callback" option to convert both keys and values
(in both directions
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
M.-A. Lemburg wrote:
| Since bsddb is about storing arbitrary data, I think just accepting
| bytes for both keys and values is more intuitive.
Agreed. This is the approach I've done in current code.
| The question of encoding is application and data
