Now that we’ve looked at the larger ideas behind modules, let’s turn to a simple example of modules in action. Python modules are easy to create; they’re just files of Python program code, created with your text editor. You don’t need to write special syntax to tell Python you’re making a module; almost any text file will do. Because Python handles all the details of finding and loading modules, modules are also easy to use; clients simply import a module, or specific names a module defines, and use the objects they reference.
To define a module, use
your text editor to type Python code into a text file. Names assigned
at the top level of the module become its attributes (names
associated with the module object), and are exported for clients to
use. For instance, if we type the
def below into a
file called module1.py and import it, we create
a module object with one attribute—the name
printer, which happens to be a reference to a
def printer(x): # Module attribute print x
A word on module filenames: you can call modules just about anything you like, but module filenames should end in a .py suffix if you plan to import them. The .py is technically optional for top-level files that will be run, but not imported; but adding it in all cases makes the file’s type more obvious.
Since module names become variables inside a Python program without the .py, they should also follow the normal variable name rules we learned in ...