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 rhettinger
Recipients GeekyShacklebolt, brett.cannon, docs@python, rhettinger, serhiy.storchaka
Date 2018-08-14.00:53:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1534208031.62.0.56676864532.issue34117@psf.upfronthosting.co.za>
In-reply-to
Content
Results from two Python courses:

* In terms of teaching gexexps, there was no net gain or loss.  When genexps are show side-by-side with list/dict/set comps the symmetric relationship was obvious regardless of terminology.

* In terms of being able to search StackOverflow, blog posts, and external resources, the new terminology made the resources unfindable.

* When using the new terminology, I did get questions that never came up before, "why don't the parentheses mean tuple-comprehension".

Based on those results, I recommend we keep the terminology the same as it is now.  The loss of searchability isn't worth it (there doesn't seem to be any upside) and it is concerning that a new category of confusion (list/tuple comprehension) seems to be arising from the change in terminology.
History
Date User Action Args
2018-08-14 00:53:51rhettingersetrecipients: + rhettinger, brett.cannon, docs@python, serhiy.storchaka, GeekyShacklebolt
2018-08-14 00:53:51rhettingersetmessageid: <1534208031.62.0.56676864532.issue34117@psf.upfronthosting.co.za>
2018-08-14 00:53:51rhettingerlinkissue34117 messages
2018-08-14 00:53:51rhettingercreate