| 1 | | @urbanit: I think this may be related: https://youtrack.jetbrains.com/issue/PY-17069#comment=27-1804561&tab=Comments |
| | 1 | Repro steps: |
| | 2 | |
| | 3 | - Install Python 3.x (doesn't happen on 2.x) |
| | 4 | - Open Windows PowerShell (only happens with PowerShell, not CMD or bash) |
| | 5 | - `pip install django` |
| | 6 | - `django-admin startproject foobar` |
| | 7 | - `cd foobar` |
| | 8 | - `python manage.py runserver` |
| | 9 | |
| | 10 | This causes a Windows crash with a window that says: "Python has stopped working": http://imgur.com/dOt6eKE |
| | 11 | |
| | 12 | However, `python manage.py runserver --noreload` works fine, so it seems related to the auto-reloader. |
| | 13 | |
| | 14 | Here is the info from the Windows Event Viewer: |
| | 15 | |
| | 16 | {{{ |
| | 17 | Faulting application name: python.exe, version: 3.5.1150.1013 |
| | 18 | Faulting module name: ucrtbase.dll, version: 10.0.14393.0 |
| | 19 | Exception code: 0xc0000005 |
| | 20 | Faulting module path: C:\WINDOWS\System32\ucrtbase.dll |
| | 21 | |
| | 22 | }}} |
| | 23 | |
| | 24 | I have seen it happen with at least 5 people using Py3 & PowerShell, with Windows 8 or 10, and various PC models. (Though most people seem unaffected.) |
| | 25 | |
| | 26 | Occurs with Django 1.8/1.10 and Python 3.5/3.6, maybe others also. |