On 3/17/17 at 5:53 AM, [email protected] (Dan Clark) pronounced:
Got stuck and then unstuck, but there are questions.
First, AWS's EB linux instances are redhat-ish
[ec2-user@ip-172-31-4-9 ~]$ cat /etc/*-release
NAME="Amazon Linux AMI"
VERSION="2016.09"
ID="amzn"
ID_LIKE="rhel fedora"
VERSION_ID="2016.09"
PRETTY_NAME="Amazon Linux AMI 2016.09"
ANSI_COLOR="0;33"
CPE_NAME="cpe:/o:amazon:linux:2016.09:ga"
HOME_URL="http://aws.amazon.com/amazon-linux-ami/";
Amazon Linux AMI release 2016.09
The ID_LIKE attribute could be misleading.
Part of the battle might be understanding where everything is
located and their names. I don't have an AWS playground, but
maybe this will help.
Here is Python support information for AWS EB:
http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/concepts.platforms.html#concepts.platforms.python
Let's see where and which version of Python 3 you really have,
then look in the same directory for other Python packaging tools.
$ python3 --version
$ which python3
You might have a pip3, easy_install-3.4, and virtualenv. Check
the versions and whether they symlink elsewhere. Report back
and maybe we can figure out what's next.
Also I recall that you had to use `sudo` at one point, which
could be a sign of system hosing. If you suspect something is
terribly wrong, then there's no harm in blowing away your AWS
instance and starting clean, or rolling back to the initial
clean version (if rollbacks are possible with AWS).
--steve
------------------------
Steve Piercy, Soquel, CA
--
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/pylons-discuss/r473Ps-10123i-C625127BE1D54D76855C51B33312A5AC%40Steves-iMac.local.
For more options, visit https://groups.google.com/d/optout.
