Skip to content

gh-149902: Remove dead packaging docs link and add a new secition for external resources #150030

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.

Sign up for GitHub

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

Open
miameows wants to merge 6 commits into
base: main
Choose a base branch
from
+12 −2
Open

gh-149902: Remove dead packaging docs link and add a new secition for external resources #150030

Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
cabca53
Remove link to unused distribution docs page
miameows May 18, 2026
314a97e
Add "Other resources" section to docs front page
miameows May 18, 2026
26a0478
Remove /en/latest from links in "Other Resources" section of docs
miameows May 18, 2026
265ab70
Remove extra newline from docs index
miameows May 18, 2026
94cd6ab
fix docs table typo: widht -> width
miameows May 19, 2026
7187979
fix docs table typo: widht -> width
miameows May 19, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 12 additions & 2 deletions Doc/tools/templates/indexcontent.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,8 +38,6 @@ <h1>{{ docstitle|e }}</h1>
</td><td width="50%">
<p class="biglink"><a class="biglink" href="{{ pathto("installing/index") }}">{% trans %}Installing Python modules{% endtrans %}</a><br>
<span class="linkdescr">{% trans %}Third-party modules and PyPI.org{% endtrans %}</span></p>
<p class="biglink"><a class="biglink" href="{{ pathto("distributing/index") }}">{% trans %}Distributing Python modules{% endtrans %}</a><br>
<span class="linkdescr">{% trans %}Publishing modules for use by other people{% endtrans %}</span></p>
<p class="biglink"><a class="biglink" href="{{ pathto("extending/index") }}">{% trans %}Extending and embedding{% endtrans %}</a><br>
<span class="linkdescr">{% trans %}For C/C++ programmers{% endtrans %}</span></p>
<p class="biglink"><a class="biglink" href="{{ pathto("c-api/index") }}">{% trans %}Python's C API{% endtrans %}</a><br>
Expand All @@ -51,6 +49,18 @@ <h1>{{ docstitle|e }}</h1>
</td></tr>
</table>

<p><strong>{% trans %}Other resources:{% endtrans %}</strong></p>
Copy link
Copy Markdown
Member

@StanFromIreland StanFromIreland May 18, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

With this we'll have two "Other resources" sections, one in the sidebar and one here, why not add these to the existing one?

Copy link
Copy Markdown
Member

@JelleZijlstra JelleZijlstra May 18, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The "Other resources" section also has two links to the deprecated Python wiki, maybe we should drop those and link to packaging.python.org and typing.python.org instead.

Copy link
Copy Markdown
Member

@hugovk hugovk May 19, 2026 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need both "Other resources" sections?

If yes, should they both contain the same things?

If not, which shall we remlve?

Perhaps the wiki books link could be replaced with
https://www.pythondiscord.com/resources/?type=book or https://pythonbooks.org/ ?

See also #148998 for more general wiki cleanup.

Copy link
Copy Markdown
Contributor Author

@miameows miameows May 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm in favor of removing the other section if it links to outdated content

Copy link
Copy Markdown
Contributor Author

@miameows miameows May 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the placement of this new section should be fairly prominent, considering it contains a link that was (indirectly) already featured front and center. I think it's helpful to have a "signpost" of sorts so users who do a web search for "Python documentation" can easily find related resources without having to look at the small text in the sidebar. I'm of the opinion that sidebars are for navigation of complex hierarchies, not holding content

Copy link
Copy Markdown
Member

@nedbat nedbat May 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree that the sidebar is serving two purposes now which could be confusing. If straightening that out expands the scope too much, we can continue the discussion in a subsequent PR.

<table class="contentstable" align="center"><tr>
<td width="50%">
<p class="biglink"><a class="biglink" href="https://packaging.python.org">{% trans %}Python Packaging User Guide{% endtrans %}</a><br>
<span class="linkdescr">{% trans %}A collection of resources relating to Python packaging{% endtrans %}</span></p>
</td>
<td width="50%">
<p class="biglink"><a class="biglink" href="https://typing.python.org">{% trans %}Static Typing with Python{% endtrans %}</a><br>
<span class="linkdescr">{% trans %}Information and guides about Python type safety{% endtrans %}</span></p>
</td></tr>
</table>

<p><strong>{% trans %}Indices, glossary, and search:{% endtrans %}</strong></p>
<table class="contentstable" align="center"><tr>
<td width="50%">
Expand Down
Loading