[Django] #24610: Deprecate html-related stuff

4 views
Skip to first unread message

Django

unread,
Apr 8, 2015, 5:58:14 PM4/8/15
to django-...@googlegroups.com
#24610: Deprecate html-related stuff
-------------------------------+--------------------
Reporter: marcinn | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------
There are many problems with creating something else than one-page-html-
doc using Django. Please remove any html related stuff from framework,
because Django is not a html framework but web framework (as mentioned in
description of #18054), and "web" term is not reserved for HTML only.

* `django.forms` should be removed or HTML-based widgets should be
cutted-off; forms should validate and clean data only
* technical error responses (404 and 500) should return responses
dependent on `Accept` header value; there are many issues with debugging
web services by digging HTML/JS/CSS output in shell/terminal
* remove html from `django.utils.log`
* remove html from `django.utils.timesince`
* if I forgot something - remove it too

--
Ticket URL: <https://code.djangoproject.com/ticket/24610>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

Django

unread,
Apr 8, 2015, 6:04:20 PM4/8/15
to django-...@googlegroups.com
#24610: Deprecate html-related stuff
-------------------------------+--------------------------------------
Reporter: marcinn | Owner: nobody
Type: Uncategorized | Status: closed
Component: Uncategorized | Version: master
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0

Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Changes (by timgraham):

* status: new => closed
* needs_docs: => 0
* resolution: => needsinfo
* needs_tests: => 0
* needs_better_patch: => 0


Comment:

Thanks for the raising the issue, however, one monolithic ticket to
address this doesn't seem the right approach to me. If you could open some
smaller, actionable tickets focused on specific use cases where output
needs to be customizable that would be better. I doubt we can simply
deprecate or remove HTML in all of the areas your raise, but we could
certainly have hooks to customize the output as needed.

--
Ticket URL: <https://code.djangoproject.com/ticket/24610#comment:1>

Reply all
Reply to author
Forward
0 new messages