[issue7328] pydoc doesn't work from the command line

2010-01-31 Thread Éric Araujo
Changes by Éric Araujo : -- nosy: +Merwok ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org

[issue7328] pydoc doesn't work from the command line

2009-11-15 Thread Nick Coghlan
Changes by Nick Coghlan : -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsu

[issue7328] pydoc doesn't work from the command line

2009-11-15 Thread Nick Coghlan
Nick Coghlan added the comment: Fixed in r76312 and subsequent checkins (pydoc was corrupting sys.path when run under -m and getting away with it in 2.x, but breaking os.popen in 3.x) -- ___ Python tracker

[issue7328] pydoc doesn't work from the command line

2009-11-15 Thread Nick Coghlan
Nick Coghlan added the comment: pydoc removes the "scriptdir" from sys.path. When run under -m, that means it removes the standard library directory! It works in 2.x because os.popen doesn't rely on subprocess there - instead it comes direct from the builtin posix module. -- _

[issue7328] pydoc doesn't work from the command line

2009-11-15 Thread Antoine Pitrou
Antoine Pitrou added the comment: Same with an installed Python by the way: $ usr/bin/python3 -m pydoc str No module named subprocess However, it works when not using "-m" but invoking the file directly: $ ./python Lib/pydoc.py str [displays the str doc page] -- assignee: -> ncoghl

[issue7328] pydoc doesn't work from the command line

2009-11-15 Thread Antoine Pitrou
New submission from Antoine Pitrou : This works under 2.x but not 3.x: $ ./python -m pydoc str No module named subprocess -- components: Library (Lib) messages: 95297 nosy: pitrou priority: normal severity: normal stage: needs patch status: open title: pydoc doesn't work from the comman