Re: Multiple template engines for Django - week 13
Hello, I published my update for week 15: https://myks.org/en/multiple-template-engines-for-django/#2015-01-18 -- Aymeric. > On 11 janv. 2015, at 00:02, Aymeric Augustin > wrote: > > Hello, > > Here’s episode 14: > https://myks.org/en/multiple-template-engines-for-django/#2015-01-11 > > Hopefully I’ll reach the point where I don’t have enough material to write > a weekly update by the end of February :-) > > -- > Aymeric. > > > >> On 4 janv. 2015, at 00:23, Aymeric Augustin >> wrote: >> >> Hello, >> >> Here’s the thirteenth update (good thing I learnt all these ordinals when I >> was a kid!) >> https://myks.org/fr/multiple-template-engines-for-django/#2015-01-04 >> >> At this point my main concern is the 1.8 feature freeze scheduled in one >> week. >> Dealing properly with some of the items I listed in my report for week 11 may >> require changes falling in the "new features” bucket and therefore being >> postponed to Django 1.9. At worst, I’ll have to document that some features >> only work with the Django template language in Django 1.8. That’s sad but not >> worth delaying the entire project until early 2016. >> >> -- >> Aymeric. >> >> >> >>> On 27 déc. 2014, at 23:59, Aymeric Augustin >>> wrote: >>> >>> Hello, >>> >>> My twelfth update is online: >>> https://myks.org/en/multiple-template-engines-for-django/#2014-12-28 >>> >>> It comes with a question — should I drop `select_template` from the backend >>> API? I think I should. Follow the link above for details. >>> >>> Looking forward to your feedback, >>> >>> -- >>> Aymeric. >>> >>> >>> On 20 déc. 2014, at 23:57, Aymeric Augustin wrote: Hello, I haven’t written to this mailing-list for three weeks because nothing warranted your immediate attention. Now the code is in reasonably good shape. Feel free to have a look: https://github.com/aaugustin/django/commits/multiple-template-engines I plan to merge this branch within a few days. Updates for weeks 9 to 11 are available at the usual location: https://github.com/aaugustin/django/commits/multiple-template-engines -- Aymeric. > On 30 nov. 2014, at 10:37, Aymeric Augustin > wrote: > > Hello, > > Here’s my eight update — this is getting repetitive :-) > https://myks.org/en/multiple-template-engines-for-django/#2014-11-30 > > -- > Aymeric. > > > >> On 23 nov. 2014, at 00:02, Aymeric Augustin >> wrote: >> >> Hello, >> >> I published my seventh update: >> https://myks.org/en/multiple-template-engines-for-django/#2014-11-23 >> >> I have another pull request ready for review: >> https://github.com/django/django/pull/3605 >> >> Let me know if you have any questions! >> >> -- >> Aymeric. >> >> >> >>> On 16 nov. 2014, at 09:19, Aymeric Augustin >>> wrote: >>> >>> Hello, >>> >>> Here’s my sixth update: >>> https://myks.org/en/multiple-template-engines-for-django/#2014-11-16 >>> >>> I have a first pull request ready for review: >>> https://github.com/django/django/pull/3555 >>> >>> Whenever possible, I’ll merge changes that make sense regardless of the >>> Multiple Template Engines Project in small batches, in order to >>> minimize the size of the final pull request. >>> >>> -- >>> Aymeric. >>> >>> >>> On 9 nov. 2014, at 22:05, Aymeric Augustin wrote: Hello, Here’s my fifth update: https://myks.org/en/multiple-template-engines-for-django/#2014-11-09 The first step of my project, as outlined in my original proposal, is complete. -- Aymeric. > On 1 nov. 2014, at 23:30, Aymeric Augustin > wrote: > > Hello, > > I’m happy to annonce that the DEP is ready for public review! > > Direct link, HTML: > https://myks.org/en/multiple-template-engines-for-django/dep/ > > Direct link, ReStructured Text: > https://raw.githubusercontent.com/aaugustin/mtefd/master/multiple-template-engines.rst > > (I’m not reproducing it here because I don’t think email is a very > good medium for communicating 50kB of markup.) > > I’ve written a bit more about what “ready” means: > https://myks.org/en/multiple-template-engines-for-django/#2014-11-01 > > Of course, your regularly scheduled update will also be available (in > half an hour): > https://myks.org/en/multiple-template-engines-for-django/#2014-11-02 > > I’m looking forward to your feedback! > > -- > Aymeric. > >
Re: Multiple template engines for Django - week 13
Hello, Here’s episode 14: https://myks.org/en/multiple-template-engines-for-django/#2015-01-11 Hopefully I’ll reach the point where I don’t have enough material to write a weekly update by the end of February :-) -- Aymeric. > On 4 janv. 2015, at 00:23, Aymeric Augustin > wrote: > > Hello, > > Here’s the thirteenth update (good thing I learnt all these ordinals when I > was a kid!) > https://myks.org/fr/multiple-template-engines-for-django/#2015-01-04 > > At this point my main concern is the 1.8 feature freeze scheduled in one week. > Dealing properly with some of the items I listed in my report for week 11 may > require changes falling in the "new features” bucket and therefore being > postponed to Django 1.9. At worst, I’ll have to document that some features > only work with the Django template language in Django 1.8. That’s sad but not > worth delaying the entire project until early 2016. > > -- > Aymeric. > > > >> On 27 déc. 2014, at 23:59, Aymeric Augustin >> wrote: >> >> Hello, >> >> My twelfth update is online: >> https://myks.org/en/multiple-template-engines-for-django/#2014-12-28 >> >> It comes with a question — should I drop `select_template` from the backend >> API? I think I should. Follow the link above for details. >> >> Looking forward to your feedback, >> >> -- >> Aymeric. >> >> >> >>> On 20 déc. 2014, at 23:57, Aymeric Augustin >>> wrote: >>> >>> Hello, >>> >>> I haven’t written to this mailing-list for three weeks because nothing >>> warranted your immediate attention. >>> >>> Now the code is in reasonably good shape. Feel free to have a look: >>> https://github.com/aaugustin/django/commits/multiple-template-engines >>> >>> I plan to merge this branch within a few days. >>> >>> Updates for weeks 9 to 11 are available at the usual location: >>> https://github.com/aaugustin/django/commits/multiple-template-engines >>> >>> -- >>> Aymeric. >>> >>> >>> On 30 nov. 2014, at 10:37, Aymeric Augustin wrote: Hello, Here’s my eight update — this is getting repetitive :-) https://myks.org/en/multiple-template-engines-for-django/#2014-11-30 -- Aymeric. > On 23 nov. 2014, at 00:02, Aymeric Augustin > wrote: > > Hello, > > I published my seventh update: > https://myks.org/en/multiple-template-engines-for-django/#2014-11-23 > > I have another pull request ready for review: > https://github.com/django/django/pull/3605 > > Let me know if you have any questions! > > -- > Aymeric. > > > >> On 16 nov. 2014, at 09:19, Aymeric Augustin >> wrote: >> >> Hello, >> >> Here’s my sixth update: >> https://myks.org/en/multiple-template-engines-for-django/#2014-11-16 >> >> I have a first pull request ready for review: >> https://github.com/django/django/pull/3555 >> >> Whenever possible, I’ll merge changes that make sense regardless of the >> Multiple Template Engines Project in small batches, in order to minimize >> the size of the final pull request. >> >> -- >> Aymeric. >> >> >> >>> On 9 nov. 2014, at 22:05, Aymeric Augustin >>> wrote: >>> >>> Hello, >>> >>> Here’s my fifth update: >>> https://myks.org/en/multiple-template-engines-for-django/#2014-11-09 >>> >>> The first step of my project, as outlined in my original proposal, is >>> complete. >>> >>> -- >>> Aymeric. >>> >>> >>> On 1 nov. 2014, at 23:30, Aymeric Augustin wrote: Hello, I’m happy to annonce that the DEP is ready for public review! Direct link, HTML: https://myks.org/en/multiple-template-engines-for-django/dep/ Direct link, ReStructured Text: https://raw.githubusercontent.com/aaugustin/mtefd/master/multiple-template-engines.rst (I’m not reproducing it here because I don’t think email is a very good medium for communicating 50kB of markup.) I’ve written a bit more about what “ready” means: https://myks.org/en/multiple-template-engines-for-django/#2014-11-01 Of course, your regularly scheduled update will also be available (in half an hour): https://myks.org/en/multiple-template-engines-for-django/#2014-11-02 I’m looking forward to your feedback! -- Aymeric. > On 26 oct. 2014, at 22:36, Aymeric Augustin > wrote: > > Hello, > > I just published the third update: > https://myks.org/en/multiple-template-engines-for-django/#2014-10-26 > > -- > Aymeric. > > > >> On 19 oct. 2014, at 00:09, Aymeric A
Re: Multiple template engines for Django - week 13
On 4 janv. 2015, at 22:09, Tim Graham 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 django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. 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.
Re: Multiple template engines for Django - week 13
I don't think it's fair to put pressure on Aymeric like that. It seems to me with should, if anything, be more conservative with an LTS -- not try to cram in last minute features. We have 2-3 months until the scheduled final release -- if we liberalize our "rules", I'm sure we can kick that date out the window. My own hope (from what others have expressed interest in) is to move Django to a more rapid release cycle of 6-9 months instead of the more historical 9-12 months. I believe this feature will be all the better in 1.9 after getting a first version out the door in 1.8. On Sunday, January 4, 2015 3:51:22 AM UTC-5, Florian Apolloner wrote: > > On Sunday, January 4, 2015 2:44:52 AM UTC+1, jdunck wrote: >> >> If getting proper support for other template backends would only delay >> the 1.8 release timeline by a couple weeks, I think that is preferable to a >> generalized 1.8 backend which only include DTL until 1.9. >> > > Define proper support. Either way -1 on pushing the alpha further. > -- 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 django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. 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/3e10a35f-16cf-46c1-a832-7c9a17ac5a80%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Multiple template engines for Django - week 13
On Sunday, January 4, 2015 2:44:52 AM UTC+1, jdunck wrote: > > If getting proper support for other template backends would only delay the > 1.8 release timeline by a couple weeks, I think that is preferable to a > generalized 1.8 backend which only include DTL until 1.9. > Define proper support. Either way -1 on pushing the alpha further. -- 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 django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. 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/f7e477ad-e59a-4d19-998e-a0957a753c80%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Multiple template engines for Django - week 13
+1 to delaying the freeze to get this feature fully in place, especially since 1.8 will be an LTS release. Is there precedent to doing a freeze with an exemption for an in progress feature? If so, that is another option to an outright extension. Regards, Michael Manfre On Sat, Jan 3, 2015 at 8:44 PM, Jeremy Dunck wrote: > If getting proper support for other template backends would only delay the > 1.8 release timeline by a couple weeks, I think that is preferable to a > generalized 1.8 backend which only include DTL until 1.9. > > What do others think? > > > On Sat, Jan 3, 2015 at 3:23 PM, Aymeric Augustin < > aymeric.augus...@polytechnique.org> wrote: > >> Hello, >> >> Here’s the thirteenth update (good thing I learnt all these ordinals when >> I was a kid!) >> https://myks.org/fr/multiple-template-engines-for-django/#2015-01-04 >> >> At this point my main concern is the 1.8 feature freeze scheduled in one >> week. >> Dealing properly with some of the items I listed in my report for week 11 >> may >> require changes falling in the "new features” bucket and therefore being >> postponed to Django 1.9. At worst, I’ll have to document that some >> features >> only work with the Django template language in Django 1.8. That’s sad but >> not >> worth delaying the entire project until early 2016. >> >> -- >> Aymeric. >> >> >> >> > On 27 déc. 2014, at 23:59, Aymeric Augustin < >> aymeric.augus...@polytechnique.org> wrote: >> > >> > Hello, >> > >> > My twelfth update is online: >> > https://myks.org/en/multiple-template-engines-for-django/#2014-12-28 >> > >> > It comes with a question — should I drop `select_template` from the >> backend API? I think I should. Follow the link above for details. >> > >> > Looking forward to your feedback, >> > >> > -- >> > Aymeric. >> > >> > >> > >> >> On 20 déc. 2014, at 23:57, Aymeric Augustin < >> aymeric.augus...@polytechnique.org> wrote: >> >> >> >> Hello, >> >> >> >> I haven’t written to this mailing-list for three weeks because nothing >> warranted your immediate attention. >> >> >> >> Now the code is in reasonably good shape. Feel free to have a look: >> >> https://github.com/aaugustin/django/commits/multiple-template-engines >> >> >> >> I plan to merge this branch within a few days. >> >> >> >> Updates for weeks 9 to 11 are available at the usual location: >> >> https://github.com/aaugustin/django/commits/multiple-template-engines >> >> >> >> -- >> >> Aymeric. >> >> >> >> >> >> >> >>> On 30 nov. 2014, at 10:37, Aymeric Augustin < >> aymeric.augus...@polytechnique.org> wrote: >> >>> >> >>> Hello, >> >>> >> >>> Here’s my eight update — this is getting repetitive :-) >> >>> https://myks.org/en/multiple-template-engines-for-django/#2014-11-30 >> >>> >> >>> -- >> >>> Aymeric. >> >>> >> >>> >> >>> >> On 23 nov. 2014, at 00:02, Aymeric Augustin < >> aymeric.augus...@polytechnique.org> wrote: >> >> Hello, >> >> I published my seventh update: >> https://myks.org/en/multiple-template-engines-for-django/#2014-11-23 >> >> I have another pull request ready for review: >> https://github.com/django/django/pull/3605 >> >> Let me know if you have any questions! >> >> -- >> Aymeric. >> >> >> >> > On 16 nov. 2014, at 09:19, Aymeric Augustin < >> aymeric.augus...@polytechnique.org> wrote: >> > >> > Hello, >> > >> > Here’s my sixth update: >> > >> https://myks.org/en/multiple-template-engines-for-django/#2014-11-16 >> > >> > I have a first pull request ready for review: >> > https://github.com/django/django/pull/3555 >> > >> > Whenever possible, I’ll merge changes that make sense regardless of >> the Multiple Template Engines Project in small batches, in order to >> minimize the size of the final pull request. >> > >> > -- >> > Aymeric. >> > >> > >> > >> >> On 9 nov. 2014, at 22:05, Aymeric Augustin < >> aymeric.augus...@polytechnique.org> wrote: >> >> >> >> Hello, >> >> >> >> Here’s my fifth update: >> >> >> https://myks.org/en/multiple-template-engines-for-django/#2014-11-09 >> >> >> >> The first step of my project, as outlined in my original proposal, >> is complete. >> >> >> >> -- >> >> Aymeric. >> >> >> >> >> >> >> >>> On 1 nov. 2014, at 23:30, Aymeric Augustin < >> aymeric.augus...@polytechnique.org> wrote: >> >>> >> >>> Hello, >> >>> >> >>> I’m happy to annonce that the DEP is ready for public review! >> >>> >> >>> Direct link, HTML: >> >>> https://myks.org/en/multiple-template-engines-for-django/dep/ >> >>> >> >>> Direct link, ReStructured Text: >> >>> >> https://raw.githubusercontent.com/aaugustin/mtefd/master/multiple-template-engines.rst >> >>> >> >>> (I’m not reproducing it here because I don’t think email is a >> very good medium for communicating 50kB of markup.) >> >>> >> >>> I’ve written a bit more about what “
Re: Multiple template engines for Django - week 13
If getting proper support for other template backends would only delay the 1.8 release timeline by a couple weeks, I think that is preferable to a generalized 1.8 backend which only include DTL until 1.9. What do others think? On Sat, Jan 3, 2015 at 3:23 PM, Aymeric Augustin < aymeric.augus...@polytechnique.org> wrote: > Hello, > > Here’s the thirteenth update (good thing I learnt all these ordinals when > I was a kid!) > https://myks.org/fr/multiple-template-engines-for-django/#2015-01-04 > > At this point my main concern is the 1.8 feature freeze scheduled in one > week. > Dealing properly with some of the items I listed in my report for week 11 > may > require changes falling in the "new features” bucket and therefore being > postponed to Django 1.9. At worst, I’ll have to document that some features > only work with the Django template language in Django 1.8. That’s sad but > not > worth delaying the entire project until early 2016. > > -- > Aymeric. > > > > > On 27 déc. 2014, at 23:59, Aymeric Augustin < > aymeric.augus...@polytechnique.org> wrote: > > > > Hello, > > > > My twelfth update is online: > > https://myks.org/en/multiple-template-engines-for-django/#2014-12-28 > > > > It comes with a question — should I drop `select_template` from the > backend API? I think I should. Follow the link above for details. > > > > Looking forward to your feedback, > > > > -- > > Aymeric. > > > > > > > >> On 20 déc. 2014, at 23:57, Aymeric Augustin < > aymeric.augus...@polytechnique.org> wrote: > >> > >> Hello, > >> > >> I haven’t written to this mailing-list for three weeks because nothing > warranted your immediate attention. > >> > >> Now the code is in reasonably good shape. Feel free to have a look: > >> https://github.com/aaugustin/django/commits/multiple-template-engines > >> > >> I plan to merge this branch within a few days. > >> > >> Updates for weeks 9 to 11 are available at the usual location: > >> https://github.com/aaugustin/django/commits/multiple-template-engines > >> > >> -- > >> Aymeric. > >> > >> > >> > >>> On 30 nov. 2014, at 10:37, Aymeric Augustin < > aymeric.augus...@polytechnique.org> wrote: > >>> > >>> Hello, > >>> > >>> Here’s my eight update — this is getting repetitive :-) > >>> https://myks.org/en/multiple-template-engines-for-django/#2014-11-30 > >>> > >>> -- > >>> Aymeric. > >>> > >>> > >>> > On 23 nov. 2014, at 00:02, Aymeric Augustin < > aymeric.augus...@polytechnique.org> wrote: > > Hello, > > I published my seventh update: > https://myks.org/en/multiple-template-engines-for-django/#2014-11-23 > > I have another pull request ready for review: > https://github.com/django/django/pull/3605 > > Let me know if you have any questions! > > -- > Aymeric. > > > > > On 16 nov. 2014, at 09:19, Aymeric Augustin < > aymeric.augus...@polytechnique.org> wrote: > > > > Hello, > > > > Here’s my sixth update: > > https://myks.org/en/multiple-template-engines-for-django/#2014-11-16 > > > > I have a first pull request ready for review: > > https://github.com/django/django/pull/3555 > > > > Whenever possible, I’ll merge changes that make sense regardless of > the Multiple Template Engines Project in small batches, in order to > minimize the size of the final pull request. > > > > -- > > Aymeric. > > > > > > > >> On 9 nov. 2014, at 22:05, Aymeric Augustin < > aymeric.augus...@polytechnique.org> wrote: > >> > >> Hello, > >> > >> Here’s my fifth update: > >> > https://myks.org/en/multiple-template-engines-for-django/#2014-11-09 > >> > >> The first step of my project, as outlined in my original proposal, > is complete. > >> > >> -- > >> Aymeric. > >> > >> > >> > >>> On 1 nov. 2014, at 23:30, Aymeric Augustin < > aymeric.augus...@polytechnique.org> wrote: > >>> > >>> Hello, > >>> > >>> I’m happy to annonce that the DEP is ready for public review! > >>> > >>> Direct link, HTML: > >>> https://myks.org/en/multiple-template-engines-for-django/dep/ > >>> > >>> Direct link, ReStructured Text: > >>> > https://raw.githubusercontent.com/aaugustin/mtefd/master/multiple-template-engines.rst > >>> > >>> (I’m not reproducing it here because I don’t think email is a very > good medium for communicating 50kB of markup.) > >>> > >>> I’ve written a bit more about what “ready” means: > >>> > https://myks.org/en/multiple-template-engines-for-django/#2014-11-01 > >>> > >>> Of course, your regularly scheduled update will also be available > (in half an hour): > >>> > https://myks.org/en/multiple-template-engines-for-django/#2014-11-02 > >>> > >>> I’m looking forward to your feedback! > >>> > >>> -- > >>> Aymeric. > >>> > >>> > >>> > On 26 oct. 2014, at 22:36, Aymeric Augustin < > aymeric.augus...@polyt
Multiple template engines for Django - week 13
Hello, Here’s the thirteenth update (good thing I learnt all these ordinals when I was a kid!) https://myks.org/fr/multiple-template-engines-for-django/#2015-01-04 At this point my main concern is the 1.8 feature freeze scheduled in one week. Dealing properly with some of the items I listed in my report for week 11 may require changes falling in the "new features” bucket and therefore being postponed to Django 1.9. At worst, I’ll have to document that some features only work with the Django template language in Django 1.8. That’s sad but not worth delaying the entire project until early 2016. -- Aymeric. > On 27 déc. 2014, at 23:59, Aymeric Augustin > wrote: > > Hello, > > My twelfth update is online: > https://myks.org/en/multiple-template-engines-for-django/#2014-12-28 > > It comes with a question — should I drop `select_template` from the backend > API? I think I should. Follow the link above for details. > > Looking forward to your feedback, > > -- > Aymeric. > > > >> On 20 déc. 2014, at 23:57, Aymeric Augustin >> wrote: >> >> Hello, >> >> I haven’t written to this mailing-list for three weeks because nothing >> warranted your immediate attention. >> >> Now the code is in reasonably good shape. Feel free to have a look: >> https://github.com/aaugustin/django/commits/multiple-template-engines >> >> I plan to merge this branch within a few days. >> >> Updates for weeks 9 to 11 are available at the usual location: >> https://github.com/aaugustin/django/commits/multiple-template-engines >> >> -- >> Aymeric. >> >> >> >>> On 30 nov. 2014, at 10:37, Aymeric Augustin >>> wrote: >>> >>> Hello, >>> >>> Here’s my eight update — this is getting repetitive :-) >>> https://myks.org/en/multiple-template-engines-for-django/#2014-11-30 >>> >>> -- >>> Aymeric. >>> >>> >>> On 23 nov. 2014, at 00:02, Aymeric Augustin wrote: Hello, I published my seventh update: https://myks.org/en/multiple-template-engines-for-django/#2014-11-23 I have another pull request ready for review: https://github.com/django/django/pull/3605 Let me know if you have any questions! -- Aymeric. > On 16 nov. 2014, at 09:19, Aymeric Augustin > wrote: > > Hello, > > Here’s my sixth update: > https://myks.org/en/multiple-template-engines-for-django/#2014-11-16 > > I have a first pull request ready for review: > https://github.com/django/django/pull/3555 > > Whenever possible, I’ll merge changes that make sense regardless of the > Multiple Template Engines Project in small batches, in order to minimize > the size of the final pull request. > > -- > Aymeric. > > > >> On 9 nov. 2014, at 22:05, Aymeric Augustin >> wrote: >> >> Hello, >> >> Here’s my fifth update: >> https://myks.org/en/multiple-template-engines-for-django/#2014-11-09 >> >> The first step of my project, as outlined in my original proposal, is >> complete. >> >> -- >> Aymeric. >> >> >> >>> On 1 nov. 2014, at 23:30, Aymeric Augustin >>> wrote: >>> >>> Hello, >>> >>> I’m happy to annonce that the DEP is ready for public review! >>> >>> Direct link, HTML: >>> https://myks.org/en/multiple-template-engines-for-django/dep/ >>> >>> Direct link, ReStructured Text: >>> https://raw.githubusercontent.com/aaugustin/mtefd/master/multiple-template-engines.rst >>> >>> (I’m not reproducing it here because I don’t think email is a very good >>> medium for communicating 50kB of markup.) >>> >>> I’ve written a bit more about what “ready” means: >>> https://myks.org/en/multiple-template-engines-for-django/#2014-11-01 >>> >>> Of course, your regularly scheduled update will also be available (in >>> half an hour): >>> https://myks.org/en/multiple-template-engines-for-django/#2014-11-02 >>> >>> I’m looking forward to your feedback! >>> >>> -- >>> Aymeric. >>> >>> >>> On 26 oct. 2014, at 22:36, Aymeric Augustin wrote: Hello, I just published the third update: https://myks.org/en/multiple-template-engines-for-django/#2014-10-26 -- Aymeric. > On 19 oct. 2014, at 00:09, Aymeric Augustin > wrote: > > Hello, > > Here’s the second update: > https://myks.org/en/multiple-template-engines-for-django/#2014-10-19 > > Best, > > -- > Aymeric. > > > > On 12 oct. 2014, at 20:31, Aymeric Augustin > wrote: > >> Hello, >> >> I just posted the first update on this project: >> https://m
