normalize_email will indeed allow both u...@example.com and
u...@example.com to be different entities. From the user perspective, this
is an error. Most probably the user enters some day their email in all
upper case because he pressed the CapsLock key, or copy pasted a transcript
of his email,
>
> - Then, we can create dummy implementations of `render_to_response` (and
> all
>other functions) that checks the template extension and dispatch to
>corresponding function from `django.dtl` or `jinja2`.
>
Hello,
Could this create a little problem for the people in charge of the tem
On Thursday, February 20, 2014 2:42:07 PM UTC-4:30, Devashish Badlani wrote:
>
> I am into my last year of graduation and I am currently an intern in Khan
> Academy ,Foundation for Learning Equality from IIT Bombay .I have been
> developing working with Django for the same
>
> *Title*: Building b
