On Fri, Aug 02, 2019 at 07:52:37AM +1000, Chris Angelico wrote: > Maybe there needs to be a > second-tier recommendation, where a list of packages can be given that > aren't category killers, but have been given the blessing of the > Python devs as "this is a good-quality, well-maintained package, and > can be depended on"?
Which of the core devs will have the responsibility for checking that something which is a good-quality, well-maintained, dependable package today remains so a year from now? There are third-party libraries like numpy, nltk etc which are too specialised, big and complex for anyone to duplicate in their own code. But I think that anyone who pip installs more-itertools *solely* to avoid copying and pasting the "grouper" receipe from the docs is doing themselves, and the users of their software, a disservice. It's three lines of code. Adding a third-party dependency of 2000+ sloc to avoid a three liner is not as bad as the Node.js LeftPad debarcle, but it's heading into the same ballpark. (Of course the calculus changes if you are a heavy consumer of iterators, and the extra tools in more-itertools are useful for you.) -- Steven _______________________________________________ Python-ideas mailing list -- python-ideas@python.org To unsubscribe send an email to python-ideas-le...@python.org https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://mail.python.org/archives/list/python-ideas@python.org/message/G6TPH6MESITYI2F6MTPWWWASXULO4H6T/ Code of Conduct: http://python.org/psf/codeofconduct/
