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.

Sign up for GitHub

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

Jump to bottom

Move Sphinx-ify on-the-fly code to another module #7000

Closed
qed777 mannequin opened this issue Sep 23, 2009 · 2 comments
Closed

Move Sphinx-ify on-the-fly code to another module #7000

qed777 mannequin opened this issue Sep 23, 2009 · 2 comments
Labels
c: documentation p: minor / 4 t: enhancement
Milestone
sage-4.1.2

Comments

@qed777
Copy link
Mannequin

qed777 mannequin commented Sep 23, 2009

The code for running docstrings through Sphinx on-demand could be useful in other contexts:

Currently, the code lives in cell.py, but it would be easier to mantain and extend in sage.misc, say.

CC: @jhpalmieri

Component: documentation

Issue created by migration from https://trac.sagemath.org/ticket/7000
@qed777 qed777 mannequin added c: documentation labels Sep 23, 2009
@qed777

This comment has been minimized.

Sign in to view
@williamstein
Copy link
Contributor

comment:3

This is now down as part of the notebook refactoring. It's in sagenb.misc.sphinxify.

@williamstein williamstein added this to the sage-4.1.2 milestone Sep 30, 2009
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
c: documentation p: minor / 4 t: enhancement
Projects
None yet
Milestone
sage-4.1.2
Development

No branches or pull requests
1 participant
@williamstein