[Python-bugs-list] [ python-Bugs-409430 ] pydoc install broken

[noreply@sourceforge.net]

Bugs item #409430, was opened at 2001-03-17 10:04
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=409430&group_id=5470

Category: Installation
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Michael Hudson (mwh)
>Assigned to: Fred L. Drake, Jr. (fdrake)
Summary: pydoc install broken

Initial Comment:
I've moaned about this on python-dev but I want to make
sure it doesn't get forgotten.

I've just built from CVS, installed in /usr/local, and:

$ pydoc -g
Traceback (most recent call last):
  File "/usr/local/bin/pydoc", line 3, in ?
    import pydoc
ImportError: No module named pydoc

because the /usr/bin/env python thing hits the older
python in /usr first.

Don't really know how best to implement this, not being
a distutils whiz.

----------------------------------------------------------------------

>Comment By: Guido van Rossum (gvanrossum)
Date: 2001-12-07 05:48

Message:
Logged In: YES 
user_id=6380

Fred, can you have a quick look at this and bounce it back
to MWH with a yea or nay?

----------------------------------------------------------------------

Comment By: Michael Hudson (mwh)
Date: 2001-12-07 05:08

Message:
Logged In: YES 
user_id=6656

I finally got off my fat butt and had a go at fixing this.

I've no idea who to assign this to to get it reviewed, I'm
afraid.  Someone have a look please!

----------------------------------------------------------------------

Comment By: Michael Hudson (mwh)
Date: 2001-08-11 07:40

Message:
Logged In: YES 
user_id=6656

Oops, not paying attention.

Revision 1.9 of Lib/distutils/command/build_scripts.py seemed 
to be aimed at fixing this; however, I now have a ~/bin/pydoc 
that starts:

#!python

which isn't too helpful.  This command either needs to do 
something different when building Python, or a different 
command needs to be used to install the pydoc script.

Or you could wedge the install path into sys.executable in 
setup.py, I suppose.

Assigned to Greg, as I don't think he's had this patch yet.

Also bumped priority, as we now seem to be installing 
decidely broken scripts, and changed summary.


----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2001-06-10 21:56

Message:
Logged In: NO 

I am having similar problems with the win 2.1 ver
it seems none of my saved .py files are recognised.
Is this simply a case of not configed as an executable or a 
version clash?
(solutions as well as opinions would be nice)
I can however import string,sys and other modules if that 
muddies the water any.

----------------------------------------------------------------------

Comment By: Guido van Rossum (gvanrossum)
Date: 2001-04-10 12:11

Message:
Logged In: YES 
user_id=6380

OK, ping-pong.  Ping, do you have any bright ideas?

----------------------------------------------------------------------

Comment By: A.M. Kuchling (akuchling)
Date: 2001-04-10 10:57

Message:
Logged In: YES 
user_id=11375

The pydoc script is Ping's, really.  Fixing this requires
Distutils 
hackery, and I don't see that this is worth fixing.  Leaving
it to someone else to make the decision to close it, though.

----------------------------------------------------------------------

Comment By: Tim Peters (tim_one)
Date: 2001-03-17 22:23

Message:
Logged In: YES 
user_id=31435

Assigned to Andrew because I seem to recall he wrote the 
pydoc script.

----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=409430&group_id=5470