You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The x-ref PR is 🤞 wrapping up and I want to document the various possible followups that have cropped up. In an unexplained but very particular order:
standardize usage of optional and keyword-only for optional OR keyword-only arguments.
all arguments to which these apply should be labelled as such
¿ standardize as being parenthesized (optional, keyword-only)
unignore the numpy array subclassing terms (in conf.py)
Implement some sub-package specific glossary terms, e.g. “frame-instance” (as suggested by @adrn)
get all parameters that had to be converted to rst code markup x-ref’ed
Expand input types by making more things “-like” by passing them through their relevant constructors. E.g. more things that only accept an angle should also be able to accept angle-like strings.
Parameter descriptions have a lot of inexactness, like claiming something must be a function, when it can be any callable. Correct this.
Get the x-ref links to look the same as the other links. See Getting started — numpydoc v1.2.dev0 Manual
Similarly, where it is more clear, use typing-like syntax to explain sub-types: dict[str, float] over "dict with string keys and float values"
finalize array shape syntax and how it applies to non-NumPy arrays. What is a (3,2) tuple? or even what is the difference between 2 tuple and (2,) tuple?
Copied from https://community.openastronomy.org/t/abcd-always-be-code-documenting/56/2?u=nstarman
The x-ref PR is 🤞 wrapping up and I want to document the various possible followups that have cropped up. In an unexplained but very particular order:
ndarray
is preferred, see this comment by @dhomeier ]The text was updated successfully, but these errors were encountered: