-
-
Notifications
You must be signed in to change notification settings - Fork 135
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
[Bug] Python Repair is broken #428
Comments
Under the hood, all the repair function does is try to reinstall the package, and in your case, Homebrew itself returned a That error is thrown when the package folder exists, but there are no versions installed for that package. I'm not surprised python broke like that. I'd recommend going to
If it's not empty, still delete the entire |
Thanks for the support here. When you say "Reinstall Python, but through the Terminal” does it matter if it installed via brew or should I use a different tool for this install? Thanks again!
…On Nov 17, 2024 at 15:39 -0600, David Bureš ***@***.***>, wrote:
Under the hood, all the repair function does is try to reinstall the package. I think not even Homebrew can fix it for you 😅
That error is thrown when the package folder exists, but there are no versions installed for that package. I'm not surprised python broke like that.
I'd recommend going to /usr/local/Cellar/python/ and seeing if that folder is empty, if it is, do this:
• Delete that entire folder
• Reinstall Python, but through the Terminal
If it's not empty, still delete the entire /usr/local/Cellar/python/ folder, and do the above steps
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
I meant that you should use brew to reinstall the package 😊 |
Thank you, just want to make sure I don’t screw this up. I don’t mean to make you support me in repairing all of this, feel free to direct me to any documents at any time. After reinstalling via python, my `/usr/local/Cellar/python/` folder remains deleted. However, ***@***.***/` now exists.
Is there any way I can link these / replace the `/usr/local/Cellar/python/` folder?
Thank you again for your help.
…On Nov 17, 2024 at 16:31 -0600, David Bureš ***@***.***>, wrote:
I meant that you should use brew to reinstall the package 😊
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
If you mean you got a folder like
So, for example you can have a package that's You shouldn't move any of these versions to I'm not sure how Python works, but what I'd do now is add the |
Thanks for the insight here, I just realized GitHub censored what I tried to share via email. What I was attempting to share was that
All this said, I believe that reinstalling Python, thanks to your support and some Googling (but mostly your support and time), has resolved my errors. When opening Cork, I no longer see the "python is corrupted" alert, which is refreshing, and when running python3 in terminal I have the expected output of a Clang callback with Thank you very much for your time and support! I am grateful that newer devs and full stack designers like myself have a tool like Cork to rely on instead of blindly running commands and guessing their way through while hoping for the best, like I did all those years ago. A quick note that may be helpful for users, when the Thank you for your time, your support, and your guidance; I deeply appreciate it and hope and pray for immense success with Cork! |
What were you trying to do?
I wanted to clean up my environment with Cork. Upon opening I saw a message that read
python is corrupted
(I agree and have no idea how to fix it on my machine).What was the problem?
When clicking on the
Repair python
button, Cork goes through the repair process, eventually telling the user that Python is repaired. However, when closing and then reopening Cork, the message returns (final attached image).I don't know if this a bug with Cork or more of an issue on my end but whatever it is, Cork cannot seem to repair my issues with Python.
After reopening Cork post "repair"
Error logs
App Version
1.4.6.1 (85)
App Acquisition
Self-Compiled
Final checklist
The text was updated successfully, but these errors were encountered: