Hacker News new | ask | show | jobs
by colpabar 1706 days ago
I've seen that before, but I dunno, it seems kind of anti-python[0] to have an "official doc" that basically says "here's a third-party tool we like, but also here's 5 other tools you could use instead." I want ONE tool, built and maintained by the same people who build and maintain python, so that it always works.

[0]: There should be one-- and preferably only one --obvious way to do it. (from the zen of python)

1 comments

That’s never been true for packages. Just because someone else did it doesn’t mean you can’t do it better. The goal in the last few years has been to make it possible for anyone to write a build system or tooling, just like any other library in Python. Otherwise there is no innovation.
Innovation or invitation to shave a Yak?