The following illustrates a problem with the parser 
handling the lack of trailing newlines:

>>> parser.suite('def foo():\n\tpass\n\n# comment')
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
  File "<string>", line 4
    # comment
           ^
SyntaxError: invalid syntax
>>> parser.suite('def foo():\n\tpass\n\n# comment\n')
<parser.st object at 0x847f0a0>

This is similar to bug 501622, however, this only seems 
to happen when you have an indented block, followed by 
a comment line that has no trailing newline.

I traced through tokenizer.c and whittled down the issue 
into tok_get().  In the statement where it is processing 
the comment character and looking at the tabforms, in 
the first case this will end up with 'c' equal to EOF 
whereas in the second case "c" will eqaul '\n'.  When it 
equals EOF, it is unable to do the cleanup necessary to 
emit the DEDENT token (it immediately bails out with 
ENDMARKER which causes parsetok() to barf because 
the indentation level is still 1 inside tok_state).

Attached is a patch of a little hack I made that seems 
to fix the problem.  Although it seems to be a safe thing 
to do, it is definitely a hack.

Logged In: YES 
user_id=393416

Well, wonderful sourceforge is barfing with the 
error "ArtifactFile: Could not open file for writing" when trying 
to upload my patch, so I'll just post it in the comment here.  
Very sorry. :(

--- tokenizer.c	3 Feb 2004 22:53:59 -0000	1.2
+++ tokenizer.c	16 Apr 2005 01:45:05 -0000
@@ -1139,6 +1139,9 @@
 		}
 		while (c != EOF && c != '\n')
 			c = tok_nextc(tok);
+		if (c == EOF) {
+			c = '\n';
+		}
 	}
 	
 	/* Check for EOF and errors now */

Logged In: YES 
user_id=1038590

Confirmed on SVN HEAD using:

exec """
def foo():
    pass

#comment"""

(Blows up with a syntax error)

Logged In: YES 
user_id=593130

As noted by F.Lundh on pydev list,
http://docs.python.org/lib/built-in-funcs.html
says "When compiling multi-line statements, two caveats 
apply: [...] and the input must be terminated by at least 
one newline character" so it appears that doc == behavior.
Should this be closed? or both changed?

As of 2.5.1, a missing trailing newline no longer causes a Syntax Error,
making the second part of the caveat in the documentation unnecessary.

Changing to a documentation bug applicable to 2.5+.

The exec example still presents me a syntax error in 2.5.2.

Missing trailing newline still triggers error as of 2.5.1:

>>> import parser
>>> parser.suite("pass\n ")
IndentationError: unexpected indent
>>> parser.suite("if True:\n pass\n ")
SyntaxError: invalid syntax

Yeah, it's actually still blowing up for me to. I have no idea what I
actually tested when I thought it was working in 2.6/3.0 - I must have
managed to sneak an extra carriage return into the test string. So
reverting back to marking it as a non-easy interpreter core problem.

Confirmed on versions 2.6.2, 3.0.1 and 3.1rc1.  On the three of them, I
tried this:

>>> import parser 
>>> test = 'def foo():\n\tpass\n\n# comment'
>>> parser.suite(test)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "<string>", line 4
    # comment
           ^
SyntaxError: invalid syntax
>>>

This has been fixed in 2.7 and 3.2.