This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author r.david.murray
Recipients carsten.klein@axn-software.de, docs@python, r.david.murray
Date 2013-01-28.22:00:14
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1359410414.84.0.129664893665.issue17067@psf.upfronthosting.co.za>
In-reply-to
Content
Thanks for your suggestion, but...

The example currently in the docs is exactly how we do deferred translation in the project I am currently working on.  Your example is much more complex, and I don't see the benefit of it.

Specifically, using the example in the docs you can easily mix deferred translations with non-deferred translations, which what you generally end up wanting to do in real code.  (You use deferred translation with strings that are defined at import time, as in the example, and non-deferred with strings that are computed at runtime.)

Perhaps there is a need for additional text about how this works in practice, including an example of switching the language dynamically during runtime.
History
Date User Action Args
2013-01-28 22:00:14r.david.murraysetrecipients: + r.david.murray, docs@python, carsten.klein@axn-software.de
2013-01-28 22:00:14r.david.murraysetmessageid: <1359410414.84.0.129664893665.issue17067@psf.upfronthosting.co.za>
2013-01-28 22:00:14r.david.murraylinkissue17067 messages
2013-01-28 22:00:14r.david.murraycreate