I think this is a fine idea, but I also think we could use a more verbose FAC:
Frequently Asked Criticisms Some of the same things, but it would focus on the "why" of many of the issues. Many of the things people (newbies, mostly) complain about are simply taste, or legacy that isn't worth changing. But many are deliberate design decisions that were thoroughly thought out, and have been well explained in various places (i.e. zero-based indexing and open-on-the-right slicing). It would be good to have it all in one place. Maybe this PEP could be extended to include that, but it doesn't feel PEP-like to me. -CHB On Wed, Jan 11, 2017 at 7:17 PM, Oleg Broytman <p...@phdru.name> wrote: > On Thu, Jan 12, 2017 at 01:37:41PM +1100, Steven D'Aprano < > st...@pearwood.info> wrote: > > Explicit self > > ------------- > > > > Explicit ``self`` is a feature, not a bug. See the > > `FAQ <https://docs.python.org/3/faq/design.html#why-must-self- > be-used-explicitly-in-method-definitions-and-calls>`_ > > for more detail. > > If one thinks that ``self`` is too long and tedious to write she can > use ``s`` instead. > > Oleg. > -- > Oleg Broytman http://phdru.name/ p...@phdru.name > Programmers don't die, they just GOSUB without RETURN. > _______________________________________________ > Python-ideas mailing list > Python-ideas@python.org > https://mail.python.org/mailman/listinfo/python-ideas > Code of Conduct: http://python.org/psf/codeofconduct/ > -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception chris.bar...@noaa.gov
_______________________________________________ Python-ideas mailing list Python-ideas@python.org https://mail.python.org/mailman/listinfo/python-ideas Code of Conduct: http://python.org/psf/codeofconduct/
