[Django] #27547: Unicode in Textarea breaks rendering

[Django]

#27547: Unicode in Textarea breaks rendering
------------------------------------------+------------------------
Reporter: Nitesh Lohchab | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 1.10
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
------------------------------------------+------------------------
If you try to render unicode context in textarea, the rendering breaks
with : ascii codec can't encode unciode error

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

[Django]

#27547: Unicode in Textarea breaks rendering

--------------------------------+--------------------------------------

Reporter: Nitesh Lohchab | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 1.10

Severity: Normal | Resolution:

Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0

--------------------------------+--------------------------------------

Comment (by Nitesh Lohchab):

Changing `'<textarea{}>\r\n{}</textarea>'` to
`u'<textarea{}>\r\n{}</textarea>'` should fix this. I can send a pull
request.

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

[Django]

#27547: Unicode in Textarea breaks rendering

--------------------------------+--------------------------------------

Reporter: Nitesh Lohchab | Owner: nobody

Type: Uncategorized | Status: closed
Component: Uncategorized | Version: 1.10
Severity: Normal | Resolution: worksforme

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 Claude Paroz):

* status: new => closed
* resolution: => worksforme

Comment:

It is highly unlikely that the bug is in Django. The string you mention is
already unicode due to the `from __future__ import unicode_literals`
import at the top of `django/forms/widgets.py`.
Please use TicketClosingReasons/UseSupportChannels first to determine the
problem, and reopen the ticket if you can demonstrate that Django is at
fault.

--
Ticket URL: <https://code.djangoproject.com/ticket/27547#comment:2>