RetroSearch Browse

Tue May 29 05:31:27 CEST 2012 · https://mail.python.org/pipermail/python-dev/2012-May/119731.html

On 5/28/2012 10:31 PM, Nick Coghlan wrote:

> Given an exchange on the tracker, I feel I should expand on this point.
>
> Historically, our Setup&  Usage documentation has *only* covered the
> main Python executable, even though we actually install additional
> tools, including pydoc, idle, 2to3 and now pysetup and pyvenv, and
> provide additional documented and supported command line functionality
> via command line execution of certain modules.
>
> It is my view that this lack of centralised command line usage
> documentation is an *oversight*, not a deliberate policy that should
> be continued (hence the two new blocking issues for 3.3 as noted in my
> previous post).
>
> I've now created two more (lower priority) issues to cover the other
> officially supported command line interfaces that are currently
> missing from the setup&  usage documentation:
> Existing scripts (pydoc, idle, 2to3): http://bugs.python.org/issue14944

I added a preliminary, rough outline for idle to the issue.

> Supported -m commands: http://bugs.python.org/issue14945

-- 
Terry Jan Reedy

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2012-May/119731.html below:

[Python-Dev] Missing command line documentation for new tools