[Python-Dev] Design Principles
tjreedy at udel.edu
Wed Aug 31 23:05:17 CEST 2005
"Raymond Hettinger" <raymond.hettinger at verizon.net> wrote in message
news:003501c5ae63$664f5e40$4320c797 at oemcomputer...
> FWIW, after this is over, I'll put together a draft list of these
> principles. The one listed above has served us well. An early draft of
> itertools.ifilter() had an invert flag. The toolset improved when that
> was split to a separate function, ifilterfalse().
> Other thoughts:
> Tim's rule on algorithm selection: We read Knuth so you don't have to.
> Raymond's rule on language proposals: Assertions that construct X is
> better than an existing construct Y should be backed up by a variety of
> side-by-side comparisons using real-world code samples.
> I'm sure there are plenty more if these in the archives.
This would make a good information PEP to point people to when they ask
'Why ...' and the answer goes back to one of these principles.
Terry J. Reedy
More information about the Python-Dev