string module link to source code is broken

[alexomics]

Documentation

The links to the source code for the string module on for both python 3.14 and 3.15 are broken. They incorrectly point to the previous module location Lib/string.py not Lib/string/__init__.py.

Linked PRs

• gh-141007: update string module source code link #141008
• [3.14] gh-141007: update string module source code link (GH-141008) #141030

[StanFromIreland]

IMO it should link to Lib/string/ and not Lib/string/__init__.py.

[alexomics]

I've followed the convention that other modules e.g. json and logging use

[StanFromIreland]

Pointing to the folder is done by zoneinfo, idle(lib) and venv, to note three :-)

[alexomics]

I agree there is a split/lack of convention here I may have been lucky with my quick look 😅

I think in this scenario linking to __init__.py preserves the previous behaviour that the source code link had - linking to the actual code/file that is being referenced.

I took a look at them all:

__init__.py:

1. collections
2. dbm
3. email
4. html
5. http
6. importlib
7. json
8. logging
9. tkinter
10. unittest

Folder:

1. ctypes
2. curses
3. ensurepip
4. idlelib
5. multiprocessing
6. pathlib
7. re
8. sqlite3
9. tomllib
10. urllib
11. venv
12. wsgiref
13. xml
14. zipfile
15. zoneinfo

[terryjreedy]

If module.__init__.py is purely a 'dummy' to make a multi-implementation-file package importable as a module, as with idlelib for IDLE, the link should be to the directory. If module.__init__ is the implementation file, and other directory contents (other than __main__.py) are directories for submodules, as with tkinter, or submodule files, then it should get the link. The new string directory has the former string.py renamed as __init__.py and a new templatelib.py submodule file, so I agree with the PR and will merge it. [EDIT: the two previous sentences.]

I think the zoneinfo doc properly links to the directory as the implementation is spread over three privately-named files.
I think venv might link to its __init__ as the scripts subdirectory has data (OS-specifics) for the implementation in __init__.py.

EDIT: when __init__.py is displayed, it is trivial to back up to the directory to see what else it has -- just click on the module name on the gh-generated page.

Checking other modules, discussing on the core discord, and formulating the above as a guideline to be added to the devguide would be separate projects.