-
-
Notifications
You must be signed in to change notification settings - Fork 105
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
Conda Doctor Altered Files: Python, in a new install, can't resolve. #741
Comments
I have found the forum, which is prolly a more appropriate place for this issue than in the repo. But, I have left this issue open until I am in receipt of assistance on the forum: If and when the situation is resolved, I will remember to close this issue. |
It was determined in the forum that this is a minor inoffensive packaging bug, as another forum member had the direct analogue of the doctor notification in their Anaconda base environment |
From that thread this is the file changed:
|
Moving to the |
Solution to issue cannot be found in the documentation.
Issue
In Termux, in a Debian proot chroot, I have been having issues with conda. As a result, I have learnt a lot about conda, especially how to keep an install in good health, which I didn't know before. I have tried both
miniconda3
andminiforge3
. I settled onminiforge3
and I have systematically resolved all issues except for:I have tried uninstalling all of conda and reinstalling. I have done that five times. Same error. I have tried doing a force reinstall of Python. It doesn't fix it. The curious thing, if I use conda to install a different version of Python, even in the new version, I get the same conda doctor error. Any help resolving this once and for all would be most appreciated.
Installed packages
Environment info
The text was updated successfully, but these errors were encountered: