Cause noone reads docs and this is not really deployment related imo.
What if the checks framework warned it?
--
unai
--
You received this message because you are subscribed to the Google Groups "Django
developers (Contributions to Django itself)" group.
To unsubscribe from this
[…]
I don't think there's a risk of users overlooking the feature if we add
a check to the checks framework.
--
unai
--
You received this message because you are subscribed to the Google Groups "Django
developers (Contributions to Django itself)" group.
To unsubscribe f
feature on the security checklist, with the
rest of deployment-related features that aren't on by default?
Don't take me wrong, I *do* think this is a great feature, but it should
be the developers choice to turn it on.
--
unai
--
You received this message because you are subscr
adds just more overhead (which Django surely
doesn't need).
--
unai
--
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,
om/group/django-developers.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/CACiOJ6uz5f42vSQ_5A%2BU_GyUHSPuNrO6vWahGpzdbSH9cusFiQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
--
unai
--
You received this message because
ult one could be used. But you are right when you say that
it can be even more magical than handling the case where the auth
backends setting has length one.
But, if possible, I'm in favour of following a deprecation path and
requiring the backend argument to be mandatory.
--
unai
not Django's default one. By defaulting to the
backend defined in settings if there is only one present we are
introducing a bit more of magic.
--
unai
--
You received this message because you are subscribed to the Google Groups "Django
developers (Contributions to Django itsel
d which is not present in your
settings) they would get an error.
--
unai
--
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
Hi Paulo!
If the application has only one backend we always infer it in the login
function. If it isn't, the client needs to provide one explicitly.
Why not pass the single auth backend into the login function? It makes
the design and the documentation much simpler.
--
unai
-
se a couple
of years ago when I discovered it didn't work.
--
unai
--
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,
g but the same exact behaviour can be achieved by:
{% block myblock %}
{% if myvariable %}
my content
{% else %}
{{ block.super }}
{% endif %}
{% endblock myblock %}
--
unai
--
You received this message because you are subscribed to the Google Groups "Django
ons 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 vi
" and
"Submissive", "Dom" and "Sub" or "Top" and "Bottom"?
--
unai
signature.asc
Description: Digital signature
Hi there!
> In fact, it allows arbitrary nesting and combinations. It works by
> keeping a list of possible sources for each template and as template
> is rendered it removes it from the list, so that next time it is not
> loaded anymore.
I'm not entirely convinced about maintaining a dicts of li
c, suggestion or idea is highly appreciated ;-)
I'm going to be able to put some more effort into this tomorrow.
Best regards,
Unai Zalakain
signature.asc
Description: PGP signature
extend. The negative one, that it is just a lot more of code on the template
layer and that it would (IMO) overcomplicate things.
My two cents! I'll work on the self-referencing code today and tomorrow.
Best regards,
Unai Zalakain
signature.asc
Description: PGP signature
ent path will be found and returned by the app loader, concluding the
``find_template`` loop.
Cheers!
Unai Zalakain
signature.asc
Description: PGP signature
x27;t think the overuse of this feature (A --> B --> C --> D)
would be recommendable but I couldn't imagine anyone doing that.
Sorry for keep you waiting, busy week :-/
Best wishes,
Unai Zalakain
signature.asc
Description: PGP signature
pt a
``skip_template`` parameter in ``find_template``, ``select_template`` and
``render_to_template`` funcs and pass that parameter on to the loaders.
Thanks for your concern!
Best wishes,
Unai Zalakain
signature.asc
Description: PGP signature
any problems that this solution would arise don't hesitate
in telling ;)
Best wishes,
Unai Zalakain
signature.asc
Description: PGP signature
re already giving some thought to this
idea.
We are aware that this is not a small change in the template engine so reviews
and suggestions are highly appreciated. The pull request can be found at:
https://github.com/django/django/pull/2042
Greetings,
Unai Zalakain
References
--
its; With the first, I'll need to fix
> both the receivers and the signal-sending code, which may be out of
> my control.
Patch on its way then!
--
unai
signature.asc
Description: PGP signature
I go with the second one?
Yours sincerely,
Unai
signature.asc
Description: PGP signature
23 matches
Mail list logo
