AWS CLI not working on Mac OSX Yosemite




I have successfully downloaded AWS CLI using PIP on Mac OSX Yosemite. I am running Python version 2.7.


I can see the AWS executable in `/Library/Frameworks/Python.framework/Versions/2.7/bin`
  




 (adsbygoogle = window.adsbygoogle || []).push({});
 
  

.


But when I try to run


 `aws help`
  




 (adsbygoogle = window.adsbygoogle || []).push({});
 
  




in my terminal to check that the AWS CLI is running I get


 `-bash: aws: command not found`
  




 (adsbygoogle = window.adsbygoogle || []).push({});
 
  




Does anyone know why this is not working?
`/Library/Frameworks/Python.framework/Versions/2.7/bin`
  




 (adsbygoogle = window.adsbygoogle || []).push({});
 
  

should be on your way. In your file `~/.profile`
  




 (adsbygoogle = window.adsbygoogle || []).push({});
 
  

(create if needed) add a line like:



```
export PATH="/Library/Frameworks/Python.framework/Versions/2.7/bin:$PATH"

        

        
        
        
 (adsbygoogle = window.adsbygoogle || []).push({});
 
        

    
```


  




 (adsbygoogle = window.adsbygoogle || []).push({});
 
  

Open a new terminal window and it should work.
Did you had ACS common installed in your AEM.

<https://adobe-consulting-services.github.io/acs-aem-commons/features/versioned-clientlibs/index.html>




[View solution in original post](/t5/adobe-experience-manager/aem-implementation-of-versioning-for-clientlibs-and-css/m-p/399346#M7116) hi [@staffan](/u/staffan) ,

sorry for not responding to this sooner.

i know that chromeos now has some support for linux applications. odrive has a linux version, but this isn’t something we’ve tested on chromeos yet.

[agent/cli (linux, macos, win)](https://docs.odrive.com/docs/odrive-sync-agent)

sync agent and cli overview the odrive sync agent provides advanced users with a flexible, scriptable interface to odrive’s progressive sync engine. use it to bring cloud access and sync to almost any environment. the odrive sync agent can be used... if drivers are uptodate it will not show onto the list. else start the utility with 'run as administrator' option and see if it's working. solution to my problem.

install python enabling framework and then do the rest of the installation as defined

python\_configure\_opts="--enable-framework" pyenv install 3.6.8

the issue was with wx and the need for a framework

when running a simple ws app

import wx

app = wx.app(false) # create a… No other user in a public forum can help... and, since it does not seem that you are a plan administrator, I doubt that support can help


 


Be sure to remain signed in with your Adobe ID before accessing the link below  
-you must also allow 'cookies' in your web browser for this to work  
<https://helpx.adobe.com/contact/support.html> for chat or <https://helpx.adobe.com/contact/phone.html>  
-click the chat icon at the bottom right of the page to open a chat session  
-the chat icon looks like '3 dots inside a circle' at the lower right  
-type AGENT into the chat window to connect directly to a person rather than the AI  
Do be aware that Adobe's staffing is impacted by the virus, so wait times are long hey [@emartini](/u/emartini) ,

if you want to use clij2, you also need to activate the clij update site. the error should be gone then.

[[image]](https://aws1.discourse-cdn.com/business4/uploads/imagej/original/3x/0/9/095bc5fb3f3fa0db9dac6286bb16cf30ee81783d.jpeg "image")

see also the [installation instructions](https://clij.github.io/clij2-docs/installationinfiji).

let me know if this solves the issue!

cheers,

robert i had to actually connect to the team viewer from remote to get this popup. can you please fix the documentation to reflect this step please?

https://community.teamviewer.com/t5/knowledge-base/how-to-control-a-mac-running-macos-10-14-or-higher/ta-p/44699#toc-hid--**please do not post teamviewer ids** 7.0.3 is now available! :raised\_hands:

switch between modern and classic views on apple tv, remote control improvements, option to hide titles, and more.

<https://firecore.com/releases>
[[modern]](https://aws1.discourse-cdn.com/business7/uploads/firecore/original/3x/d/8/d81d00bfac171dafa1ee2862c7ea1ccff4c3a2a4.jpeg "modern")
[[classic]](https://aws1.discourse-cdn.com/business7/uploads/firecore/original/3x/7/8/788cfadb6f1830843dfd2b6d630750999f7271c6.jpeg "classic") [http://ccm.net/forum/affich-710527-please-help-me-to-open-my-yahoo-mail](/forum/affich-710527-please-help-me-to-open-my-yahoo-mail) Call statement Transfers control to a Sub procedure, Function procedure, or dynamic-link library (DLL)procedure.



I believe that you cannot use "CALL" to call a file which is not executable.  

same goes with SHELL...



Call Shell(AppName, 1) Where AppName contains the path of the Executable file.



try it with any other directory and try calling an executable.. it will work.



If you try calling a .txt or .bmp, it will give you the same error message...