Context Navigation

Changes between Version 5 and Version 6 of Ticket #27647

v5	v6
19	19	I have run Django 1.8, 1.9 and 1.10 on multiple Python versions on top of Windows 10 64-bit on different computers. Starting with Python 3.5 and Python 3.6 I have reproduced a consistent segmentation fault on the `runserver` command with both 32-bit and 64-bit Pythons. This has happened for several months. `python manage.py migrate` and other commands work well and consistently. `python manage.py runserver` is the ONLY command that segmentation faults and does NOT do this with `--noreload` option. Today I dug a bit deeper on the cause of the segmentation fault.
20	20
21		As a note, I have also run Django on top of Python 3.4 and at least the 32-bit distribution, for whatever reason, tends not to cause errors like these. This is, however, just my ~~butt-feeling, as we say in Finland, and I have not measured the stuff for a small~~ while.
	21	As a note, I have also run Django on top of Python 3.4 and at least the 32-bit distribution, for whatever reason, tends not to cause errors like these. This is, however, just my gut feeling and I have not looked into the `runserver` error rate on Python 3.4 for a while.
22	22
23	23	----