-
Notifications
You must be signed in to change notification settings - Fork 53
Convert the specification files to rst format #283
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
Comments
idea:
|
I ended up hacking some quick py file generation at https://github.com/xloem/arrays to work with the spec in the repl help(). I was thinking of making a base class for something that plugged in api implementation fudges based on name matching with existing libraries |
Thanks for sharing @xloem. That may be useful as an intermediate step; I'm hoping we end up with a more normal spec though which uses the numpydoc docstring format. So instead of:
it should look like:
|
The source of the sphinx builder that outputs rst probably reveals what document elements might output that format, but if it's a one-way change a search+replace tool might be simpler. |
@steff456 Now that this tracking issue is complete, can we close this out? |
I'm closing this issue given that all the specification is now in rst 🎉🎉🎉 |
The main goal is to make the specification files more machine readable and enable sphinx extensions like latex to convert into a pdf. This issue will track the changes by markdown file,
API Specification
Design topics
Extensions
The text was updated successfully, but these errors were encountered: