Oleg Broytman phdru.name> writes:
>
> On Mon, Jun 17, 2013 at 06:37:49PM +, Vinay Sajip
yahoo.co.uk> wrote:
> > echo off
> > __VENV_PYTHON__ -c "import sys, pydoc; sys.exit(pydoc.cli())"
>
>I think you want to pass command line arguments:
>
> echo off
> __VENV_PYTHON__ -c "import
On Mon, Jun 17, 2013 at 06:37:49PM +, Vinay Sajip
wrote:
> @echo off
> __VENV_PYTHON__ -c "import sys, pydoc; sys.exit(pydoc.cli())"
I think you want to pass command line arguments:
@echo off
__VENV_PYTHON__ -c "import sys, pydoc; sys.exit(pydoc.cli())" %1 %2 %3 %4 %5 %6
%7 %8 %9
Oleg.
On Mon, 17 Jun 2013 16:27:45 -, Vinay Sajip wrote:
> Issue #18224 (http://bugs.python.org/issue18224) highlights a problem on
> Windows with the pydoc script provided with venvs created by pyvenv. On
> POSIX, the script is named pydoc and causes no problems: on Windows, it is
> called pydoc.py
Richard Oudkerk gmail.com> writes:
>
> Can't a batch file pydoc.bat be used?
>
I generally find .bat files so limiting that I never thought of that. In
this case, it makes perfect sense to use one. Thanks!
@echo off
__VENV_PYTHON__ -c "import sys, pydoc; sys.exit(pydoc.cli())"
should do it.
On 17/06/2013 5:27pm, Vinay Sajip wrote:
3. Rename the pydoc.py script to pydoc-script.py and introduce a simple .exe
launcher pydoc.exe adjacent to it (which is how setuptools and distlib
handle installed scripts).
Can't a batch file pydoc.bat be used?
--
Richard
Issue #18224 (http://bugs.python.org/issue18224) highlights a problem on
Windows with the pydoc script provided with venvs created by pyvenv. On
POSIX, the script is named pydoc and causes no problems: on Windows, it is
called pydoc.py and this causes problems because it shadows the stdlib pydoc
mo
