On Tue, May 12, 2020 at 5:20 PM Paul Moore <p.f.mo...@gmail.com> wrote: > > On Tue, 12 May 2020 at 07:53, Brandt Bucher <brandtbuc...@gmail.com> wrote: > > > > Another proposed idiom, per-module shadowing of the built-in zip with > > > > some subtly different variant from itertools, is an anti-pattern that > > > > shouldn't be encouraged. > > > Source? > > > > Point taken. I probably went a bit far labeling this a straight-up > > "anti-pattern", but it is certainly annoying to find that someone has added > > `from pprint import pprint as print` at the top of a module, for example > > (which has actually happened to me before). Very hard to figure out what's > > happening. > > Also irrelevant. It's very easy to suggest bad ways of using a > feature. That doesn't make the feature bad. You seem to be arguing > that zip_strict is bad because people can misuse it. We could probably > remove 99% of the Python language by that argument... >
And considering that "from __future__ import print_function" is an officially-sanctioned way to cause a semantic change to print, I don't think it's really that strong an argument. Python is *deliberately* designed so that you can shadow things. I am most in favour of the separate-functions option *because* it makes shadowing easy. Not an anti-pattern at all. ChrisA _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/EWNW7SQGN55NIME6LD3NVVJUWIKXZO4I/ Code of Conduct: http://python.org/psf/codeofconduct/
