[issue36908] "This module is always available" is confusing

Mariatta Wijaya added the comment: Thanks all. I've backported the change to 3.7. I think this is good to be closed. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: +Python 3.7, Python 3.8, Python 3.9 ___

[issue36908] "This module is always available" is confusing

miss-islington added the comment: New changeset 740a7cde9c0af5a237a7f6525b38d65a83f4fbf1 by Miss Islington (bot) in branch '3.7': bpo-36908: 'This module is always available' isn't helpful. (GH-13297) https://github.com/python/cpython/commit/740a7cde9c0af5a237a7f6525b38d65a83f4fbf1

[issue36908] "This module is always available" is confusing

Change by miss-islington : -- pull_requests: +13304 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36908] "This module is always available" is confusing

Kushal Das added the comment: New changeset 6faad355db6c2bd4a0ade7868f245b42c04f5337 by Kushal Das (Ned Batchelder) in branch 'master': bpo-36908: 'This module is always available' isn't helpful. (#13297) https://github.com/python/cpython/commit/6faad355db6c2bd4a0ade7868f245b42c04f5337

[issue36908] "This module is always available" is confusing

Kushal Das added the comment: In future we should do the similar change for any module. This will be helpful for new beginners. -- nosy: +kushal.das ___ Python tracker ___

[issue36908] "This module is always available" is confusing

Emmanuel Arias added the comment: > More useful would be to annotate those modules that might not be importable, > with a reason why. yes, that is more reasonable. :-D -- ___ Python tracker

[issue36908] "This module is always available" is confusing

Emmanuel Arias added the comment: I agree. What about create a section (or subsection?) or note with the text: ``` The next modules: sys, math ... are always available. This mean that ... ``` ? -- nosy: +eamanu ___ Python tracker

[issue36908] "This module is always available" is confusing

Ned Batchelder added the comment: There are hundreds of modules that are always importable. The majority of the standard library is always importable. More useful would be to annotate those modules that might not be importable, with a reason why. --

[issue36908] "This module is always available" is confusing

Ned Batchelder added the comment: Looks like these modules describe themselves as always available: _thread, sys, threading, time. Notice that the built-ins are also described as "always available", which is the meaning we're trying to move math away from (you can use them without

[issue36908] "This module is always available" is confusing

Ned Batchelder added the comment: If we want to keep it, how about "it can always be imported."? Though I still wonder whether this is worth it. Are we going to annotate all of the always-available modules with this notation? -- ___ Python

[issue36908] "This module is always available" is confusing

Mariatta Wijaya added the comment: I agree the wording "is always available" is quite ambiguous. It's just that we use this phrase pretty much everywhere... Example: First paragraph of https://docs.python.org/3/library/sys.html "It is always available."

[issue36908] "This module is always available" is confusing

Change by Ned Batchelder : -- keywords: +patch pull_requests: +13207 stage: -> patch review ___ Python tracker ___ ___

[issue36908] "This module is always available" is confusing

New submission from Ned Batchelder : The math and cmath modules say this in their docs: "This module is always available." This lead a beginner to believe they didn't need to be imported. Nearly the entire standard library is always available in this sense (they can be imported). This