#35869: Add explicit warning when AppConfig.create() can't choose from multiple
subclasses of AppConfig
--------------------------------------+------------------------------------
     Reporter:  schnee                |                    Owner:  schnee
         Type:  Cleanup/optimization  |                   Status:  closed
    Component:  Core (Other)          |                  Version:  5.0
     Severity:  Normal                |               Resolution:  wontfix
     Keywords:  AppConfig             |             Triage Stage:  Accepted
    Has patch:  1                     |      Needs documentation:  0
  Needs tests:  0                     |  Patch needs improvement:  0
Easy pickings:  0                     |                    UI/UX:  0
--------------------------------------+------------------------------------
Changes (by Sarah Boyce):

 * resolution:   => wontfix
 * status:  assigned => closed

Comment:

 In reviewing the patch, I saw that there was a similar deprecation warning
 which has been removed as we are out of the depreciation period, see
 
https://github.com/django/django/commit/e5fce539bcd7d5cf73cf79aa068cb42aab39a726
 #diff-
 0f8bc657bc27c9f80385c4814c2c2ebc033bda3e03285a7212965309a481cc70R163-R170

 As you experienced this updating from 3.2 to 4.2, this
 [https://docs.djangoproject.com/en/5.1/howto/upgrade-version/#resolving-
 deprecation-warnings warning would have been available], the question is
 now whether we should have a permanent warning or whether this was only a
 case for upgrading between versions

 If you think a warning is still valuable, you need to start a discussion
 on the [https://forum.djangoproject.com/c/internals/5 Django forum] and
 get community agreement that this is needed.
 I will close the ticket for now as wontfix this can be reopened if the
 community agrees this is needed
-- 
Ticket URL: <https://code.djangoproject.com/ticket/35869#comment:5>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion visit 
https://groups.google.com/d/msgid/django-updates/01070192f6a81e95-44c0c12f-0f52-4dcf-86ac-eec5c681a33b-000000%40eu-central-1.amazonses.com.

Reply via email to