Skip to content
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

Specifying conda version used #2076

Closed
jakirkham opened this issue Mar 17, 2016 · 14 comments
Closed

Specifying conda version used #2076

jakirkham opened this issue Mar 17, 2016 · 14 comments

Comments

@jakirkham
Copy link
Contributor

@jakirkham jakirkham commented Mar 17, 2016

Conda has gone through a lot of changes of late. Namely the 4.0 release. Given the large overhaul of the solver, there have been a few recent bug fix releases. It would be nice for users to specify the conda version used if they cannot work with 4.x yet or to opt-in to 4.x if they need it.

cc @Korijn @agjohnson

@agjohnson
Copy link
Contributor

@agjohnson agjohnson commented Mar 17, 2016

This could certainly be an option, we'd support this with our readthedocs.yaml via http://github.com/rtfd/readthedocs-build

Loading

@Korijn
Copy link

@Korijn Korijn commented Mar 17, 2016

I would personally recommend just running conda update conda -y at the start of each build.

Loading

@jakirkham
Copy link
Contributor Author

@jakirkham jakirkham commented Mar 17, 2016

Some people use specific versions of conda in their CIs. I think it is reasonable for them to set the version here to match.

It also helps when a bug enters conda to be able to pick a lower version that does not have this issue until it is fixed.

Loading

@humitos
Copy link
Member

@humitos humitos commented May 30, 2017

I would personally recommend just running conda update conda -y at the start of each build.

Maybe we can use the keyword latest for this and so run

conda update conda -y

but also accept the version number as 4.3.21 and run:

conda install conda=4.3.21 -y

Loading

@Korijn
Copy link

@Korijn Korijn commented May 30, 2017

To be frank, conda changes so much and has seen so many instabilities, I would rather allow users to bring their own deploy scripts, rather than adding an option each time something needs to be changed. RTD will always be lagging behind. Just let your users handle it!

Loading

@humitos
Copy link
Member

@humitos humitos commented May 30, 2017

@Korijn my proposal receives the version from the user: a pinned one or latest.

Loading

@wkerzendorf
Copy link

@wkerzendorf wkerzendorf commented Oct 6, 2017

I need a newer conda version - the current on rtd crashes. Is that possible with the current setup

Loading

@RichardLitt
Copy link
Member

@RichardLitt RichardLitt commented Oct 6, 2017

@wkerzendorf That sounds like a different issue. Could you create a new issue for that, showing the logs?

Loading

@agjohnson
Copy link
Contributor

@agjohnson agjohnson commented Oct 19, 2017

I think updating conda releases at build time fixes a number of conda issues for now -- we're actually still on 4.2.x on the stable build images.

If anyone wanted to take on configurable conda versions, here are the changes required:

Ultimately, does staying up to date with conda releases, alone, solve more problems? Do we really need to provide granular configuration of conda? My guess is no, most users would be better served by the latest version of conda. However, I say this without using conda for any repositories.

Loading

@wkerzendorf
Copy link

@wkerzendorf wkerzendorf commented Oct 19, 2017

@agjohnson I would argue along the same lines that the vast majority of users are much better served using the latest conda version. This would also mean that if problems occur this will use the team from continuum io (a company with much more resources and money), rather than requiring input from the RTD team. Would it be possible to try this?

Loading

@humitos
Copy link
Member

@humitos humitos commented Nov 16, 2017

Loading

@jakirkham
Copy link
Contributor Author

@jakirkham jakirkham commented Dec 1, 2017

FWIW I'm perfectly happy with your proposal @humitos.

Loading

@agjohnson
Copy link
Contributor

@agjohnson agjohnson commented Dec 4, 2017

Currently, we are alerted on any new releases to conda, we should be running the latest version on our build images -- or at least we'll be shamed by our CI into upgrading on a daily basis until we do upgrade :). Closing this as I don't see there being much use in a specific version of conda for end users. If anyone has a good reason for this, we can reopen this.

Loading

@agjohnson agjohnson closed this Dec 4, 2017
@humitos
Copy link
Member

@humitos humitos commented Dec 5, 2017

Loading

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
6 participants