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 martin.panter
Recipients bbrazil, eric.araujo, martin.panter, michael.foord, orsenthil, r.david.murray, terry.reedy
Date 2015-10-05.04:57:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1444021080.16.0.957413710271.issue15280@psf.upfronthosting.co.za>
In-reply-to
Content
The name changes to the function parameters should be avoided without a good reason.

I would recommend rejecting all of the changes in this patch. They are basically changing one person’s coding style to another person’s style. I happen to prefer list() and map() over the list comprehension syntax.

I don’t have a problem with a variable named “type” in a small function. For instance, open_unknown() is only four lines, including signature and doc string! If you can’t easily predict all the variables in a larger function, then I suggest dividing it into smaller components. PEP 8 doesn’t seem to mention the issue of shadowing variable names that I can see anyway.
History
Date User Action Args
2015-10-05 04:58:00martin.pantersetrecipients: + martin.panter, terry.reedy, orsenthil, eric.araujo, r.david.murray, michael.foord, bbrazil
2015-10-05 04:58:00martin.pantersetmessageid: <1444021080.16.0.957413710271.issue15280@psf.upfronthosting.co.za>
2015-10-05 04:58:00martin.panterlinkissue15280 messages
2015-10-05 04:57:59martin.pantercreate