Mariusz makes the point on the ticket that this can cause data loss for
custom content types, which is true.
This seems to be a fairly thorny problem to me since there are several
different data loss risks. Perhaps a documentation change would be the
easiest first step - one can always remove part
>
> This seems a weird suggest, but when apps depend on another app it should
> be able to override settings for that dependency too (because it "uses"
> that app anyway).
It does seem weird to suggest. I haven't seen such a use case myself. Can
you describe in more detail?
For me, I can only im
@adam I agree with your points, about data loss, but this can still see this as
being beneficial, perhaps the approach was just too harsh. Perhaps adding a
flag in the management command would get everyone on board? The flag being off
by default and only turns on if you know what you’re doing an
Hi Christian,
Definitely not a boring theme, but as pointed by others, there are many
aspects to be taken into consideration.
Having said that, I recently stumbled on this package django-configurations
by chance, while working on something else. It looks quite promising, as
one can use (multip
Details are available on the Django project weblog:
https://www.djangoproject.com/weblog/2020/jan/02/django-bugfix-release-302/
--
You received this message because you are subscribed to the Google Groups "Django
developers (Contributions to Django itself)" group.
To unsubscribe from this grou
