#29443: Unify registries in Django
-------------------------------------+-------------------------------------
     Reporter:  Johannes Hoppe       |                    Owner:  nobody
         Type:                       |                   Status:  new
  Cleanup/optimization               |
    Component:  Utilities            |                  Version:  master
     Severity:  Normal               |               Resolution:
     Keywords:  plugin, registry,    |             Triage Stage:  Accepted
  pattern, utils                     |
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by Johannes Hoppe):

 Hi Florian,

 thanks for bringing this up. I didn't check 3rd party.

 IMHO this particular implementation does too much. I goes way beyond a
 simple registry. Replacing the existing code will be more difficult and
 could introduce unwanted bug.

 What concerns me more is adding a dependency.

 If you prefer using this package, I am happy to run it by the mailing
 list. I personally would avoid to use it.

 Best
 -Joe

-- 
Ticket URL: <https://code.djangoproject.com/ticket/29443#comment:7>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.565d106ee61fb4cc3ec5dabf33587269%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to