Unable to install FF14 due to Python2 errors? Im trying to install FF14 on my MacBook, something that I've done before and should be fairly easy. Ive done a bit of python development and used pyenv to make changing which python version im using easier. Initially I got an error that it wanted me to report to apple because it said that python 2 wasn't installed specifically in the location it wanted. So I went to python.org and downloaded the latest official release of 2.7.18. Now upon trying to start the game I am greeted with this error. I tried to use pip to install cxutils but I get the same error. Any suggestions? Python: How to install pygments using pip? I had pygments (a colorizing Python code parser) running on my previous OS High Sierra. Now in Catalina it won't install. pip install Pygments The error I get, after a long list of other errors, is: pkg_resources.DistributionNotFound: The 'pip==20.1.1' distribution was not found and is required by the application How to get the pip installer working? Can someone tell me exactly how to fix the messy Python system on Catalina? I can't figure it out and it seems botched in multiple locations. Mac MI installing kernel on JupyterLab I have been trying to install JupyterLab with Python 3.10.5 on my M1 Mac Mini running macOS Monterey version 12.4. First, please note that I had no issue doing the same on my Intel based MacBook Pro also running macOS Monterey version 12.4. Installing Python 3.10.5 was not a problem. Following the instructions at Installation — JupyterLab 3.4.3 documentation 1, I opened a Terminal window and ran the following command: pip3 install jupyterlab All seemed to be going well and then the text provided in the additional text appeared in the terminal window. Any information on what is happening and how to solve the issue would be greatly appreciated. Sincerely, Dale

Start with modifying the PATH line in. your Zsh shell dot file (~/.zshrc):


export PATH="/usr/local/bin:${PATH}



and then from the Terminal, run the following to make that PATH current:


source ~/.zshrc


Next, you install Python 3.9.4 (universal) directly from Python.org (not using brew) — which is a normal macOS package installer. It will create a Python 3.9 folder in your /Applications folder, deposit python3, idle3, etc in /usr/local/bin as links back to:


/Library/Frameworks/Python.framework/Versions/3.9/bin


and though the Python 3.9.4 installer updates your PATH statement for Bash, it still does not do so for the Zsh shell, so back to your ~/.zshrc dot file for one last change:


export PATH="/Library/Frameworks/Python.framework/Versions/3.9/bin:${PATH}"


and


source ~/.zshrc


If you have installed Xcode, or the command-line tools for Xcode 12.4, these place a Python v3.8.2 into /usr/bin, and if you do not make the preceding PATH adjustments, it is that older Python3 that you get by default, and one that won't let you install modules into it.


The last PyAudio module that I see was last updated in 2017 and very likely not compatible with Python 3.9.4.


One way to avoid polluting the main Python 3.9.4 package area is to create a virtual environment that you install packages into as I have done for pyobjc, pyobjc-core, and Qt 5.15.

Show more

Hello @jitender8076,


I solved this issue on my M1 Mac through the following Steps:

  • Firstly, uninstall the PyAudio & portaudio from you systemby the following commands:
brew uninstall portaudio
pip uninstall pyaudio
  • Update your brew :
brew update
  • Upgrade the wheel and setuptools:
python3 -m pip install --upgrade pip setuptools wheel
  • Then, install the latest version of portaudio:
brew install portaudio --HEAD
  • Install PyAudio:
python3 -m pip install pyaudio --global-option="build_ext" --global-option="-I/opt/homebrew/include" --global-option="-L/opt/homebrew/lib"


For Miniforge/ Anaconda environment, install the pyaudio in side the environment i.e:

conda activate myEnvName
python3 -m pip install pyaudio --global-option="build_ext" --global-option="-I/opt/homebrew/include" --global-option="-L/opt/homebrew/lib"



And you are good to go!!!

Show more

Start with modifying the PATH line in. your Zsh shell dot file (~/.zshrc):


export PATH="/usr/local/bin:${PATH}



and then from the Terminal, run the following to make that PATH current:


source ~/.zshrc


Next, you install Python 3.9.4 (universal) directly from Python.org (not using brew) — which is a normal macOS package installer. It will create a Python 3.9 folder in your /Applications folder, deposit python3, idle3, etc in /usr/local/bin as links back to:


/Library/Frameworks/Python.framework/Versions/3.9/bin


and though the Python 3.9.4 installer updates your PATH statement for Bash, it still does not do so for the Zsh shell, so back to your ~/.zshrc dot file for one last change:


export PATH="/Library/Frameworks/Python.framework/Versions/3.9/bin:${PATH}"


and


source ~/.zshrc


If you have installed Xcode, or the command-line tools for Xcode 12.4, these place a Python v3.8.2 into /usr/bin, and if you do not make the preceding PATH adjustments, it is that older Python3 that you get by default, and one that won't let you install modules into it.


The last PyAudio module that I see was last updated in 2017 and very likely not compatible with Python 3.9.4.


One way to avoid polluting the main Python 3.9.4 package area is to create a virtual environment that you install packages into as I have done for pyobjc, pyobjc-core, and Qt 5.15.

Show more
KunalBhayana wrote:

Even I am a longtime Windows user I am regretting this purchase so much.

The whole problem here is that these are unsupported, open-source projects that you can't purchase for any price. The idea is that you purchase an M1 Mac so that you can fix pyaudio, homebrew, pip3, pipwin, portaudio, and Python 3 so that they will work on the M1 for other people. Large corporations like Google, Amazon, and Facebook would really appreciate your work so that they can more easily port their internal code to less expensive ARM-based system. You weren't expecting them to do the work themselves, were you?

Show more
KunalBhayana wrote:

I was expecting everything to be ready since it's almost 6 months now.

Actually it has been almost 11 months since Apple Silicon computers have first been available to developers. Apple is only responsible for its own software, which works fine. If you have 3rd party software that isn't working, you will have to contact the developers and let them know.

Show more

Hello @jitender8076,


I solved this issue on my M1 Mac through the following Steps:

  • Firstly, uninstall the PyAudio & portaudio from you systemby the following commands:
brew uninstall portaudio
pip uninstall pyaudio
  • Update your brew :
brew update
  • Upgrade the wheel and setuptools:
python3 -m pip install --upgrade pip setuptools wheel
  • Then, install the latest version of portaudio:
brew install portaudio --HEAD
  • Install PyAudio:
python3 -m pip install pyaudio --global-option="build_ext" --global-option="-I/opt/homebrew/include" --global-option="-L/opt/homebrew/lib"


For Miniforge/ Anaconda environment, install the pyaudio in side the environment i.e:

conda activate myEnvName
python3 -m pip install pyaudio --global-option="build_ext" --global-option="-I/opt/homebrew/include" --global-option="-L/opt/homebrew/lib"



And you are good to go!!!

Show more
First comment 'brew install portaudio' in a virtual environment then 'pip install pyaudio' or 'pip3 install pyaudio' if these comments don't work try this comment in a virtual enviorenment if you directly paste the comment in terminal maybe doesn`t run 'pip install --global-option='build_ext' --global-option='-I/opt/homebrew/Cellar/portaudio/19.7.0/include' --global-option='-L/opt/homebrew/Cellar/portaudio/19.7.0/lib' pyaudio' 
                        
A forum where Apple customers help each other with their products. Get started with your Apple ID.
Learn more Sign up This site contains user submitted content, comments and opinions and is for informational purposes only. Apple may provide or recommend responses as a possible solution based on the information provided; every potential issue may involve several factors not detailed in the conversations captured in an electronic forum and Apple can therefore provide no guarantee as to the efficacy of any proposed solutions on the community forums. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Community Terms of Use. See how your data is managed...