OK. So when you say build from source, do you mean using MacPorts port for this, or are you building directly yourself (and if the later, any reason why you are not using the port ?)
https://github.com/macports/macports-ports/blob/master/python/py-awscli/Portfile <https://github.com/macports/macports-ports/blob/master/python/py-awscli/Portfile> > crjoberon ~ > port search awscli > awscli_select @0.1 (python, sysutils) > common files for selecting default awscli version > > py-awscli @1.16.292 (python) > Universal Command Line Environment for AWS. > > py27-awscli @1.16.292 (python) > Universal Command Line Environment for AWS. > > py35-awscli @1.16.292 (python) > Universal Command Line Environment for AWS. > > py36-awscli @1.16.292 (python) > Universal Command Line Environment for AWS. > > py37-awscli @1.16.292 (python) > Universal Command Line Environment for AWS. > On 2 Dec 2019, at 8:43 pm, Forrest <forrie@forr > ie.com> wrote: > > The /usr/bin/python installs the executable into /usr/local/bin. I'd be fine > if the Macports installed it in /opt/local/bin -- this makes me believe there > is a config directive I'm missing somewhere. > > > > On 12/2/19 2:38 PM, Christopher Jones wrote: >> When you say " vs /usr/bin/python that does the right thing and places the >> commands in proper places “ where exactly are you referring to ? Where >> exactly do you want the macports provided python to install things to ? >> >>> On 2 Dec 2019, at 7:50 pm, Forrest <[email protected]> wrote: >>> >>> I'm new to Python and I'm trying to figure out why, for example, when I >>> install aws-cli (from source) using Macports, it doesn't install properly >>> vs /usr/bin/python that does the right thing and places the commands in >>> proper places. When I run "/opt/local/bin/python setup.py install" it >>> ends up buried in directories under the Macports directory structure, which >>> isn't usable. Maybe I am missing some ENV variables? >>> >>> >>> >>> F >>> >
smime.p7s
Description: S/MIME cryptographic signature
