[issue17067] Examples in documentation for 3.x in 23.1.3.4. Deferred translations are rather weak

Irit Katriel added the comment: I can't find DeferredTranslation in the current codebase, and in any case the response from 8 years ago seems to be leaning towards reject. -- nosy: +iritkatriel resolution: -> out of date stage: -> resolved status: open -> closed ___

[issue17067] Examples in documentation for 3.x in 23.1.3.4. Deferred translations are rather weak

R. David Murray added the comment: Sorry, I didn't mean "computed at runtime", I meant defined in code where the _ call is *executed* at runtime, rather than at import time. -- ___ Python tracker _

[issue17067] Examples in documentation for 3.x in 23.1.3.4. Deferred translations are rather weak

R. David Murray added the comment: 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

[issue17067] Examples in documentation for 3.x in 23.1.3.4. Deferred translations are rather weak

New submission from Carsten Klein: The examples for the topic presented are rather weak. In fact, they merely present do nothing replacements for an actually working, deferred localization mechanism or some sort of prototypical implementation thereof. As such I propose that they be replaced wi