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:
>
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
>
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
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
+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
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 <
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