-
Notifications
You must be signed in to change notification settings - Fork 504
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pidcat
installed via brew
no longer works on macOS 12.3, due to Python 2 having been removed
#180
Comments
Having the same issue here. Quick hack: install python 2 via brew: Then in
to
(Might vary depending on the exact installed version of python 2.) |
The fix applied in #179 makes |
Simply symlinking The real solution would be to fully depend Pidcat on Python 3. It's also about time, since Python 2 has long-since reached end of life. |
Any updates on this ? Should we make pidcat compatible with python 3 and simply replace python link with python3 in pidcat.py ? |
I got the same error on my Apple M1. I installed pidcat 2.1.0 via homebrew and python 3.8 by miniconda. The error is caused by the first line of local pidcat file(path: /opt/homebrew/Cellar/pidcat/2.1.0/bin/pidcat):
I just replaced it with: Line 1 in 61cd1ee
Don't forget to add write permission to the local pidcat file:
|
I tried installing the latest from master (
But I still get an error: If I try changing the
Any hints? |
switching to |
OK I actually modified the local file as #179 suggests and the whole thing (get colored pretty logs) works now |
I used to do the following for getting the logs saved into an html file with colors for sharing
After the changes in my comments above I can get colored logs in my terminal but they end in plain black text on the html. Any idea why? |
No formulae found in taps. |
I was able to fix it with following steps: # Use pyenv to install python2 with:
brew install pyenv
pyenv install 2.7.18
# Optionally set it to your global default:
pyenv global 2.7.18
# Create Alias in .zshrc
alias python=/Users/<user>/.pyenv/versions/2.7.18/bin/python
# Reload shell and test
source .zshrc
python -V
# Edit shebang line of Pidcat script
sudo nano "$(which pidcat)"
# Replace first line:
#!/Users/<user>/.pyenv/versions/2.7.18/bin/python -u
|
@rafaelmaeuer has the right answer! This worked for me as well, on macOS 12.3.1. I would recommend creating an alias |
rafaelmaeuer's solution also worked for me. |
I didn't want to set it as a default, neither use an alias and this is my workaround based on rafael's: # Workarounds for Pidcat.
# https://github.com/JakeWharton/pidcat/issues/180#issuecomment-1124019329
brew install pyenv
pyenv install 2.7.18
# Pidcat.
brew install pidcat
# Change pidcat to use Python 2.7.18
sudo sed -i '1d' "$(which pidcat)"
sudo sed -i "1i #\!$HOME/.pyenv/versions/2.7.18/bin/python -u" "$(which pidcat)" |
My workaround for Apple M1: $ chmod +w /opt/homebrew/Cellar/pidcat/HEAD-61cd1ee/bin/pidcat
$ sed -i '' '1 s/python/python3/' /opt/homebrew/Cellar/pidcat/HEAD-61cd1ee/bin/pidcat 🤓 |
Similar to Raphael's solution, I used pyenv to install version 2.7.18 and set it as global
Then I changed the #!/usr/bin/env python -u I used |
Hi @brAzzi64! Did you manage to solve this colors issue? [EDIT]
|
If anyone still read this; I'm not sure how come this still remains open. But both of the issues are fixed by changing:
The broken color output apparently came from the attempt to convert line buffer to utf8. |
Hey!
First off, thank you for the great util, Jake. And all the other cool stuff you've built througout the years.
I'm having an issue where
pidcat
, installed frombrew
, can no longer run on macOS 12.3. I believe this is because of Python 2 having been removed on this version of macOS.I'm getting the following output, when attempting to run
pidcat
:~ pidcat zsh: /opt/homebrew/bin/pidcat: bad interpreter: /usr/bin/python: no such file or directory
This in turn is caused by
pidcat/pidcat.py
Line 1 in 44b4a10
#!/usr/bin/python -u
On macOS 12.3,
/usr/bin/python
does not exist - only/usr/bin/python3
.Running on the latest development version (as listed in the current
README.md
, does not solve the issue, as it still looks forpython
, which still does not exist.One alternative that could resolve the issue would be to update
pidcat
to explicitly try to usepython3
, but this would have some less desirable backwards compatibility issues, perhaps.The text was updated successfully, but these errors were encountered: