2👍
✅
This was a Django bug introduced in Django 1.11:
https://code.djangoproject.com/ticket/28174
This is now fixed in Django 1.11.4, so upgrading to the latest Django should solve this. However, I’d strongly recommend upgrading to Python 3 (which will also avoid this issue) – Python 2.7 is very much end-of-line now, and support for it will be dropped in Django 2.0 (due at the end of this year).
Source:stackexchange.com