Triaged
---
https://code.djangoproject.com/ticket/26488 - migrate raises
InvalidBasesError if you rename a multitable inheritance base model
(accepted)
https://code.djangoproject.com/ticket/26491 - Duplicated queries with
nested prefetch (duplicate)
https://code.djangoproject.com/ticke
Claude proposed a PR which simply adds the setting as an AppConfig
attribute: https://github.com/django/django/pull/6460
Feedback would be welcome as to whether this seems sufficient or if we need
something more complex. I imagine this pattern will become fairly common if
we decide to move in t
On Saturday, April 16, 2016 at 4:06:04 AM UTC+2, brigh...@gmail.com wrote:
>
> JsonpResponse isn't needed for most use cases. But is needed for some use
> cases.
>
Like which? I think this should better live outside of Django.
--
You received this message because you are subscribed to the Goo
Hi everybody,
Tim pointed me to this discussion here and I support the overall goal. It
accelerates development, especially when designing somewhat prettier Web
pages. Quoting my quite naive approach from the issue tracker
(https://code.djangoproject.com/ticket/26507#comment:2):
"""
I don't kn