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 ncoghlan
Recipients CuriousLearner, eric.smith, ncoghlan
Date 2017-06-09.04:19:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1496981968.17.0.346491787423.issue30597@psf.upfronthosting.co.za>
In-reply-to
Content
Eric, right, I left a couple of logical leaps out of my reply as well. My first thought was the same as yours but then I went:

- that means we need to split on commas
- which means we need to track whether or not we're inside a quoted string or not
- which is probably more complexity than is warranted just to produce a slightly better hint to the user

Result: let's just use "<expr>" as a placeholder for "the thing you were trying to print"

Although now that I put it that way, "<output>" is probably a better user-oriented placeholder, since "expr" (short for expression) is a very language-developer-oriented term, while "print(<output>)" is closer to pseudocode.
History
Date User Action Args
2017-06-09 04:19:28ncoghlansetrecipients: + ncoghlan, eric.smith, CuriousLearner
2017-06-09 04:19:28ncoghlansetmessageid: <1496981968.17.0.346491787423.issue30597@psf.upfronthosting.co.za>
2017-06-09 04:19:28ncoghlanlinkissue30597 messages
2017-06-09 04:19:27ncoghlancreate