Re: Stop QuerySet repr from executing queries

Yes, it's a complicated issue, but isn't the SQL query the ultimate representation of which methods are called or not? Having the query evaluated during debugging has been shown to be harmful in certain situations, isn't that the most important thing to fix? -- You received this message becaus

Re: How can I join to django translations on transifex

Thank you for your response Claude. I just wrote to that group and I am waiting for their response, Soyuzbek On Tue, Oct 15, 2019 at 9:09 PM Claude Paroz wrote: > Hi, > > There is a specific group dedicated to translation issues: > django-i...@googlegroups.com > Please write to that group. > > C

Re: How can I join to django translations on transifex

Hi, There is a specific group dedicated to translation issues: django-i...@googlegroups.com Please write to that group. Claude Le mardi 15 octobre 2019 13:40:38 UTC+2, Soyuzbek orozbek uulu a écrit : > > Hi all, > I want to translate Django to Kyrghyz language using transifex. I already > sent

Re: Stop QuerySet repr from executing queries

I agree with what James eloquently said, the issue is more complicated it appears. Simon Le mardi 15 octobre 2019 05:59:27 UTC-4, James Bennett a écrit : > > This request is a bit more complicated than I think people > realize. There's no practical way I can see to have the __repr__() of > a Que

How can I join to django translations on transifex

Hi all, I want to translate Django to Kyrghyz language using transifex. I already sent a request but I didn't get any response. Can you help me with it? -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To u

Re: Stop QuerySet repr from executing queries

This request is a bit more complicated than I think people realize. There's no practical way I can see to have the __repr__() of a QuerySet supply information sufficient to reconstruct it, at least not in a manner recognizable to most users of the ORM (there's no internal record of which query meth

Re: Stop QuerySet repr from executing queries

Current behavior is indeed usually useful but I actually remember being annoyed by it during interactive debugging - as watches affect sql log. What about reusing DEBUG instead of introducing brand new setting? I imagine all tutorials are in the context of scaffolded project with DEBUG=True a

Re: Stop QuerySet repr from executing queries

I'd be -1 on the change here too. That QuerySet shows you its value in the shell is beyond valuable. Look at the Django Tutorial , or the Django Girl Tutorial , or a

Re: Stop QuerySet repr from executing queries

Hi y'all, I closed the original ticket because two responses is not enough to reopen it. I'm -1 to this change. IMO your issue is really niche and it's caused by multiple reasons, i.e. huge table, Meta.ordering by non-indexed column, uncaught exception, error reporting layer that calls `rep