Hi,
I'd like to bring up #18133 again, which has been closed as wontfix.
I am looking for an easy and non-intrusive way to override the default
colon suffix on form field labels. The suggested methods of subclassing
the affected Form classes leads to quite a bit of code churn. I am using
Forms an
Hi Russell,
On Wed, 2014-02-26 at 15:33 +0800, Russell Keith-Magee wrote:
> The idea here is that we just ship a normal auth.User, but with email
> identification rather than username.
I have just implemented an email based User model as well, and was
wondering about case sensitivity in the loca
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
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
Hi Saurabh,
On Wed, 2014-03-19 at 13:12 -0700, Saurabh Wahile wrote:
> The Plan:
> I intend to build a library that can help to resolve this issue by
> using Django's existing model architecture and extending the foreign
> key relationships to be redirected onto the NoSQL solution.
>
>
> I woul
