* lisp/progmodes/python.el: Add comment about pipe buffering and

solutions for missing/delayed output in inferior Python shells.

Fixes: debbugs:17304

diff --git a/lisp/ChangeLog b/lisp/ChangeLog
index 9c41c6f7ade1d399bdfdcaecd33969b2b8fc0e23..2ee5ee808c1abd2f3f7d7d9ec4a8a48e4c7af6ef 100644 (file)
--- a/lisp/ChangeLog
+++ b/lisp/ChangeLog
@@ -1,3 +1,9 @@
+2014-07-20  Fabián Ezequiel Gallina  <fgallina@gnu.org>
+
+       * progmodes/python.el: Add comment about pipe buffering and
+       solutions for missing/delayed output in inferior Python shells.
+       (Bug#17304)
+
 2014-07-20  Fabián Ezequiel Gallina  <fgallina@gnu.org>
 
        * progmodes/python.el (python-mode): Don't set

diff --git a/lisp/progmodes/python.el b/lisp/progmodes/python.el
index f4ff03e240563ac884458b200ac8169959815521..86970b8a0c7c154d9a8d4ee8bcfa4ec85e650890 100644 (file)
--- a/lisp/progmodes/python.el
+++ b/lisp/progmodes/python.el
@@ -94,6 +94,14 @@
 ;;       python-shell-interpreter-args
 ;;       "-i C:\\Python27\\Scripts\\ipython-script.py")
 
+;; If you are experiencing missing or delayed output in your shells,
+;; that's likely caused by your Operating System's pipe buffering
+;; (e.g. this is known to happen running CPython 3.3.4 in Windows 7.
+;; See URL `http://debbugs.gnu.org/cgi/bugreport.cgi?bug=17304').  To
+;; fix this, using CPython's "-u" commandline argument or setting the
+;; "PYTHONUNBUFFERED" environment variable should help: See URL
+;; `https://docs.python.org/3/using/cmdline.html#cmdoption-u'.
+
 ;; The interaction relies upon having prompts for input (e.g. ">>> "
 ;; and "... " in standard Python shell) and output (e.g. "Out[1]: " in
 ;; IPython) detected properly.  Failing that Emacs may hang but, in