From 38c28e379c42fc520daf38a94637886869b692c0 Mon Sep 17 00:00:00 2001
From: Greg Ward <gward@python.net>
Date: Thu, 27 Apr 2000 18:32:02 +0000
Subject: Added a note to the section on 'exec' about the need for a trailing
 newline in certain circumstances.  (Apparently, this is a CPython problem.)

---
 Doc/ref/ref6.tex | 11 ++++++++++-
 1 file changed, 10 insertions(+), 1 deletion(-)

diff --git a/Doc/ref/ref6.tex b/Doc/ref/ref6.tex
index 6c2b485..b62e394 100644
--- a/Doc/ref/ref6.tex
+++ b/Doc/ref/ref6.tex
@@ -227,7 +227,7 @@ target sequence, if the object allows it.
 \indexii{slicing}{assignment}
 
 \end{itemize}
-	
+        
 (In the current implementation, the syntax for targets is taken
 to be the same as for expressions, and invalid syntax is rejected
 during the code generation phase, causing less detailed error
@@ -612,3 +612,12 @@ for use by \keyword{exec}.
 \bifuncindex{eval}
 \bifuncindex{globals}
 \bifuncindex{locals}
+
+Also, in the current implementation, multi-line compound statements must
+end with a newline:
+\code{exec "for v in seq:\e{}n\e{}tprint v\e{}n"} works, but
+\code{exec "for v in seq:\e{}n\e{}tprint v"} fails with
+\exception{SyntaxError}.
+\exindex{SyntaxError}
+  
+
-- 
cgit v0.12