Re: More input on #20945

2013-08-23 Thread charettes
Don't know if my last message made it to the mailing list, it looks like google-group might have eaten it. If it's not the case sorry for the noise. Concerning (2) I do agree with Carl it's not required to default to a specific template fragment cache alias. For the uncommon cases you want to c

password reset email template tags

2013-08-23 Thread nobody
Hi, I have customized template tags such as {{ org_name }} and {{ account_email }} which work fine for most of email template files and html files, but the tags {{ org_name }} and {{ account_email }} could not work with password reset email template. The django/contrib/auth/forms.py defined sev

Re: password reset email template tags

2013-08-23 Thread Jorge Cardoso Leitão
Hi jupiter This mailing list is for the development of Django itself. Please refer to django-users mailing list for questions about the usage of Django. Cheers, Jorge On Aug 23, 2013, at 1:33 PM, nobody wrote: > Hi, > > I have customized template tags such as {{ org_name }} and {{ account_ema

Re: Featurereuqest: Helpfull tracebacks

2013-08-23 Thread Florian Apolloner
On Friday, August 23, 2013 4:52:16 AM UTC+2, Ben Finney wrote: > > I didn't see a traceback. The OP gave only the error message. How do you > know they are getting the model name? > If he had shown his full traceback you'd see how django came to execute this query; when it reaches your code y

Custom prefetches (#17001)

2013-08-23 Thread Marc Tamlyn
Ticket #17001 concerns the ability to customise the querysets used when using `prefetch_related()`. This has a working implementation with a less than ideal API - see the patches on the ticket. As the API design seems to be the main issue here, Anssi and I bounced some ideas around on IRC, and I t

Re: Custom prefetches (#17001)

2013-08-23 Thread Andrew Ingram
I'd love to see this solved. I'm not sold on the API, but then again I've yet to see a single suggested API for this problem that I actually like. I showed you this a little while ago, you had some reservations with my idea, but I figured I might as well add it to the conversation anyway: https://

Re: Custom prefetches (#17001)

2013-08-23 Thread Anssi Kääriäinen
On Friday, August 23, 2013 6:25:42 PM UTC+3, Andrew Ingram wrote: > > I'd love to see this solved. I'm not sold on the API, but then again I've > yet to see a single suggested API for this problem that I actually like. > > I showed you this a little while ago, you had some reservations with my >

Re: Custom prefetches (#17001)

2013-08-23 Thread Andrew Ingram
Yeah, that was Marc's main issue with the idea too. Based on that distinction it makes sense to keep the two as separate concepts, but as far as API design is concerned it makes sense to try and make them feel similar. On 23 August 2013 18:25, Anssi Kääriäinen wrote: > On Friday, August 23, 201

Re: Custom prefetches (#17001)

2013-08-23 Thread Marc Tamlyn
The other restriction imposed by your suggested api is that the Count or Model list will presumably only know the standard queryset api - with a queryset= parameter any custom qs methods will work. This is perhaps more necessary in the annotate case as it is naturally a restricted api - select rel

Re: Featurereuqest: Helpfull tracebacks

2013-08-23 Thread Aymeric Augustin
As soon as Django drops support for Python 2 :) -- Aymeric. Le 22 août 2013 à 06:43, Ben Finney a écrit : > > This could be done by having Django's database interface catch the > error, and chain a new exception from that one: -- You received this message because you are subscribed to the G