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 Comments
Leave a Reply. |