-
Notifications
You must be signed in to change notification settings - Fork 338
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
Creating an environment with geo stack problem with python 3.7 #9
Comments
It's your fault! ;) This is the offending line: I'm currently parsing this as Mixing stars and relational operators should be forbidden. I'll try to push conda-forge's linter to disallow this. |
We can change the behavior for the next release of mamba so that this behavior is backward-compatible! Thanks for trying it out, by the way! |
I fixed the first issue, but the parser needs to become a little smarter (supporting |
Works with 0.0.3 (as far as I can tell!) Let us know if you see other problems! :) |
Tested again with 0.3, and indeed now working nicely (for this specific case) It does however give a slightly different result compared to conda (but not sure if this is important / a problem, just noted it). The main difference seems to be that mamba is getting
|
Actually, up to now I only looked at what mamba proposed, but now trying to actually create the environment, I get an error for the example above:
And the rolling back also didn't fully succeed, as the Doing the same with |
Hi Joris, great! Happy to hear that :) Indeed, I think it's due to how I implemented version comparison that sometimes the default channel "wins" where conda-forge should win. Luckily the guys over at |
hmm interesting! I didn't observe that specific problem yet. One idea I have is that we need to install pip (which I think is something that conda automatically adds). Otherwise I wouldn't know what the difference between conda and mamba at this stage is... |
I get the same error when explicitly adding pip to the required packages ( I have a |
Bumps [@actions/io](https://github.com/actions/toolkit/tree/HEAD/packages/io) from 1.0.2 to 1.1.1. - [Release notes](https://github.com/actions/toolkit/releases) - [Changelog](https://github.com/actions/toolkit/blob/main/packages/io/RELEASES.md) - [Commits](https://github.com/actions/toolkit/commits/@actions/tool-cache@1.1.1/packages/io) --- updated-dependencies: - dependency-name: "@actions/io" dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Gave mamba a test drive for installing an environment with the geospatial stack (with mamba-0.0.2 just installed). The following command works:
but, it proposes to create an environment with python 3.6, while I expected it to use the latest python 3.7.
If I try to specify that explicitly:
I get an error (for some reason, it tries to install geopandas-0.1.1.0-py27_0). Full output:
But in any case, it is much faster! (also in failing :))
The text was updated successfully, but these errors were encountered: