Switch from `pip` to `conda` in Travis
See original GitHub issueBecause of https://github.com/openbabel/openbabel/issues/2067, we can no longer use pip
to install Open Babel. However, thanks to Felipe’s hard work in https://github.com/cclib/cclib/pull/758, it should be straightforward to make the full switch over.
Personally, I do not like conda
at all, one reason being its slowness, especially on Travis (total time for a single build went up to 12 and a half minutes from 7 and a half on 3.7), but we don’t have much choice unless we’d like to build just the Python bindings form scratch, and we’re already using it for Psi4 anyway.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Using conda with Travis CI
If you are already using Travis CI, using conda is a preferable alternative to using apt and pip to install packages. The Debian...
Read more >Continuous Deployment with Travis and CONDA
If switching from pip installing your package you may notice that this method takes longer to complete. In general, CONDA seems to be...
Read more >Travis-CI for Python and R with conda - August Guang
Conda is a great package manager for several languages, including Python, R and C++ that runs on Windows, macOS and Linux. Since it...
Read more >Installing both Python and R for a Travis build? - Stack Overflow
Here is a travis.yml I use for my pyrle package. It just installs R usinq the ubuntu package manager: language: python python: -...
Read more >Using Anaconda Repository (AER 2.28)
pip install git+https://github.com/Anaconda-Server/anaconda-client ... To install conda packages from the user travis, use the repository url https://conda.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Oh, and this is in order to upgrade from Open Babel 2.4.1 to 3.0.0, which…do we want to?
I think this was done in some combination of #758, #881, #939, though in between #939 and switching to GitHub Actions in #983 we never fully switched.