Hi,
I'm working on porting a large codebase to 1.4 (using the rc), and have run
into what appears to be a regression in the serializers. I wanted to run it
past some eyes here before I raise a ticket.
The Python serializer's handle_fk_field() method now no longer handles the case
where a relat
On 12.03.2012, at 08:19, Dan Fairs wrote:
> Hi,
>
> I'm working on porting a large codebase to 1.4 (using the rc), and have run
> into what appears to be a regression in the serializers. I wanted to run it
> past some eyes here before I raise a ticket.
>
> The Python serializer's handle_fk_fi
Is this bug fix too late for the upcoming release?
https://code.djangoproject.com/ticket/15644
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/django-developers/-/JG
On Thursday, February 23, 2012 10:41:36 AM UTC-5, Tom Evans wrote:
I don't like this function that much.
>
I share that sentiment. When it becomes possible to refactor auth.User, I
hope we'll be able to first deprecate and then remove
User.is_authenticated() and User.is_anonymous(). In addition
On March 12, 2012, at 14:47 , Clay McClure wrote:
> On Thursday, February 23, 2012 10:41:36 AM UTC-5, Tom Evans wrote:
> there is also the possible source of confusion stemming from the fact that
> in template language we write:
>
> {% if user.is_authenticated %}
>
> but in Python we writ
