On 4 janv. 2015, at 22:09, Tim Graham <[email protected]> wrote: > > I don't think it's fair to put pressure on Aymeric like that.
My throughput on this project has been rather stable. There’s only so much I can do by next week. Pressure won’t add hours to my days anyway ;-) As a consequence I don’t want to weigh in one way or another. I’ll just do my best within the allotted time. As Tim reminded us, 1.8 will be a LTS, which means that robustness is more important than features. I’m working under this assumption and erring on the side of caution when introducing new APIs. Here are the main limitations I know of, to help make the decision. Missing pieces Documentation: I’m making good progress and I’m confident that it will be committed within one week. Deprecating Template.render(Context) - where Template is a backend-specific Template, not a django.template.Template: I think I can complete the patch next weekend. i18n / makemessages: I hope I can get away with a small hack to support both the DTL and Jinja2, as suggested in #23299 [1]. I haven’t checked the code [2]. Limitation: makemessages won’t work with third-party template backends. Timeline: probably 1.9 — one suggested solution is to integrate Babel. Origin API: I have left aside the discussion with Preston Timmons for now. It's hard to estimate what its outcome will be and how much work it will require. Limitation: the debug view may be less useful with non-DTL engines when a template isn’t found. Timeline: unknown Traceback integration: perhaps Jinja2’s traceback integration will just work and peacefully cohabit with Django’s custom implementation but I’m not taking bets. Limitation: the debug view may be less useful with non-DTL engines when rendering a template raises an exception. Timeline: unknown django.contrib.admindocs & syndication: they depend on Engine.get_current(). Limitation: these apps won't work when zero or more than one DjangoTemplates engines are configured. Timeline: hopefully 1.8 beta Broken pieces current_app: currently it’s impossible to reverse namespaced URLs with a non- default instance namespace outside of a request handling cycle [3] e.g. when sending email. Today’s discussion with Florian on #django-dev shows that this regression may be a problem. Plus, of course, everything that will be reported after the alpha release :-) I believe everything else is sufficiently small not to qualify as a new feature, meaning that it can be taken care of after the alpha and before the beta. Making sure that all Django-specific template tags have plain Python equivalents may require documenting new APIs but they will be transliterations of existing APIs so there’s very little at stake. Reviewing and perhaps updating the list of context processors in the default settings.py template seems small enough to be changed in the beta. Fixing the debug view that still depends on Engine.get_default() counts as a bugfix, not a new feature. -- Aymeric. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/F603DBE2-BDD6-4E2F-91AE-47B75937AA86%40polytechnique.org. For more options, visit https://groups.google.com/d/optout.
