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 ezio.melotti, gvanrossum, ncoghlan, peter.otten, pitrou, serhiy.storchaka
Date 2013-08-20.14:06:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1377007576.66.0.3902386563.issue18788@psf.upfronthosting.co.za>
In-reply-to
Content
As Serhiy's examples show, the ambiguities this introduces get confusing fast. A more constrained version that (for example) permitted only name references for the callable could resolve that, but it's probably still a bad idea. Still, interesting to know it is *technically* possible, if anyone decides to pursue it further :)

The "silently ignores bare print statements" aspect isn't new - Python 3 already behaves that way, since a print on its own line now just references the builtin without calling it.
History
Date User Action Args
2013-08-20 14:06:16ncoghlansetrecipients: + ncoghlan, gvanrossum, peter.otten, pitrou, ezio.melotti, serhiy.storchaka
2013-08-20 14:06:16ncoghlansetmessageid: <1377007576.66.0.3902386563.issue18788@psf.upfronthosting.co.za>
2013-08-20 14:06:16ncoghlanlinkissue18788 messages
2013-08-20 14:06:16ncoghlancreate