[英]Django killed suddenly after runserver on M1
I have couple of project on Django and after hi runserver terminal shows:我在 Django 上有几个项目,在 hi runserver 终端显示之后:
[1] 23857 killed python3 manage.py runserver
I had update all library for working on Apple M1 and everything was good.我已经更新了所有在 Apple M1 上工作的库,一切都很好。 after couple of day I tried to run and everything is crushed.
几天后,我试图跑步,一切都被粉碎了。 my requirments.txt is:
我的 requests.txt 是:
boto3==1.15.6
botocore==1.18.6
Django==3.1.1
django-cors-headers==3.5.0
django-debug-toolbar==3.1.1
django-storages==1.10.1
django-summernote==0.8.11.6
docutils==0.16
gunicorn==20.0.4
jmespath==0.10.0
Pillow==8.1.0
pipupgrade==1.7.4
psycopg2-binary==2.8.6
python-dateutil==2.8.1
pytz==2020.1
s3transfer==0.3.3
six==1.15.0
sqlparse==0.3.1
urllib3==1.25.10
whitenoise==5.2.0
python3 version is 3.9.1 python3版本是3.9.1
and when I run the code in PyCharm shows:当我在 PyCharm 中运行代码时显示:
/Users/username/python/myProject/.venv/bin/python3.9 /Users/username/python/myProject/myApp/manage.py runserver 8000
Process finished with exit code 137 (interrupted by signal 9: SIGKILL)
I read maybe the problem of SIGKILL is about memory but half of my ram is free ~5GIG used 3GIG free我读到也许 SIGKILL 的问题是关于 memory 但我的 ram 有一半是免费的 ~5GIG 使用了 3GIG 免费
I am not sure is it the same problem like this - Python/pip process are killed in virtualenv (Apple M1 chip) .我不确定这是否是同样的问题 - Python/pip 进程在 virtualenv (Apple M1 chip) 中被杀死。 Maybe you can try the steps and use x86_64 mode shell to execute django.
也许您可以尝试这些步骤并使用 x86_64 模式 shell 执行 django。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.