[issue24961] shell stdout broken after exiting interactive python prompt

2015-08-29 Thread Dave Hein

Dave Hein added the comment:

Thanks. I installed py34-readline and rebuilt my virtualenv; all is well now.

I put in a MacPorts ticket when their bugtracker gets back online.

--

___
Python tracker 
<http://bugs.python.org/issue24961>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue24961] shell stdout broken after exiting interactive python prompt

2015-08-29 Thread Dave Hein

New submission from Dave Hein:

With 3.4.3 from an OS X terminal prompt, if I just enter the interactive Python 
REPL environment (by just entering the command "python" from the command line) 
and then exit (via "exit()" or Ctrl-D), then stdout appears to be broken ... I 
see no stdout output on the terminal from that point forward. I do see stderr 
output.

If I just run a python script, without the "-i" flag, then stdout is not 
damaged and the subsequent terminal interaction is normal.

I did not see this with 3.4.2 or any other version of Python.

I'm running OS X 10.9.5, have installed Python 3.4.3 with MacPorts, and use 
virtualenv.

--
components: IO
messages: 249337
nosy: datihein
priority: normal
severity: normal
status: open
title: shell stdout broken after exiting interactive python prompt
type: behavior
versions: Python 3.4

___
Python tracker 
<http://bugs.python.org/issue24961>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com