This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author rhettinger
Recipients SilentGhost, avalentino, christian.heimes, gregory.p.smith, gvanrossum, martin.panter, palaviv, rhettinger, terry.reedy, vstinner
Date 2016-08-22.02:11:58
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Guido, would you can to opine on this?  Every now and then we get a request to make command-line utilities out of tools in the standard library.  Whether we should or not depends on whether the standard library intends to be primarily a library for Python code or whether it is also about providing general purpose toolkits that might be helpful in a non-unix environment.

We've has some of these that have met with success (for example, timeit, json.tool, and SimpleHTTPServer) and others that were just a waste or a were a pale shadow of their full featured Unix counterparts (or left to rot in the Tools directory).  

If we go further down this road, it would be nice for you to lay out the ground roads for what kind of command line tools would be acceptable, how stable their API would be, and whether they should be separated from the module itself.  Do you even want to be in the business of offering command-line APIs that duplicate commonly available Unix tools?
Date User Action Args
2016-08-22 02:11:59rhettingersetrecipients: + rhettinger, gvanrossum, terry.reedy, gregory.p.smith, vstinner, christian.heimes, SilentGhost, martin.panter, palaviv, avalentino
2016-08-22 02:11:59rhettingersetmessageid: <>
2016-08-22 02:11:59rhettingerlinkissue26488 messages
2016-08-22 02:11:58rhettingercreate