Having issues installing CustomTkinter on Mac
I have tried to install this package using pip install customtkinter, but then I get this error:
error: externally-managed-environment
× This environment is externally managed
╰─> To install Python packages system-wide, try brew install
xyz, where xyz is the package you are trying to
install.
If you wish to install a Python library that isn't in Homebrew,
use a virtual environment:
python3 -m venv path/to/venv
source path/to/venv/bin/activate
python3 -m pip install xyz
If you wish to install a Python application that isn't in Homebrew,
it may be easiest to use 'pipx install xyz', which will manage a
virtual environment for you. You can install pipx with
brew install pipx
You may restore the old behavior of pip by passing
the '--break-system-packages' flag to pip, or by adding
'break-system-packages = true' to your pip.conf file. The latter
will permanently disable this error.
If you disable this error, we STRONGLY recommend that you additionally
pass the '--user' flag to pip, or set 'user = true' in your pip.conf
file. Failure to do this can result in a broken Homebrew installation.
Read more about this behavior here: <https://peps.python.org/pep-0668/>
note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.
Does anybody else have the same issue on Macs? What would be the best recommended way to solving this problem?
Have you tried pip3 install customtkinter?
Regards.
Have you tried
pip3 install customtkinter?Regards.
I get the same error warning message.
While this issue is not specific to customtkinter, you may attempt the following solution:
pip install customtkinter --break-system-packages
Additionally, please consider the following steps:
- Reinstall your Python environment setup. The issue might be due to a mix of different Python versions installed on your system.
- Using a virtual environment may also resolve this problem.
Regards
Is there no way to update using brew itself?