This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author dripton
Recipients dripton
Date 2007-09-06.22:06:49
SpamBayes Score 0.002498297
Marked as misclassified No
Message-id <1189116410.02.0.82025271699.issue1120@psf.upfronthosting.co.za>
In-reply-to
Content
Gentoo Linux, x86, Python 3.0a

I did a vanilla "./configure; make; make test; make altinstall" build.

The following files were created in /usr/local/bin:
-rwxr-xr-x 1 root root   18036 Sep  6 17:49 smtpd.py
-rwxr-xr-x 1 root root      81 Sep  6 17:49 pydoc
-rwxr-xr-x 1 root root      96 Sep  6 17:49 idle
-rwxr-xr-x 1 root root 3644316 Sep  6 17:58 python3.0
-rwxr-xr-x 1 root root    1401 Sep  6 17:59 python3.0-config

As intended, altinstall does not create /usr/local/bin/python, so
"python" is still the pre-existing python2.5.

However, other binaries are installed as though /usr/local/bin/python
were created, so they don't work.

dripton@al ~ $ pydoc
bash: /usr/local/bin/pydoc: /usr/local/bin/python: bad interpreter: No
such file or directory
dripton@al ~ $ idle
bash: /usr/local/bin/idle: /usr/local/bin/python: bad interpreter: No
such file or directory
dripton@al ~ $ smtpd.py
bash: /usr/local/bin/smtpd.py: /usr/local/bin/python: bad interpreter:
No such file or directory

Suggest that "make altinstall" should not put anything in the bin
directory except pythonX.Y and pythonX.Y-config, which are "safe"
because of the embedded version numbers.  Another option would be
installing those other binaries but with fixed shebang lines.
History
Date User Action Args
2007-09-06 22:06:50driptonsetspambayes_score: 0.0024983 -> 0.002498297
recipients: + dripton
2007-09-06 22:06:50driptonsetspambayes_score: 0.0024983 -> 0.0024983
messageid: <1189116410.02.0.82025271699.issue1120@psf.upfronthosting.co.za>
2007-09-06 22:06:49driptonlinkissue1120 messages
2007-09-06 22:06:49driptoncreate