[prev in list] [next in list] [prev in thread] [next in thread] 

List:       python-list
Subject:    Re: Issues installing Python 2.7
From:       Chris Angelico <rosuav () gmail ! com>
Date:       2014-11-27 22:40:51
Message-ID: CAPTjJmqXF9VgH0dvLhkEV137NhNhOC9B92hsj7ym2=1sHM7L0g () mail ! gmail ! com
[Download RAW message or body]

On Fri, Nov 28, 2014 at 4:40 AM, Dennis Lee Bieber
<wlfraed@ix.netcom.com> wrote:
> On Thu, 27 Nov 2014 11:53:10 +1100, Steven D'Aprano
> <steve+comp.lang.python@pearwood.info> declaimed the following:
>
>>billyfurlong@gmail.com wrote:
>
>>
>>> Add this to the bashrc
>>> export PATH=$PATH:/opt/python2.7/bin/
>>
>>I'm not so sure about that, but I don't have time to investigate right now.
>>
>         If this is for the user login (and where it won't conflict with the
> system startup processes) I'd have swapped the $PATH and /opt... order --
> putting the 2.7 bin directory ahead of the system bin directory.

I wouldn't. Do you know, for absolute certain, which programs you run
that end up calling on Python, perhaps via "#!/usr/bin/env python", or
perhaps by being shell scripts and running "python my_main_module.py",
or something? You'd break those. Unless, of course, you're making
absolutely sure there's no "python" command in the /opt/... directory,
in which case the PATH order won't have any semantic difference, and
directory caching will make sure there's virtually no performance
difference, so the current form is just as good.

That said, I have never compiled a Python 2, ever. I've always
compiled Py3, and let that happily take over the name "python3",
leaving the system Python 2.x on the name "python" and "python2".

ChrisA
-- 
https://mail.python.org/mailman/listinfo/python-list
[prev in list] [next in list] [prev in thread] [next in thread]