klen / asgi-babel

Adds internationalization (i18n) support to ASGI applications (Asyncio/Trio)

Hi there, I'm Kirill 👋

• 🔭 I’m currently working on Muffin ecosystem
• 🌱 I’m currently learning Rust
• 💬 Ask me about anything here
• 📫 How to reach me: [email protected]

asgi-babel's Issues

Add support for lazy gettext functions variants

Hello there 👋

When developing web apps, it's a common pattern to put translated strings in modules or class definitions. For example, with WTForms:

class RegistrationForm(Form):
    name = StringField(_('Name'))

At module import, the locale is not yet known, maybe messages are even not loaded. To circumvent this, frameworks usually come with "lazy" variants of functions which are interpolated only when rendering the final template, at a time where the locale is known.

Currently, asgi-babel only provides the "normal" gettext functions. It could be useful to have the lazy variants at hand in this context.

The implementation should be quite straightforward, as Babel conveniently bundles as LazyProxy class. It could look like this:

def gettext_lazy(string: str, domain: str = None, **variables):
    return support.LazyProxy(gettext, string, domain, **variables)

# ... and so on for `pgettext` and `npgettext`

I've tested it in one of my project, and it works well. Do you think it would be a useful addition? If so, I would be happy to propose a PR for this.

Cheers!