Re: Multiple template engines for Django - week 1

2014-11-04 Thread Preston Timmons 
Hi Aymeric,

With the new template update, do you foresee 
django.utils.setup_test_template_loader and 
django.utils.restore_template_loaders still working?

Those aren't officially public api's, but they're useful nonetheless. 
Perhaps the way to do it in the future would be with override_settings and 
a dict loader?

Preston

-- 
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/837097fd-7d90-486d-a85f-7161232766fd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Multiple template engines for Django - week 1

2014-10-17 Thread Aymeric Augustin 
Hi Anssi,

On 17 oct. 2014, at 14:49, Anssi Kääriäinen  wrote:

> The FAQ section says that template context processors isn't going to be
> supported for context processors.

Indeed, at this time, my theoretical position is not to enforce such an API
and leave it up to template engines.

But I may settle for a pragmatic position if this results in every template
engine copy-pasting 50 lines of code to provide that feature.

As shown by the `render` shortcut, APIs in this area must be pragmatic,
even if that requires some compromise with the general design.

> The context processors return a dictionary to be added to the context,
> so there is nothing template language specific in this definition.

It's implemented in RequestContext which used to be called DjangoContext
until magic-removal (2006) and lives in django.template.context. That's why
I considered it part of the Django template language itself.

> What is the rationale of dropping context processors out of the
> proposal? It seems supplying different template engines with different
> data isn't going to work well for any project in which one wants to
> replace DTL templates.

Yes, providing all templates with a common set of request-specific values
is a useful feature. It was on my todo list :-)

-- 
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/18EED14B-40E2-4107-9C72-EDB0C47C800F%40polytechnique.org.
For more options, visit https://groups.google.com/d/optout.

Re: Multiple template engines for Django - week 1

2014-10-17 Thread Anssi Kääriäinen 
On Sun, 2014-10-12 at 20:31 +0200, Aymeric Augustin wrote:
> Feedback is welcome, especially on sections I've described as "done" in the 
> update.

The FAQ section says that template context processors isn't going to be
supported for context processors.

The context processors return a dictionary to be added to the context,
so there is nothing template language specific in this definition.

What is the rationale of dropping context processors out of the
proposal? It seems supplying different template engines with different
data isn't going to work well for any project in which one wants to
replace DTL templates.

 - Anssi

-- 
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/1413550163.21107.146.camel%40TTY32.
For more options, visit https://groups.google.com/d/optout.

Re: Multiple template engines for Django - week 1

2014-10-12 Thread Fred Stluka 

Excellent!  Thanks for the update.  I donated to the IndieGoGo
campaign.

--Fred

Fred Stluka -- mailto:f...@bristle.com -- http://bristle.com/~fred/
Bristle Software, Inc -- http://bristle.com -- Glad to be of service!
Open Source: Without walls and fences, we need no Windows or Gates.


On 10/12/14 2:31 PM, Aymeric Augustin wrote:

Hello,

I just posted the first update on this project:
https://myks.org/en/multiple-template-engines-for-django/#2014-10-12

My work in progress on the DEP is available here:
https://myks.org/en/multiple-template-engines-for-django/dep/

Feedback is welcome, especially on sections I've described as "done" in the 
update.

Thanks,



--
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/543AFE2D.5050304%40bristle.com.
For more options, visit https://groups.google.com/d/optout.

Multiple template engines for Django - week 1

2014-10-12 Thread Aymeric Augustin 
Hello,

I just posted the first update on this project:
https://myks.org/en/multiple-template-engines-for-django/#2014-10-12

My work in progress on the DEP is available here:
https://myks.org/en/multiple-template-engines-for-django/dep/

Feedback is welcome, especially on sections I've described as "done" in the 
update.

Thanks,

-- 
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/F839214C-972F-42BF-ABC0-4CAA07B301B3%40polytechnique.org.
For more options, visit https://groups.google.com/d/optout.