-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Aws-cli run error in linux #800
Comments
I am running Mac OSX 10.9 and I'm getting the same error with Python 3.4, but it seems to work OK using Python 2.7. |
What version of py3.4 are you using? I just tried this with py3.4.0 and I'm not getting any errors. |
Ah, I see this on py3.4.1. Interesting this 3.4.1 is not backwards compatible. Looking. |
Yes, exactly the python3.4.1 seems some backward compatibility issues. I suspect the problems in botocore library. |
Now fixed in boto/botocore#300 |
I have begun encountering this same error over the past couple of days and am unsure of how to fix it. Any ideas? Ubuntu 14.04
|
I think an automated upgrade to Python caused me the same issue Currently on Python 3.4.3 |
Im also having the same issue with ubuntu 14.04. |
Same problem here. |
Same thing started to happen today (used to work since it was an automated task). The previous one was
I downgraded python to 3.4.0-2ubuntu1 and it's working again
|
The downgrade to 3.4.0-2ubuntu1 did not work for me. Now I get another error
|
Didn't work for me either actually I get the threading error as well. |
I got it working. Pip install upgrade botocore and awscli. |
The version of the CLI installed via |
Updating awscli via pip did the job. Thank you @Aeramor @JordonPhillips ! |
I have same problem. awscli/trusty,now 1.2.9-2 looks broken see below. |
@umiyosh I already submitted a bug report, so I marked yours as a duplicate. That escalates the 'heat' of the issue a great deal, which is great. For anybody else being affected, marking yourself as affected and subscribing to the issue will further raise the heat. I'm trying to get in contact with canonical, but I don't have a direct contact with the team that maintains the package. I'll update on this github issue when I have any new information. Again, I highly recommend using pip instead of aptitude. That will allow you to get bug fixes and new features ASAP. Bug report: https://bugs.launchpad.net/ubuntu/+source/awscli/+bug/1501042 |
For a workaround, based on what @Aeramor said I did this:
which fixed things for me :) |
I ran into the same issue (for downgrading to
and gave us a working aws cli again (with packages from |
I finally got into contact with somebody at Canonical. Looks like there's a fix in the works in the 'proposed' channel. To fix the issue without downgrading / locking python to version 3.4.0, perform the following: First, enable the proposed repo
No word on how long it will take to reach the main repository, but based on their update procedures it looks like it'll be somewhere in the neighborhood of a week or more. We've opened a priority support ticket requesting expedited escalation to the main update channel, so hopefully it'll be sooner than that. At the risk of sounding like a broken record, I highly recommend you use pip instead of aptitude to install the cli. It's the only way to be sure you're getting the latest features and bug fixes since we directly control that package. |
Note that To downgrade and remove the now-pulled package upgrade, the suggestion provided by @somechris worked for my hosts (the last line Hopefully the botocore update makes it into |
The botocore update has made its way into the stable update channel as of last night. When python 3.4.3 is reintroduced, the issue should no longer be present. https://bugs.launchpad.net/ubuntu/+source/python-botocore/+bug/1499075 |
@JordonPhillips Thanks, it works. |
Still experiencing same issue on Ubuntu 14.04, tried the mentioned fix (removing python3.4 and reinstalling), no dice. The version of python is:
I went for the pip solution. |
it worked for me |
Still has the same issue on Ubuntu 14.04. It worked for me:
|
I am using Arch linux, installed the aws from tarball tried also the pip install same problem. Using python version 3.4.
The text was updated successfully, but these errors were encountered: