#36771: Django needs a _massive_ refactor
-------------------------------------+-------------------------------------
Reporter: cammil | Owner: (none)
Type: | Status: closed
Cleanup/optimization |
Component: Uncategorized | Version: 6.0
Severity: Normal | Resolution: invalid
Keywords: refactor | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Jake Howard):
* resolution: => invalid
* status: new => closed
Comment:
As you can imagine, a ticket like this is incredibly hard (basically
impossible) to action. If you have any concrete suggestions other than
rewrite all of Django from scratch, the new-features repo
https://github.com/django/new-features is the best way to go.
A project the size and scale of Django needs to move slowly so it doesn't
harm its users. But as can be seen by the new features in each release, it
_is_ improving, adapting, changing and "upgrading" - hopefully for the
better.
--
Ticket URL: <https://code.djangoproject.com/ticket/36771#comment:1>
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/0107019ae8a7b499-1df8c9ae-1bc7-43b7-8eef-b933ca1a6f51-000000%40eu-central-1.amazonses.com.
