-
Notifications
You must be signed in to change notification settings - Fork 32
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] - Cannot install from conda #252
Comments
Looks like the first error was present in an old version of conda and fixed in 4.6.0 |
Looks like the 2nd error can be fixed by adding to the windows paths See this comment |
Is it worth to start a troubleshooting section in the doc? |
Up to you, I think these are conda issues instead of geouned issues. I suspect they don't occur when using miniforge instead of anaconda or when using mamba instead of conda |
Working for me in conda 23.3.1 |
@dodu94, whenever you can, please confirm if the error persists with the new release on conda-forge. |
I still get the same error for conda 22.X (on my laptop). On conda 23.X (on my WS), instead, it took something like 20 mins if this endless looping:
but finally it managed to install |
Conda appears to on version v24.7.1 at the moment, would it be worth trying a newer version we could add a hint to update the conda version to the install docs if that helps? For speed of solve then I think mamba is faster option |
Also please consider the fact that conda now moved to a mandatory paid plan for organizations of more than 200 employees (https://www.anaconda.com/pricing) so its popularity may fall a bit in the future (at least in pure open source environments) |
Yes a pip install would be great. I thought the use of miniforge + mamba + conda-forge helps avoid the paid plan |
Describe the bug
I tried to install geouned from conda on a fresh enviroment (python 3.11) without success. Error can be seen in the screenshot.
To Reproduce
Steps to reproduce the behavior:
for example:
Screenshots
Please complete the following information):
The text was updated successfully, but these errors were encountered: