When this problem occurs, please check the python version and django version used.
The emergence of this problem is a bug that django3.0 and python3.7.0 use together.
The python upgrade (in python3.7.1 version this issue has been resolved) or django downgrade (django2.2 / 2.1 can work).
At this point, the problem is solved perfectly.