Django's django.core.urlresolvers.reverse() seems to have changed its
behavior in 1.6. It now runs the arguments through quote(), without
specifying the safe characters for path components. As a result:
on 1.4.10:
In [2]: reverse('test', args=['foo:bar'])
Out[2]: '/foo:bar'
but on 1.6.2:
In [2]
The following may be a viable solution for the case-insensitive fields.
(email, username, alias ... etc.)
Look at lines: 23, 66 and 159.
https://gist.github.com/un33k/9273782
Val
On Fri, Feb 28, 2014 at 5:05 AM, Tilman Koschnick wrote:
> On Thu, 2014-02-27 at 08:43 +0800, Russell Keith-Mag
On Thu, 2014-02-27 at 08:43 +0800, Russell Keith-Magee wrote:
> It does - assuming you use User.objects.create_user() to create all
> your users. However, the UserCreationForm doesn't use this (and hasn't
> ever used this); it also doesn't account for fixtures, or any other
> path into the databas
On Thu, 2014-02-27 at 20:11 -0800, schinckel wrote:
> But there's the rub. Whilst for _most_ email servers, this will indeed
> send mail to the same account, there's nowhere that says this _must_
> happen.
I agree. Reading RFC 822, it says
The domain-dependent
string is
