-
-
Notifications
You must be signed in to change notification settings - Fork 165
Unnecessary renaming of references #114
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
This is not necessary. The initial de-duplication script used numerical references for simplicity, but there's no reason why that has to be the case. |
@stefanv - ok, thanks! Just to be clear, in this case this may actually be a regression since in the rest of the docstring the reference is referred to by |
I just read the code, and it does special case for anything other than numeric references. I guess it will transform it to something like |
Basically I think it doesn't rename the |
@astrofrom shouldn't you be referring to it by Still, there's no way to determine if there will be a duplicate and also mangle the references in a single pass over the docstrings. We could allow the first appearance of a reference to not be mangled, if there is little risk in tracking all references ever mentioned. We could also insert some delimiter between the existing reference and the added number in the non-numeric case. |
The mangling here should only affect those references that are listed with |
Numpydoc now renames references even when this is not needed. For example, a reference originally called
Scargle2012
has now been renamed in the Astropy docs:Is this intentional? Should we be using only numerical reference names? Or is it a bug since there are no duplicates of this reference so no reason to rename it?
The text was updated successfully, but these errors were encountered: