Can't install awscli using Python 3.7

[ViktorHaag]

It seems like awscli pinning to an older version of pyyaml is, at least for the moment, causing a problem attempting to install under Python3.7.

See (yaml/pyyaml#126) for reference.

The PyYAML team is apparently attempting to release a fixed package for 3.7 users, but it looks like it might require 4.2b4 at the earliest; it's unclear to me whether they'll provide re-built wheels for older versions like the ones that awscli relies upon.

As the default Python3 with homebrew is now 3.7, I expect this will cause widespread breakages for awcli users.

Is it possible to un-pin the PyYAML dependency and reset it to >4.1?

See also #2290 and #3414

[ViktorHaag]

Closed as addressed with #3414

[JordonPhillips]

Gonna re-open this until we actually merge a fix. Generally speaking I wouldn't want to upgrade to 4.x even if it appears at first glance to be safe, at least not without a thorough vetting. But it does look like they're going to release 3.13 soon which will be 3.12 exactly but with 3.7 support. Looks like their current plans are to put that out on Thursday: yaml/pyyaml#193

[JordonPhillips]

Another complication to this is that we can't set Travis up for testing. The only way to do that right now is to use an undocumented experimental image with elevated privileges, or use a pre-release version that isn't wholly representative of the state of the released version.

travis-ci/travis-ci#9815

[number5]

Here is the temporary fix to install awscli or boto3 on Python 3.7 https://gist.github.com/number5/015eef7783e7ddf7d5a4176d4e6bc975

(Should not be required after pyyaml release 3.13 on 5th July and #3430 merged and released)

[asottile]

I just opened #3430 which enables the re-release of 3.12: 3.13

[tylerhackbart]

Anyone still having this issue, our team is when deploying through circleCI

[jakul]

@tylerhackbart You need to wait for #3430 to be merged & released.

[bureson]

@JordonPhillips the MR is ready and there is even a workaround for Travis, can you prioritize it please?

[antonioned]

@tylerhackbart I have the pip install awscli working on circleci, that has been fixed. But the pip install awsebcli is not. Anything on this ?

[number5]

@antonioned awsebcli is a different project (not even on github), you better ask their authors, see #2696

[ilanbiala]

When I run the following, AWS configure is still looking for Python 3.6...has this been fixed?

$ aws configure
-bash: /usr/local/bin/aws: /usr/local/opt/python3/bin/python3.6: bad interpreter: No such file or directory

[asottile]

Try brew reinstall awscli

[asottile]

This issue is fixed though, pyyaml 3.13 was released

[justnance]

Thanks @ViktorHaag for opening this issue and @asottile for your latest updates. It appears all the related PRs are merged and the work is complete. I am setting this issue to close soon pending any new feedback.

[no-response]

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.

[bitfede]

Still experiencing the same issue as the user @ilanbiala

I get this error when trying to execute the aws cli:

-bash: /Users/fede/Library/Python/3.7/bin/aws: /usr/local/opt/python/bin/python3.7: bad interpreter: No such file or directory

The suggested solution of running brew reinstall awscli does not fix the problem... Anyone has had this similar issue?

[dwene]

I also am experiencing this issue. Tried reinstalling awscli also, still get the same error as @bitfede.
It appears I'm on python version 3.8.5, wondering why it hard links to 3.7.

[matthinea]

Hack, but installing python@3.7 via homebrew and then cping that installation into the directory expected by awscli cleared the error for me.

brew install python@3.7
cp -r /usr/local/opt/python@3.7/bin/python3.7 /usr/local/opt/python/bin/python3.7