- #AWS SUDO PIP COMMAND NOT FOUND INSTALL#
- #AWS SUDO PIP COMMAND NOT FOUND UPGRADE#
- #AWS SUDO PIP COMMAND NOT FOUND TRIAL#
You can get the path with python -m site -user-base But the packages will still be visible to all Python projects that you create. User site-packages is where Python installs packages available only for you. You can check the global site package with the command python -m siteįor example, on Linux with Python 3.7 the path is usually /usr/lib/python3.7/dist-packages/setuptools Global site-packages is where Python installs packages that will be available to all users and all Python applications on the system.
#AWS SUDO PIP COMMAND NOT FOUND INSTALL#
Not sure if this is something that will be helpful for others, but figured I'd throw it into the mix.Before jumping into the command that will install pipenv, it is worth understanding where pip installs Python packages. So I did this: sudo chmod -R a+r /Library/Python/Īnd then afterwards, I'm able to use the aws commands again.
#AWS SUDO PIP COMMAND NOT FOUND UPGRADE#
The solution that the operating system upgrade had changed permissions. Pkg_resources.DistributionNotFound: pip=1.5.5 Raise DistributionNotFound(req) # XXX put more info here Needed = self.resolve(parse_requirements(requirements))įile "/System/Library/Frameworks/amework/Versions/2.7/Extras/lib/python/pkg_resources.py", line 565, in resolve
I upgraded from OSX 10.7 to OSX 10.9 and afterwards, my installation of aws no longer worked.įrom pkg_resources import load_entry_pointįile "/System/Library/Frameworks/amework/Versions/2.7/Extras/lib/python/pkg_resources.py", line 2603, in įile "/System/Library/Frameworks/amework/Versions/2.7/Extras/lib/python/pkg_resources.py", line 666, in require And this is exactly why I have 2 version installed.
#AWS SUDO PIP COMMAND NOT FOUND TRIAL#
However, if I'm doing local trial and error work for a remote system that uses the Python2.7 version, I'm going to want to use that. I probably want to use the Python3.6 version. System/Library/Frameworks/amework/Versions/3.6/bin/awsĪs you can see, I have 2 bin folders and 2 aws executables. System/Library/Frameworks/amework/Versions/2.7/bin/aws $ find /System/Library/Frameworks/amework -type f -perm -100 -name aws System/Library/Frameworks/amework/Versions/3.6/bin System/Library/Frameworks/amework/Versions/2.7/bin Apply what we've learned $ find /System/Library/Frameworks/amework -type d -name bin I have 2 Pythons and neither of them use the same paths or even path patterns as the OP. $ python3 -c 'import awscli print(awscli)' Here is how I do that: $ python -c 'import awscli print(awscli)' Ask your python where things are installed.The easiest answer is also our next learning lesson: How did OP know to look in their /Library/Frameworks/amework/Versions/3.3/lib/python3.3/site-packages/? # the `-` in `perm -100` means not an exact match of 100 In this case I would have suggested looking for bin folders via: find /Library/Frameworks/amework -type d -name binīut, if you are going to do that, you might as well just search for your executable via: find /Library/Frameworks/amework -type f -perm -100 -name aws Look for bin folders that share a common lineage.Executables tend to not be in lib folders.
And consider that the OP stated, " there are no executables named aws." That brings us to our first learning lessons: Library/Frameworks/amework/Versions/3.3/bin Let's learn somethingĬompare those paths to find their commonality: /Library/Frameworks/amework/Versions/3.3/lib/python3.3/site-packages/awscli The solution was to add /Library/Frameworks/amework/Versions/3.3/bin to the my PATH. There are a number of files located at /Library/Frameworks/amework/Versions/3.3/lib/python3.3/site-packages/awscli, however there are no executables named aws. So, let's break down WHY his solution worked so you can apply it to yourself. The OP answered their own question, but the exact location of the executable is more likely to be different than it is to be the same.
0 kommentar(er)
