➜

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 Eric Lafontaine, docs@python, gvanrossum, rhettinger, tebeka
Date 2016-12-17.02:05:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1481940353.22.0.811937999203.issue28972@psf.upfronthosting.co.za>
In-reply-to
Content 
+1 for Miki's idea.  It would be nice if there were a single page that collected together all the command-line tools (with examples).  It should include a 2to3 example as well.  Also, there should be some indication of which tools we guarantee to be available (2to3 json.tool) versus those that just happen to be exposed but are subject to change (possibly because they were just used for testing, or because they have a crummy API, or because Guido has said that we are in the library business, not the command-line tool business).

See also:  http://bugs.python.org/issue26488
History
Date User Action Args
2016-12-17 02:05:53rhettingersetrecipients: + rhettinger, gvanrossum, tebeka, docs@python, Eric Lafontaine
2016-12-17 02:05:53rhettingersetmessageid: <1481940353.22.0.811937999203.issue28972@psf.upfronthosting.co.za>
2016-12-17 02:05:53rhettingerlinkissue28972 messages
2016-12-17 02:05:52rhettingercreate