Message 177210 - Python tracker

Message177210

Author	ncoghlan
Recipients	aliles, asvetlov, cjw296, eric.araujo, kristjan.jonsson, ncoghlan
Date	2012-12-09.11:42:49
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1355053370.19.0.43956450171.issue7741@psf.upfronthosting.co.za>
In-reply-to

Content
Good to know - I guess in most circumstances copy-and-paste already works, because the input will be arriving via a line-buffered IO stream. I was thinking that with #16649 implemented, it would be possible to simply switch from "single" to "exec", without users needing to request the multi-statement support explicitly. However, I'm now back to wondering if such a change might have a few unforeseen consequences I haven't thought of. So if that seems like too much of a risk to backwards compatibility, how about moving the "symbol" argument to __init__, rather than needing to supply it with each call to push?

Content

Good to know - I guess in most circumstances copy-and-paste already works, because the input will be arriving via a line-buffered IO stream.

I was thinking that with #16649 implemented, it would be possible to simply switch from "single" to "exec", without users needing to request the multi-statement support explicitly. However, I'm now back to wondering if such a change might have a few unforeseen consequences I haven't thought of.

So if that seems like too much of a risk to backwards compatibility, how about moving the "symbol" argument to __init__, rather than needing to supply it with each call to push?

History
Date	User	Action	Args
2012-12-09 11:42:50	ncoghlan	set	recipients: + ncoghlan, kristjan.jonsson, cjw296, eric.araujo, asvetlov, aliles
2012-12-09 11:42:50	ncoghlan	set	messageid: <1355053370.19.0.43956450171.issue7741@psf.upfronthosting.co.za>
2012-12-09 11:42:50	ncoghlan	link	issue7741 messages
2012-12-09 11:42:49	ncoghlan	create