-1
If a person brute forces your site and finds the correct username /
password they could try this on other sites (gmail, banking, etc..)
While it would make it a little more clear I think the implications
are too big.
On Sep 13, 3:14 pm, Adam Jenkins wrote:
> On Tue, Sep 13, 2011 at 12:42 PM,
+1 for {% include "foo.html" x=1 y=2 %}
This just seems more natural. My designer agreed based on the {% url
%} tags.
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
Wouldn't it be better to just have an email authentication backend.
I feel that its unnecessary to duplicate information. The username is
there for a reason as well as the email. Maybe the solution is to
ship django with both an email and a username authentication and make
the other field optiona
