Developer's Guide: Add instructions for sagelib development in a conda environment
mkoeppe opened this issue · 35 comments
#28745 updates the installation manual and explains the use of SAGE_ROOT/environment[-optional].yml.
As section in the developer's guide should explain the use of SAGE_ROOT/src/environment-[optional].yml
... from https://wiki.sagemath.org/Conda
including answers to the following questions (from #31099):
- How do I now create a conda environment with a given name in a given location with the sage dependencies installed, and activate this env later and run say the doctests? Similarly, say I've created a conda env myself and activated it.
- How can I now install the sage dependencies and run tests/lints using tox in this env?
Depends on #28745
CC: @dimpase @isuruf @saraedum @tobiasdiez
Component: documentation
Keywords: conda, sd110, sd111
Author: Isuru Fernando, Matthias Koeppe
Branch/Commit: b4e9e8c
Reviewer: Matthias Koeppe, Tobias Diez
Issue created by migration from https://trac.sagemath.org/ticket/28746
Ticket retargeted after milestone closed
Changed keywords from none to Anaconda
Changed keywords from Anaconda to Anaconda, conda
Changed keywords from Anaconda, conda to conda
pushing these forward to 9.2
Changed keywords from conda to conda, sd110
Description changed:
---
+++
@@ -1 +1 @@
-
+... from https://wiki.sagemath.org/CondaDescription changed:
---
+++
@@ -1 +1,6 @@
+#28745 updates the installation manual and explains the use of `SAGE_ROOT/environment[-optional].yml`.
+
+As section in the developer's guide should explain the use of `SAGE_ROOT/src/environment-[optional].yml`
+
+
... from https://wiki.sagemath.org/CondaHoping we can make progress on this ticket this week - https://wiki.sagemath.org/days111
Changed keywords from conda, sd110 to conda, sd110, sd111
Description changed:
---
+++
@@ -4,3 +4,10 @@
... from https://wiki.sagemath.org/Conda
+
+including answers to the following questions (from #31099):
+
+- How do I now create a conda environment with a given name in a given location with the sage dependencies installed, and activate this env later and run say the doctests? Similarly, say I've created a conda env myself and activated it.
+- How can I now install the sage dependencies and run tests/lints using tox in this env?
+
+Branch: u/isuruf/sagelib
Branch pushed to git repo; I updated commit sha1. New commits:
028c702 | use conda to provide all SPKGs |
Branch pushed to git repo; I updated commit sha1. New commits:
b9928fd | run ./bootstrap again just in case it failed with m4/gettext errors before |
Branch pushed to git repo; I updated commit sha1. New commits:
29ce3fa | Use update so that it is self-explanatory |
Author: Isuru Fernando
Branch pushed to git repo; I updated commit sha1. New commits:
d08601d | clarify the difference |
Wondering if the environment files in src/ should use a different environment name...
Sure. Feel free to push a change.
Changed branch from u/isuruf/sagelib to u/mkoeppe/sagelib
Changed author from Isuru Fernando to Isuru Fernando, Matthias Koeppe
Reviewer: Matthias Koeppe, ...
New commits:
5912ab3 | src/environment*.yml: Use sage, not sage-build, as environment name |
Branch pushed to git repo; I updated commit sha1. New commits:
b4e9e8c | src/doc/en/installation/source.rst: Expand slightly |
Changed reviewer from Matthias Koeppe, ... to Matthias Koeppe, Tobias Diez
LGTM
Changed branch from u/mkoeppe/sagelib to b4e9e8c