在执行数据库迁移的时候报出错误RuntimeError: populate() isn't reentrant,以前也出过这个错误,可是忘记记录了,此次又出现了。百度搜好好多,都没解决个人问题,这里作个踩坑记录。python
背景:项目有多个app,如今新需求增长了一个app,并编写了该app的utils文件数据库
在执行python manage.py makemigrations后报出以下异常django
Traceback (most recent call last): File "manage.py", line 14, in <module> execute_from_command_line(sys.argv) File "D:\Program Files\Python37\lib\site-packages\django\core\management\__init__.py", line 381, in execute_from_command_line utility.execute() File "D:\Program Files\Python37\lib\site-packages\django\core\management\__init__.py", line 357, in execute django.setup() File "D:\Program Files\Python37\lib\site-packages\django\__init__.py", line 24, in setup apps.populate(settings.INSTALLED_APPS) File "D:\Program Files\Python37\lib\site-packages\django\apps\registry.py", line 81, in populate raise RuntimeError("populate() isn't reentrant") RuntimeError: populate() isn't reentrant
跟着错误信息,初步断定是新建立的app才引起的此问题,因此就把INSTALLED_APPS中新建立的app注释掉,再执行python manage.py makemigrations就不报异常了。app
因此错误信息应当在新app中,在检查到utils文件时,发现引入包的方式有问题code
文件目录为blog
未修改时引入方式为it
修改后方式为io
就是在引入TLSSigAPI模块时加上app的名称ast
总结:在新建app并初始化后,若是提示RuntimeError: populate() isn't reentrant错误,应该先检查每一个app的模块引入状况。class