-
Notifications
You must be signed in to change notification settings - Fork 121
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
multiple definitions for std:label:python--m-build--v #795
Comments
Well, this is interesting. When updating the intersphinx mapping to the new location, the warning goes away, so it appears to be a sphinx bug. The warning about the multiple definitions no longer appears, suggesting that Sphinx is incorrectly detecting multiple definitions due to the redirection. That's a yak I'm not planning to shave today. |
I'm re-opening, since it appears that the docs build in RTD doesn't match the docs in GitHub. Latest is v1.0.2: But there's no v1.0.2 in the repo: |
Oh! I see my mistake now.
|
After getting the correct intersphinx target configured without the redirection, the error message returns.
Maybe there's something about the way the hosting is configured that causes the multiple definitions? |
When I download the inventory and inspect it, I can see that the "multiple definitions" are actually distact, but they vary only by case:
|
I'm guessing those labels are generated by the use of sphinx-argparse-cli. |
Maybe it's not a sphinx-argparse-cli issue. Those two labels are unique if compared case-sensitive. According to Gemini (which I barely trust), HTML labels are case sensitive, so those two labels are in fact distinct. It's sphinx that's improperly warning when two labels exist that vary only by case. |
In sphinx-doc/sphinx#12585, users report a recent emergent issue with Sphinx 7.4.0, and indeed, if I downgrade to Sphinx 7.3.7, the error goes away, so it's probably not an issue with build or with sphinx-argparse-cli, but with Sphinx 7.4. |
Sphinx contributor / author of this warning message here. It is intended to flag potential problems in Intersphinx If it is possible to adjust PS: For an interim workaround if you do want to upgrade Sphinx while this warning message exists, you can suppress these warnings following some guidance from here (quoting @AA-Turner):
|
In pypa/setuptools#4474 I report an issue where in the past few days, Setuptools docs builds have started failing due to this warning (treated as error):
I can see that the docs for build haven't changed in the past few weeks.
It's preceded by this notice:
That makes me wonder if maybe the
pypa-build
was recently updated to redirect and previously, Setuptools was linking to a stale site and that's why the issue has surfaced now.The text was updated successfully, but these errors were encountered: