This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: Clarify that __path__ can't be set to just anything
Type: Stage: resolved
Components: Documentation Versions: Python 3.8, Python 3.7, Python 3.6
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: brett.cannon Nosy List: brett.cannon
Priority: normal Keywords: easy, patch

Created on 2018-04-13 19:08 by brett.cannon, last changed 2022-04-11 14:58 by admin. This issue is now closed.

Pull Requests
URL Status Linked Edit
PR 6554 merged brett.cannon, 2018-04-20 21:11
PR 6557 merged miss-islington, 2018-04-20 23:35
PR 6556 merged miss-islington, 2018-04-20 23:35
Messages (1)
msg315256 - (view) Author: Brett Cannon (brett.cannon) * (Python committer) Date: 2018-04-13 19:08
https://docs.python.org/3/reference/import.html#module-path says that "regardless of its value", __path__'s mere existence is key. But then later the docs say "__path__ must be an iterable of strings, but it may be empty". Technically the latter is more accurate, so the docs should get touched up to match itself better.
History
Date User Action Args
2022-04-11 14:58:59adminsetgithub: 77457
2018-04-20 23:35:47miss-islingtonsetpull_requests: + pull_request6253
2018-04-20 23:35:37miss-islingtonsetpull_requests: + pull_request6252
2018-04-20 23:33:43brett.cannonsetstatus: open -> closed
resolution: fixed
stage: patch review -> resolved
2018-04-20 21:11:25brett.cannonsetkeywords: + patch
stage: needs patch -> patch review
pull_requests: + pull_request6250
2018-04-13 19:08:16brett.cannoncreate