> PS. Why wasn't a new builtin zip_strict() on the menu? I think I would
have given it at least +0.5, because of this rule of thumb.

I would think that if zip_strict() added as a builtin, then zip_longest()
should too.

And the fact that zip_longest was not added as a builtin made me think that
it was a non-starter.

Which kinda brings up a point— in the example string methods (formerly the
string module) there are a number of separate functions that could have
been one function with flags. And that works well. But partly because it’s
a a well defined namespace. We really don’t want to clutter up builtins too
much, and having such closely related functions in different namespaces
really reduces the  usability.

-CHB


-- 
Christopher Barker, PhD

Python Language Consulting
  - Teaching
  - Scientific Software Development
  - Desktop GUI and Web Development
  - wxPython, numpy, scipy, Cython
_______________________________________________
Python-ideas mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/python-ideas.python.org/
Message archived at 
https://mail.python.org/archives/list/[email protected]/message/MFJPBQLJOCNDMLZZFMJGRQOVK6UGNPYE/
Code of Conduct: http://python.org/psf/codeofconduct/

Reply via email to