[Django] #30225: Unicode characters in `migrate` command output

3 views
Skip to first unread message

Django

unread,
Feb 28, 2019, 9:58:51 AM2/28/19
to django-...@googlegroups.com
#30225: Unicode characters in `migrate` command output
-------------------------------------+-------------------------------------
Reporter: Vaibhav | Owner: nobody
Vishal |
Type: | Status: new
Cleanup/optimization |
Component: | Version: 2.2
Migrations |
Severity: Normal | Keywords: migration, migrate
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
When running `py manage.py migrate` it outputs some unicode characters to
the terminal. It is new in 2.2, it was not an issue in 2.1.7
Since There is a unicode character when I deploy the project on AWS
Elastic Beanstalk, the migration command fails because it cannot decode
the unicode character, please suggest a workaround to avoid this or use
ascii characters only to avoid such errors. I have attached the relevant
parts of logs of deployment for both 2.1.7(success) and 2.2(fail) to the
ticket.

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

Django

unread,
Feb 28, 2019, 9:59:49 AM2/28/19
to django-...@googlegroups.com
#30225: Unicode characters in `migrate` command output
-------------------------------------+-------------------------------------
Reporter: Vaibhav Vishal | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Migrations | Version: 2.2
Severity: Normal | Resolution:

Keywords: migration, migrate | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0

Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Vaibhav Vishal):

* Attachment "2.1.7.log" added.

Deployment log when using Django==2.1.7, which is successful.

Django

unread,
Feb 28, 2019, 10:00:33 AM2/28/19
to django-...@googlegroups.com
#30225: Unicode characters in `migrate` command output
-------------------------------------+-------------------------------------
Reporter: Vaibhav Vishal | Owner: nobody
Type: | Status: new
Cleanup/optimization |

Component: Migrations | Version: 2.2
Severity: Normal | Resolution:
Keywords: migration, migrate | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0

Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Vaibhav Vishal):

* Attachment "2.2.log" added.

Deployment log when using Django==2.2, which failed.

Django

unread,
Feb 28, 2019, 10:02:38 AM2/28/19
to django-...@googlegroups.com
#30225: Unicode characters in `migrate` command output making deployment fail

-------------------------------------+-------------------------------------
Reporter: Vaibhav Vishal | Owner: nobody
Type: | Status: new
Cleanup/optimization |

Component: Migrations | Version: 2.2
Severity: Normal | Resolution:
Keywords: migration, migrate | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0

Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

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

Django

unread,
Feb 28, 2019, 10:06:27 AM2/28/19
to django-...@googlegroups.com
#30225: Unicode characters in `migrate` command output making deployment fail
-------------------------------------+-------------------------------------
Reporter: Vaibhav Vishal | Owner: nobody
Type: | Status: closed

Cleanup/optimization |
Component: Migrations | Version: 2.2
Severity: Normal | Resolution: duplicate

Keywords: migration, migrate | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0

Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette):

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


Comment:

Duplicate of #30184 fixed in 5e94c817ee26a13e141a11a2f429f9ee2cc37ab0
which should be part of the upcoming 2.2 release.

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

Django

unread,
Feb 28, 2019, 10:11:10 AM2/28/19
to django-...@googlegroups.com
#30225: Unicode characters in `migrate` command output making deployment fail
-------------------------------------+-------------------------------------
Reporter: Vaibhav Vishal | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Migrations | Version: 2.2
Severity: Normal | Resolution: duplicate
Keywords: migration, migrate | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0

Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Comment (by Carlton Gibson):

Also though, a quick Google leads to this AWS page suggesting you can set
a decent locale in your application to fix this properly.

https://forums.aws.amazon.com/thread.jspa?threadID=221739

--
Ticket URL: <https://code.djangoproject.com/ticket/30225#comment:3>

Django

unread,
Mar 1, 2019, 12:30:21 AM3/1/19
to django-...@googlegroups.com
#30225: Unicode characters in `migrate` command output making deployment fail
-------------------------------------+-------------------------------------
Reporter: Vaibhav Vishal | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Migrations | Version: 2.2
Severity: Normal | Resolution: duplicate
Keywords: migration, migrate | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0

Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Comment (by Vaibhav Vishal):

Thanks for the aws forums link. It solved my problem. I did searched on
google for the problem but couldn't find anything, sorry for creating a
ticket.

--
Ticket URL: <https://code.djangoproject.com/ticket/30225#comment:4>

Reply all
Reply to author
Forward
0 new messages