https://github.com/python/cpython/commit/4b5340bb634be2ee2a40242cdf4e3f7a0b6... commit: 4b5340bb634be2ee2a40242cdf4e3f7a0b6c757a branch: 3.7 author: Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com> committer: GitHub <noreply@github.com> date: 2019-04-29T19:26:00-07:00 summary: closes bpo-35329: Change 'Package' to 'package' in accordance with PEP8. (GH-13008) (cherry picked from commit ee0309f3d83ab9ffa02542bcf45ece84f4fb265e) Co-authored-by: Utkarsh Gupta <guptautkarsh2102@gmail.com> files: M Doc/tutorial/modules.rst diff --git a/Doc/tutorial/modules.rst b/Doc/tutorial/modules.rst index fd594fd97af4d..d0a68faa2ee25 100644 --- a/Doc/tutorial/modules.rst +++ b/Doc/tutorial/modules.rst @@ -523,7 +523,7 @@ Although certain modules are designed to export only names that follow certain patterns when you use ``import *``, it is still considered bad practice in production code. -Remember, there is nothing wrong with using ``from Package import +Remember, there is nothing wrong with using ``from package import specific_submodule``! In fact, this is the recommended notation unless the importing module needs to use submodules with the same name from different packages.