A RetroSearch Logo

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

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2001-April/014060.html below:

[Python-Dev] A kind of configuration question

[Python-Dev] A kind of configuration question [Python-Dev] A kind of configuration questionCameron Laird claird@starbase.neosoft.com
Thu, 5 Apr 2001 17:51:13 -0500 (CDT)
Why's there no Win* executable pydoc?

Let me know if I should ask this elsewhere.  In part,
I think I'm searching for larger generalizations that
I'm particularizing with this specific instance.

A Unix-side installation-from-source provides, along
with much else, an executable /usr/local/bin/pydoc,
whose content is simply
  #!/usr/bin/env python

  import pydoc
  pydoc.cli()    
As near as I can tell, installation of the 2.1 Python
binaries for Win* gives no corresponding executable or
"shortcut" for that (those) platform(s).  Is it intended
generally to provide homologous facilities for each of
Unix and Win* (and MacOS)?  Is ... well, how should I
think about this?

I wrote Ka-Ping Yee (the pydoc lord--right?) earlier in
the day.  I've received no response.



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