René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Provide a hint when accidentally calling a module","articleBody":"This is sort of inspired by [PEP 713](https://peps.python.org/pep-0713), but I think it's worth doing whether that PEP is accepted or not.\r\n\r\nWhen somebody attempts to call a module, we can provide a more helpful `TypeError` message than `'module' object is not callable`. Instead, we can check if the module has a callable attribute with the same name:\r\n\r\n```py\r\n\u003e\u003e\u003e import pprint\r\n\u003e\u003e\u003e pprint(thing)\r\nTraceback (most recent call last):\r\n  File \"\u003cstdin\u003e\", line 1, in \u003cmodule\u003e\r\nTypeError: 'module' object is not callable. Did you mean: 'pprint.pprint(...)'?\r\n```\r\n\r\nAs somebody who hits this fairly frequently with modules like `dis` and `datetime`, I think that this error message could reduce some confusion for beginners and friction for experienced users.\r\n\r\nThis is a cold code path, and I assume that this error is the most common reason for hitting it with a module object. So a little extra code (just one branch for non-modules) shouldn't be noticeable at all.\n\n\u003c!-- gh-linked-prs --\u003e\n### Linked PRs\n* gh-103900\n\u003c!-- /gh-linked-prs --\u003e\n","author":{"url":"https://github.com/brandtbucher","@type":"Person","name":"brandtbucher"},"datePublished":"2023-04-26T22:10:08.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/103899/cpython/issues/103899"}