[issue20347] dir(__future__) gives segfault on OS X in 3.2 and 3.3

2014-01-22 Thread Ned Deily
Ned Deily added the comment: This is a duplicate of Issue18458. The crash is caused by an incompatible change introduced in OS X 10.9 to the Apple-supplied version of libedit's readline compatibility layer and can affect Python versions that dynamically link with the system libedit (not all do

[issue20347] dir(__future__) gives segfault on OS X in 3.2 and 3.3

2014-01-22 Thread R. David Murray
Changes by R. David Murray : -- assignee: ronaldoussoren -> resolution: -> duplicate stage: -> committed/rejected status: open -> closed superseder: -> python.org Interactive interpreter linked with libedit can segfault on future OS X ___ Python

[issue20347] dir(__future__) gives segfault on OS X in 3.2 and 3.3

2014-01-22 Thread STINNER Victor
STINNER Victor added the comment: > Python 2.7.5 (default, Aug 25 2013, 00:04:04) You should try the version 2.7.6 which contains a fix for OS X 10.9: http://www.python.org/download/releases/2.7.6/ -- nosy: +haypo, hynek, ned.deily ___ Python tracke

[issue20347] dir(__future__) gives segfault on OS X in 3.2 and 3.3

2014-01-22 Thread Christopher the Magnificent
New submission from Christopher the Magnificent: On OS X 10.9.1 This works: Python 2.7.5 (default, Aug 25 2013, 00:04:04) [GCC 4.2.1 Compatible Apple LLVM 5.0 (clang-500.0.68)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> import __future__ >>> dir(__futur