Hey Colin --
Can you open a ticket for this and put "2070-fix" in the keywords area?
Thanks,
Jacob
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to dj
Hi All,
I'm not sure if anyone has noticed this yet, but in [7814],
newforms.fields.UploadedFile.content was changed to
newforms.fields.UploadedFile.data without being listed on
BackwardsIncompatibleChanges or raising a deprecation warning. However
the [7859] change has a deprecation warning for
On Dec 11, 1:01 pm, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> I suspect is_active should be False for those users (since they
> cannot log in and that's the point of is_active). So I'd probably be +1
> for changing is_active to False on AnonymousUser.
Ok, http://code.djangoproject.com/ticke
On Sun, 2007-12-09 at 14:55 -0800, SmileyChris wrote:
> Changeset 6299 [1] added some "useful" methods and attributes to
> AnonymousUser.
>
> One of these attributes is is_active = True
>
> This is a change in functionality, because previously if you used
> (like I was) {% if user.is_active %},
Changeset 6299 [1] added some "useful" methods and attributes to
AnonymousUser.
One of these attributes is is_active = True
This is a change in functionality, because previously if you used
(like I was) {% if user.is_active %}, it would be only true for real
users who were active. Now it's true
