[issue7813] Bug in command-line module launcher

Éric Araujo added the comment: Sorry, 2.6 only gets security fixes now, closing. Thanks for the report anyway! -- nosy: +eric.araujo resolution: -> out of date stage: test needed -> committed/rejected status: open -> closed ___ Python tracker

[issue7813] Bug in command-line module launcher

Pascal Chambon added the comment: Here is the patch you mentionned, it fixes my problem and seems unharmful indeed. The little problem is, I've not found related tests (test_pkgutil doesn't deal with the importer part) to ad little checks around compile(). Is that patch worth commiting anywa

[issue7813] Bug in command-line module launcher

Nick Coghlan added the comment: Since import and direct execution will cope with files that don't end with a blank line, changing the first argument to "source + '\n'" in the pkgutil compile call seems like a reasonable workaround for the limitation in the 2.6 compile function. -- _

[issue7813] Bug in command-line module launcher

R. David Murray added the comment: I meant issue 7268 in my previous message. -- ___ Python tracker ___ ___ Python-bugs-list mailing l

[issue7813] Bug in command-line module launcher

Pascal Chambon added the comment: Allright, I guess in these conditions this bugs doesn't require a patch B-) Thanks for the details. -- ___ Python tracker ___ __

[issue7813] Bug in command-line module launcher

R. David Murray added the comment: This fails on 2.6 maint but works on trunk. There have been several improvements to the way that that compile works in trunk, and one of those fixed the problem that you are seeing. The source of the problem is the final line in the source file containing