mirror of
https://github.com/jazzband/django-admin2.git
synced 2026-03-16 22:20:24 +00:00
26 lines
No EOL
1.4 KiB
ReStructuredText
26 lines
No EOL
1.4 KiB
ReStructuredText
Frequently Asked Questions
|
|
===========================
|
|
|
|
Is this intended to go into Django contrib?
|
|
----------------------------------------------
|
|
|
|
No.
|
|
|
|
Reasons why it was never intended to go into Django core and why it won't be going into Django core:
|
|
|
|
1. We want to rely on external dependencies
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
We think certain packages can do a lot of the heavy lifting for us, and rewriting them is more time taken away from fixing bugs and implementing features. Since the Django core team isn't likely to accept external dependencies, especially ones that rely on Django itself, this alone is reason enough for django-admin2 to never make it into Django contrib.
|
|
|
|
2. We want increased Speed of Development
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
Django is a huge project with a lot of people relying on it. The conservative pace at which any change or enhancement is accepted is usually boon to the community of developers who work with it. Also, the committee-based management system means everyone gets a voice. This means things often happen at a slow and steady pace.
|
|
|
|
However, there are times when it's good to be outside of core, especially for experimental replacements for core functionality. Working outside of Django core means we can do what we want, when we want it.
|
|
|
|
What's wrong with django.contrib.admin?
|
|
-----------------------------------------
|
|
|
|
Forthcoming... |