We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I think we would be able to generate import statements from the # optional (or # needs - #35779) annotations.
import
# optional
# needs
The necessary cross-referencing information is going to be in sage.features.sagemath. See:
# optional - sage....
sage -t
sage -fixdoctests
This would also have the huge advantage to support users that want to use sage as a normal python package without loading the sage environment.
+1.
I could imagine that the code blocks in the formatted HTML could offers tabs for different views, as is done for example in https://setuptools.pypa.io/en/latest/userguide/package_discovery.html: The example in monolithic Sage (goes through preparser, no imports), and the example in plain Python (some prettified version of the preparsed example + imports). This would also address @williamstein's comment (https://groups.google.com/g/sage-devel/c/utA0N1it0Eo/m/79aD4-RQAAAJ)
Originally posted by @mkoeppe in #35750 (comment)
The text was updated successfully, but these errors were encountered:
The sphinx-inline-tabs package for this type of presentation in the HTML documentation is added in #37056
Sorry, something went wrong.
f81e21f
Successfully merging a pull request may close this issue.
I think we would be able to generate
import
statements from the# optional
(or# needs
- #35779) annotations.The necessary cross-referencing information is going to be in sage.features.sagemath.
See:
# optional - sage....
doctest tags, extendsage -t
andsage -fixdoctests
for modularization tasks #35749 (needs review)(doc preview: https://deploy-preview-35749--sagemath-tobias.netlify.app/reference/misc/sage/features/sagemath.html#sage.features.sagemath.all_features)
+1.
I could imagine that the code blocks in the formatted HTML could offers tabs for different views, as is done for example in https://setuptools.pypa.io/en/latest/userguide/package_discovery.html: The example in monolithic Sage (goes through preparser, no imports), and the example in plain Python (some prettified version of the preparsed example + imports). This would also address @williamstein's comment (https://groups.google.com/g/sage-devel/c/utA0N1it0Eo/m/79aD4-RQAAAJ)
Originally posted by @mkoeppe in #35750 (comment)
The text was updated successfully, but these errors were encountered: