* Ruben Di Battista:
> What I suggest you is to use virtualenvs.
Good advice.
> * Install py-virtualenv
That's not required anymore. Python 3.3 and newer have virtual
environment support built in[1].
[1] https://docs.python.org/3/library/venv.html
-Ralph
Thank you everyone for these really useful suggestions -- learning always!
Forrest
On Fri, Nov 29, 2019 at 7:41 PM Ryan Schmidt
wrote:
> On Nov 29, 2019, at 10:01, Dave Allured wrote:
>
> > I have the longer user home prefix because my institutional network
> policy prevents all write access to /opt/anything.
>
> I still think the suggestion I made in
>
I still need to release my muscle memory .
(in reality I don't use bare virtualenv but more pew and pipenv that I
believe use venv for Python 3)
On Tue, 3 Dec 2019, 01:42 Ralph Seichter, wrote:
> * Ruben Di Battista:
>
> > What I suggest you is to use virtualenvs.
>
> Good advice.
>
> > *
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
Wait wait wait wait...
Why are you doing the `python setup.py` thing? I strongly discourage you to
use the system python to install packages globally.
What I suggest you is to use virtualenvs.
* Install py-virtualenv
* Create virtualenv
* Activate the virtual environment
* Install things
For aws-cli, I use the current code and this is how you install it,
setup.py.
Again, when I use the system MacOS python, it does the right thing; when
I use Macports python3, it ends up installing under a large tree under
/opt, which is not the correct behavior. So until I figure out the
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
I have a need to run the latest GIT of the aws-cli, so while the port is
there, I need to be able to compile and install the nightly code updates
for testing.
So I am building aws-cli from the GIT repository.
Thanks.
On 12/2/19 3:07 PM, Christopher Jones wrote:
OK.
So when you say build
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
OK, I see.
Maybe though you could learn from what the macports port does, and try and
replicate it. Note it does install stuff to ${prefix}/bin, as you want. e.g.
> port contents py37-awscli
/opt/local/bin/aws-3.7
/opt/local/bin/aws.cmd-3.7
/opt/local/bin/aws_bash_completer-3.7
On 2 Dec 2019, at 13:50, Forrest 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
12 matches
Mail list logo
