-
-
Notifications
You must be signed in to change notification settings - Fork 166
Mention more prominently that section ordering matters #68
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
Or explicitly drop the order as a requirement ;) |
Having a standard ordering of sections in docstrings within and between projects is a good thing - consistency matters. Why would we want to drop this requirement? |
It seems a bit weird to have a required order on optional sections. I agree that for some sections the order make lots of sense (should not put To be clear, I will be perfectly happy with the outcome of 'It is an intentional choice to have a fixed order' from this discussion (so as to not waste even more of everyone's time). |
I don't feel strongly about the optional section ordering. I'd be okay
with that remaining flexible.
|
I'm changing my opinion on this one after other discussion. See #78 |
My vote would be to optionally, on-by-default warn if optional sections are not ordered with the "standard" ordering. |
Fixes numpy#68 assuming we do not also want a warning
In order to open this to another contributor, I'm making a new issue instead. |
Mention this in HOWTO_DOCUMENT.txt
The text was updated successfully, but these errors were encountered: