Re: [GSoC] Revamping validation framework and merging django-secure once again

[Christopher Medrela]

I'm finishing making field tests green. I'm a bit late, because the schedule
says that I should finish this job by the end of the previous week. My 
excuse is
that I had exams in the previous week so I couldn't focus on GSoC. 
Fortunately,
I passed all exams and now I can work full time on GSoC and catch up. This 
week
I will finish field tests (there are still 5 red tests and documentation 
needs to
written) and I will start working on model tests.

Today I had a conversation with Russell and we decided to simplify some 
issues.
For example, `check_*` methods won't yield errors -- they will just return 
list
of errors. What's more, `check` method will call all `check_*` methods
explicitly (now it uses introspection to find all methods starting with
`check_`).

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" 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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Should Django ignore leading/trailing spaces on login credentials

[James Pic]

On Wed, Jul 3, 2013 at 7:25 PM, C. Kirby  wrote:
> I just ran into an issue where a user was copy/pasting username and password
> from a text file into the login screen. For some reason the c/p process was
> adding a trailing space to their credentials and they were failing login.
>
> Is there a reason to not scrub leading and trailing spaces from logon
> credentials
> in django.contrib.auth.forms.AuthenticationForm.clean? I guess that leading
> and trailing spaces would also have to be scrubbed when creating users as
> well


It's a frequent practice to use special characters including spaces as
prefix/suffix for passwords.

If you don't like it, you can override AuthenticationForm.

--
http://yourlabs.org
Customer is king - Le client est roi - El cliente es rey.

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" 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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Missing timezone support in built-in time template filter

[gilberto dos santos alves]

well done.

2013/7/3 Warren Smith :
> On Mon, Jul 1, 2013 at 6:18 PM, Russell Keith-Magee
>  wrote:
>>>
>>>
>>> Agreed.
>>>
>>> Also, just to clarify, I think we should stick with Django's policy of
>>> only supporting naive time objects, for the reasons you cited earlier in
>>> this thread.
>>>
>>> So, any timezone support we would add to the time filter should only
>>> support aware datetime objects, not aware time objects.
>>>
>>> Correct?
>>
>>
>> Yes - that sounds like the right approach to me.
>>
>
> Done. https://code.djangoproject.com/ticket/20693 is ready for somebody to
> review it. It would be great if this could get into 1.6.
>
> --
> Warren Smith
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers" 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.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>



-- 
gilberto dos santos alves
+55.11.98646-5049
sao paulo - sp - brasil

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" 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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Proposal: rename django-developers to django-contributors

[Michael Manfre]

Renaming a large mailing list is a non-trivial task that will result in
causing confusion for everyone subscribed to the list, instead of a the
occasional person posting to the wrong list. I cannot speak on behalf of
Django, but I think renaming the list is as likely to happen as Django 1.8
being a clean rewrite in PHP.

Regards,
Michael Manfre


On Tue, Jul 2, 2013 at 2:33 PM, Wim Feijen  wrote:

> Hi all,
>
> Many people post django-users questions to this group by accident. I find
> the name of our group to be misleading: it seems to refer to people who
> develop in django, but actually it is meant for people contributing to
> django.
>
> To limit confusion, my proposal is to rename django-developers to
> django-contributors.
>
> In addition, maybe django-users can be renamed as well, because the
> concept of a User in django is different from a django programmer.
>
> Regards,
>
> Wim
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers" 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.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" 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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Missing timezone support in built-in time template filter

[Warren Smith]

On Mon, Jul 1, 2013 at 6:18 PM, Russell Keith-Magee  wrote:

>
>>  Agreed.
>>
>> Also, just to clarify, I think we should stick with Django's policy of
>> only supporting naive time objects, for the reasons you cited earlier in
>> this thread.
>>
>> So, any timezone support we would add to the time filter should only
>> support aware datetime objects, not aware time objects.
>>
>> Correct?
>>
>
> Yes - that sounds like the right approach to me.
>
>
Done. https://code.djangoproject.com/ticket/20693 is ready for somebody to
review it. It would be great if this could get into 1.6.

-- 
Warren Smith

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" 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.
For more options, visit https://groups.google.com/groups/opt_out.

Proposal: rename django-developers to django-contributors

[Wim Feijen]

Hi all,

Many people post django-users questions to this group by accident. I find 
the name of our group to be misleading: it seems to refer to people who 
develop in django, but actually it is meant for people contributing to 
django.

To limit confusion, my proposal is to rename django-developers to 
django-contributors. 

In addition, maybe django-users can be renamed as well, because the concept 
of a User in django is different from a django programmer.

Regards,

Wim

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" 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.
For more options, visit https://groups.google.com/groups/opt_out.