This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author db3l
Recipients
Date 2002-03-22.23:06:27
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
Logged In: YES 
user_id=53196

If compile() is being used in exec mode with a non-
terminated multi-line string, it's not going to work unless 
the application generates that copy itself in any event.  
So without an interpreter fix, I'd think the string copy is 
inevitable, and it might simplify things to have the 
builtin function take care of it.  It's something easy to 
overlook at the application level and could thus be fixed 
in one place rather than at each point of use.

On the other hand, I also noticed something I overlooked 
when first encountering the problem - the 2.2 docs added 
some text to compile() talking about this need for 
termination.  So it could be argued that it's now a 
documented restriction, and should the newline append (with 
any requisite string duplication) be needed, it leaves it 
to the individual applications rather than forcing it in 
the builtin.

Not to mention a documentation solution could thus be 
declared already done.
History
Date User Action Args
2007-08-23 13:58:33adminlinkissue501622 messages
2007-08-23 13:58:33admincreate