#4380: Rename DEFAULT_CHARSET to OUTPUT_CHARSET (or similar)
-------------------------------------+--------------------------------------
Reporter: Simon Willison | Owner: ctrochalakis
Status: closed | Milestone:
Component: Core framework | Version: SVN
Resolution: wontfix | Keywords:
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-------------------------------------+--------------------------------------
Changes (by mtredinnick):
* status: new => closed
* resolution: => wontfix
Comment:
Not worth it now. We're going to have to support `DEFAULT_CHARSET` for a
long time now that 1.0 is coming out and it doesn't seem to be causing a
lot of confusion to people. Yes, I probably should have just fixed this
when it was first raised, but I didn't. Sorry, but can't go back in time
(time machine is only for bug fixes, not a cure for sloth).
--
Ticket URL: <http://code.djangoproject.com/ticket/4380#comment:11>
Django Code <http://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 post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---