Am 20.06.19 um 03:18 schrieb Curtis Maloney:
>
>> And a second question: The DJango docs say, that it's not recommended
>> to use "default_app_config". But in each and every example, even in
>> the tutorials and the Django boilerplate code of "./manage.py
>> startproject foo" are NO Appconfigs addressed in INSTALLED_APPS.
>> Nobody does this, right?
>>
>> How "obligate" is this recommendation, when noone uses it? Should
>> this be kept?
>
> I think it's most likely there as a legacy state, in order to reduce
> the burden of upgrading.
>
> I do agree it would be better if we abide by our own recommendations.

But is this really necessary?

When you look at your documentation, like the tutorial in
https://docs.djangoproject.com/en/3.0/intro/reusable-apps/ - "Quick
start" - you use

    INSTALLED_APPS = [
...
'polls',
]

It should be 'polls.apps.PollsConfig'
And to be honest - does this really make sense to urge people - writing
more code to satisfy the framework?

I tried to follow that rule in my own framework, but it's like driving
49,99 km/h in 50 speed limit on the street, when everyone else drives
55. Even Google allows it's self driving cars to drive faster than the
limit by 10% in some cases ;-)

What I mean is: Why don't you drop that recommendation - when noone is
using it - more than one AppConfigs still *are* possible, even when
there is a default.

Christian


-- 
Dr. Christian González
https://nerdocs.at

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/8ddcc796-6a5d-e680-b6bb-aaae6831b4fc%40nerdocs.at.

Attachment: pEpkey.asc
Description: application/pgp-keys

Reply via email to