[issue33340] Inaccurate docs on `import` behaviour

Change by Cheryl Sabella : -- nosy: +brett.cannon type: behavior -> enhancement versions: +Python 3.8 -Python 3.6 ___ Python tracker ___ ___

[issue33340] Inaccurate docs on `import` behaviour

Change by Karthikeyan Singaravelan : -- nosy: +xtreak ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:/

[issue33340] Inaccurate docs on `import` behaviour

Eric V. Smith added the comment: If you have a suggested improvement, please create a pull request. Thanks! -- ___ Python tracker ___ __

[issue33340] Inaccurate docs on `import` behaviour

sam_b added the comment: Thanks, I thought it might be something like that. Would it be worth clarifying the distinction in the docs? It was certainly surprising to me that `import time` and `import logging` behave differently. -- ___ Python tracke

[issue33340] Inaccurate docs on `import` behaviour

Eric V. Smith added the comment: "built-in modules" has the specific meaning of modules that are compiled in to the python executable. It doesn't mean modules in the standard library. See https://docs.python.org/3.6/library/sys.html#sys.builtin_module_names Python 3.6.4 (default, Jan 7 2018,

[issue33340] Inaccurate docs on `import` behaviour

New submission from sam_b : The docs https://docs.python.org/3/tutorial/modules.html#the-module-search-path describe: > When a module named spam is imported, the interpreter first searches for a > built-in module with that name. If not found, it then searches for a file > named spam.py in a l