Docs: split builtins to their own page from library

[nedbat]

We've talked about separating the built-ins from the stdlib modules, since "dict" (for example) isn't part of the stdlib.

I think I took care of all the places the pages are referenced, but the non-HTML builds are new to me, so I might have missed something.

I tried to make the intro paragraphs and pages useful, and avoided over-editing them.

[nedbat]

Also: is this NEWS-worthy?

[StanFromIreland]

Also: is this NEWS-worthy?

I don't see a need for one here, I think the docs speak for themselves.

[read-the-docs-community]

Documentation build overview

📚 cpython-previews | 🛠️ Build #34302495 | 📁 Comparing fe39fea against main (852381e)

  🔍 Preview build  

8 files changed · + 1 added · ± 7 modified

+ Added

• library/builtin-index.html

± Modified

• index.html
• extending/index.html
• library/index.html
• library/intro.html
• reference/index.html
• tutorial/index.html
• whatsnew/3.16.html

[hugovk]

Shall we name the new Doc/library/builtin-index.rst as Doc/builtins/index.rst instead?

Then instead of:

• https://docs.python.org/3/library/builtins-index.html

We get a neater:

• https://docs.python.org/3/builtins/index.html
• aka https://docs.python.org/3/builtins/

This PR can still reference the builtin stuff in their current location, and a followup could move the relevant files and deal with redirects:

• Doc/library/functions.rst -> Doc/builtins/functions.rst
• Doc/library/stdtypes.rst -> Doc/builtins/stdtypes.rst
• Doc/library/constants.rst -> Doc/builtins/constants.rst
• Doc/library/exceptions.rst -> Doc/builtins/exceptions.rst
• Doc/library/threadsafety.rst -> Doc/builtins/threadsafety.rst
• Doc/library/time-complexity.rst -> Doc/builtins/time-complexity.rst

[hugovk]

Use sentence case for headers:

https://devguide.python.org/documentation/style-guide/#capitalization

Suggested change

	##################################
	Built-in Functions and Classes
	##################################
	##################################
	Built-in functions and classes
	##################################

But we have more than functions and classes in here, also constants and thread-safety and time-complexity appendices.

Perhaps match what you put on the front page?

Suggested change

	##################################
	Built-in Functions and Classes
	##################################
	######################
	Built-in reference
	######################

And plural?

Suggested change

	##################################
	Built-in Functions and Classes
	##################################
	#######################
	Built-ins reference
	#######################

[hugovk]

Suggested change

	The built-ins also includes functions and exceptions --- objects that can
	The built-ins also include functions and exceptions --- objects that can

[hugovk]

Suggested change

	the web development. Some modules are available in all versions and ports of
	web development. Some modules are available in all versions and ports of

[hugovk]

Suggested change

	semantics of the Python language, and :ref:`builtin-index` describes
	semantics of the Python language, and :ref:`builtin-index` describes

[hugovk]

Should we remove this sentence? The intro already pointed there.

Suggested change

	and read a section or two. Regardless of the order in which you
	read the sections of this manual, it helps to start with chapter
	:ref:`built-in-funcs`, as the remainder of the manual assumes familiarity with
	this material.
	and read a section or two.

Or update it to something along the lines of?

Suggested change

	and read a section or two. Regardless of the order in which you
	read the sections of this manual, it helps to start with chapter
	:ref:`built-in-funcs`, as the remainder of the manual assumes familiarity with
	this material.
	and read a section or two. Regardless of the order in which you
	read the sections of this manual, it helps to first read
	:ref:`built-in-funcs` in :ref:`builtin-index`, as this manual assumes
	familiarity with that material.

[hugovk]

Suggested change

	<li class="biglink"><a class="biglink" href="{{ pathto("library/builtin-index") }}">{% trans %}Built-in reference{% endtrans %}</a><br>
	<li class="biglink"><a class="biglink" href="{{ pathto("library/builtin-index") }}">{% trans %}Built-ins reference{% endtrans %}</a><br>

[hugovk]

Copied from stdlib index, but no modules here.

Suggested change

	:numbered: can be enabled on a per-module basis.
	:numbered: can be enabled on a per-page basis.

[hugovk]

Nit: wrap to ~80 cols.

[StanFromIreland]

Also, you need to update the What Now? page in the tutorial.

I concur with Hugo, splitting this into a separate directory would be nicer. We can do redirects at client side (using one of the various Sphinx extensions) or sever side (by configuring them in python/psf-salt).

[StanFromIreland]

I don't think we should drop "non-essential" what about everything documented in the datamodel?