#32794: Get rid of boolean traps in Engine
-------------------------------------+-------------------------------------
Reporter: Abhyudai | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Template system | Version: 3.2
Severity: Normal | Resolution: wontfix
Keywords: template, engine | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* type: Uncategorized => Cleanup/optimization
* resolution: => wontfix
Comment:
There are dozens of methods and functions which accept boolean positional
arguments in Django. It's not worth the additional complexity and backward
compatibility concerns to change them. Moreover users do not initialize
`Engine()` themself in most of cases.
By the way, you'll reach a wider audience if you write to the
DevelopersMailingList about your ideas.
--
Ticket URL: <https://code.djangoproject.com/ticket/32794#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 on the web visit
https://groups.google.com/d/msgid/django-updates/068.f9643bc509975b35f0b35b4f2a1e55b5%40djangoproject.com.
