Re: Confusion around generic views queryset cloning.

2013-07-11 Thread Carl Meyer
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 que

Re: Confusion around generic views queryset cloning.

2013-07-11 Thread Tom Christie
My apologies, this was intended to be posted to the Django users group. On Thursday, 11 July 2013 21:54:25 UTC+1, Tom Christie wrote: > > I've noted that the generic view implementations use the private `_clone` > method when returning the queryset > attribute

Confusion around generic views queryset cloning.

2013-07-11 Thread Tom Christie
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 cached

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

2013-07-11 Thread Shai Berger
On Thursday 11 July 2013 17:57:34 Aymeric Augustin wrote: > 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

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

2013-07-11 Thread Aymeric Augustin
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 message because you are s

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

2013-07-11 Thread mjl Martin J. Laubach
> 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 y

Re: Explaining application instances

2013-07-11 Thread Daniele Procida
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 for it, >> why not write some additional UR

Re: Explaining application instances

2013-07-11 Thread Russell Keith-Magee
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": > > > < > https://docs.djangoproject.com/en/dev/ref/contrib/admin/#multiple-a

Explaining application instances

2013-07-11 Thread Daniele Procida
There are a couple of places in the documentation that refer to "application instances": However, it's not really clear what