Re: Proposal: make Model __unicode__() default to self.name

On 11 juil. 2013, at 05:46, cmawebs...@gmail.com wrote: > What do your __unicode__/__str__ methods look like? Is this a bad idea? In addition to the previous answers, I find it important to have an unambiguous __unicode__ / __str__, and name isn't necessarily unique. -- Aymeric. -- You

Re: Django 1.5.2

Thanks Jacob! Greatly appreciated :) Le mardi 9 juillet 2013 19:04:26 UTC-4, Jacob Kaplan-Moss a écrit : > > Hey Michael - > > We don't have a schedule for 1.5.2 at the moment, but I'll take a look and > see if I can get a release out sometime soon. No promises, but I'll do my > best. > > Jacob

Explaining application instances

There are a couple of places in the documentation that refer to "application instances": However, it's not really clear what

Re: Explaining application instances

On Thu, Jul 11, 2013 at 3:57 PM, Daniele Procida wrote: > There are a couple of places in the documentation that refer to > "application instances": > > > < >

Re: Explaining application instances

On Thu, Jul 11, 2013, Russell Keith-Magee wrote: >On Thu, Jul 11, 2013 at 3:57 PM, Daniele Procida wrote: >> I still don't quite see why one might want to run an additional instance >> of an application. If it's just to provide a different set of URLs

Re: Proposal: make Model __unicode__() default to self.name

> In addition to the previous answers, I find it important to have an unambiguous __unicode__ / __str__, and name isn't necessarily unique. Perhaps to have it a tiny little bit more useful, have it default to "MyModel object (object_pk)" ? mjl -- You received this message because

Re: Proposal: make Model __unicode__() default to self.name

2013/7/11 mjl Martin J. Laubach > Perhaps to have it a tiny little bit more useful, have it default to > "MyModel object (object_pk)" ? > I could support that. object_pk will be None when the object isn't saved yet, but that's fine. -- Aymeric. -- You received this

Confusion around generic views queryset cloning.

I've noted that the generic view implementations use the private `_clone` method when returning the queryset attribute . Presumably the need for that is something to do with the potential for querysets to be

Re: Confusion around generic views queryset cloning.

Hi Tom, (You said in a follow-up this was intended for django-users, but personally I think it's on-topic for -developers, so I'm replying here.) On 07/11/2013 02:54 PM, Tom Christie wrote: > I've noted that the generic view implementations use the private > `_clone` method when returning the