Skip to content
This repository has been archived by the owner on Oct 17, 2024. It is now read-only.

Introduce fall-back onto pip if conda doesn't have recent version #100

Closed
bsipocz opened this issue Jun 15, 2016 · 2 comments
Closed

Introduce fall-back onto pip if conda doesn't have recent version #100

bsipocz opened this issue Jun 15, 2016 · 2 comments
Labels
bug

Comments

@bsipocz
Copy link
Member

bsipocz commented Jun 15, 2016

Based on recent discussion in #97 #98 and on gitter, we will need an option to fall back on altrnative ways of installing a package is the version available on conda is too old.

E.g. if a build asks for 'stable' astropy version (currently we have v1.2rc1), then it's not OK to install v0.3 or v0.4 or even v1.0.3 from conda, but should go instead pip install v1.1.2
@larrybradley larrybradley mentioned this issue Jun 19, 2016
Merged
@bsipocz bsipocz mentioned this issue Jun 20, 2016
Merged
@bsipocz bsipocz added the bug label Jun 20, 2016
@astrofrog
Copy link
Member

@bsipocz - this is done, right?

@bsipocz
Copy link
Member Author

bsipocz commented Jun 21, 2016

Indeed!

@bsipocz bsipocz closed this as completed Jun 21, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@astrofrog @bsipocz