On Wed, Feb 8, 2017 at 11:36 AM, Hans-Peter Jansen <h...@urpla.net> wrote:
> As a consequence, all these packages will depend on lingua then.. > Do the packages actually need to depend on lingua? I see that your PR to deform doesn't add it, however deform expects it to in the dev environment (tests, running i18n.sh, etc). I'm just trying to clarify if you're saying it would be a new runtime dependency. > One downside of this move: jinja2 support depends on babel, and needs some > configuration file support for pot-create, that has to be patched into > i18n.sh > before: > The quick history here, as I know it: - Pyramid, etc shipped using babel for everything. - Babel didn't support py3. - For that reason and I'm sure many other reasons, Wichert created lingua and submitted a few PRs to pyramid to start using it in the documentation. I personally don't know what the state of the art is now that babel supports py3 I haven't needed to write a fully i18n app myself and so my knowledge is only limited to diving in and fixing certain bugs or reviewing PRs. I very much appreciate your work on this and would love to see things get standardized and modernized. I've had several people ask in #pyramid on IRC why things are not working as our docs kinda sort of tell you to use both babel and lingua without definitively explaining anything as I think they were only partially updated when switching to lingua. -- You received this message because you are subscribed to the Google Groups "pylons-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to pylons-devel+unsubscr...@googlegroups.com. To post to this group, send email to firstname.lastname@example.org. Visit this group at https://groups.google.com/group/pylons-devel. For more options, visit https://groups.google.com/d/optout.