James Paget added the comment:
The 2.7.12rc1+ build resolves the issue for me.
--
___
Python tracker
<http://bugs.python.org/issue27305>
___
___
Python-bugs-list m
James Paget added the comment:
Python Packaging Authority member pfmoore from pypa/pip says "there's no
ctypes-based code that could be causing the error" and "Python appears to be
crashing as a result of pure Python code" and "there's no way that I can see
James Paget added the comment:
I have submitted this to pip as you have suggested (see pip Issue #3795), but
feel that Python.exe should not crash even if there is a problem with a
third-party package.
--
___
Python tracker
<http://bugs.python.
New submission from James Paget:
On Windows 10 Professional 64-bit, typing "pip list --outdated" or "python -m
pip install -U pip" at the Windows command prompt causes Python 2.7.12rc1 to
crash. I get the standard "python.exe has stopped working" crash not
New submission from James Paget:
This applies to Python 3.5.1rc1 only. The Windows 64-bit standalone installer
installs setuptools 18.2, but the latest version is 18.5. It should be noted
that the Python 2.7.11rc1 Windows 64-bit standalone installer installs
setuptools 18.5. Other Python
New submission from James Paget:
The operator -= modifies a frozenset (this should not be possible),
instead of signaling a TypeError. Contrast with the += operator.
>>> f=frozenset([1,2])
>>> f
frozenset([1, 2])
>>> f -= frozenset([1])
>>> f
frozense
New submission from James Paget:
In Python 3.4, type:
>>> import itertools
>>> list(itertools.repeat(1))
The system will hang, and a cold reboot is necessary (at least on Windows). I
expected some sort of "infinite list" exception to be thrown.
--
c
