> But I don't see any practical difference with including setuptools and > including a module that installs setuptools. Would you be happy with > the standard library including a module whose sole function was to > install a package that you weren't happy to include directly in the > standard library? I wouldn't, personally. If the actual code is not in Python, I'm not responsible for it. I don't have to deal with bug reports, and I don't have to help users with that feature. As users want to get the functionality anyway, and out-of-the-box, I consider it a useful compromise. Regards, Martin
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4