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
Add src/sage/symbolic/assumptions to the reference manual #16695
Comments
comment:2
Yeah, doesn't even seem to need much sprucing up - maybe changing to |
comment:3
I have made little tweaks to the doc, including
New commits:
|
Changed branch from u/cheuberg/symbolic/assumptions-reference-manual to public/ticket/16695 |
comment:4
This seems to be a brand-new branch not including my minimalistic branch. Therefore, it seems that |
comment:5
Oops, sorry, looks like I have made a mistake. Should I take care of that, or are you going to do it ? |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Reviewer: Clemens Heuberger |
comment:7
I merged my old branch so that the changes now actually show up in the reference manual. I reviewed your changes and amended a few details. |
Changed author from Clemens Heuberger to Frédéric Chapoton, Clemens Heuberger |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Changed reviewer from Clemens Heuberger to Clemens Heuberger, Ralf Stephan |
comment:9
I added two minor fixes. Hope it's OK if I set positive? |
Changed branch from public/ticket/16695 to |
The file
src/sage/symbolic/assumptions.py
was not part of the reference manual; therefore, the documentation of the global functionassume()
etc. was not in the reference manual.See the discussion at https://groups.google.com/forum/#!topic/sage-devel/pb5C1xPTU7c .
This simple patch adds it to
reference/calculus
.CC: @dkrenn @kcrisman
Component: symbolics
Keywords: assumptions, assume
Author: Frédéric Chapoton, Clemens Heuberger
Branch/Commit:
fb6f620
Reviewer: Clemens Heuberger, Ralf Stephan
Issue created by migration from https://trac.sagemath.org/ticket/16695
The text was updated successfully, but these errors were encountered: