the library code is self-contained and well documented (at least in most cases it issome developers might feel that they never need to look at the library codeand they're right to some degree -you never have to look at the library code in order to use it you might want to view the library codethoughto ensure that you understand how the code works in additionthe library code can teach you new programming techniques that you might not otherwise discover soviewing the library code is optionalbut it can be helpful the one thing you do need to know how to do is obtain and use the python library documentation this shows you how to obtain and use the library documentation as part of the application-creation process creating code groupings it' important to group like pieces of code together to make the code easier to usemodifyand understand as an application growsmanaging the code found in single file becomes harder and harder at some pointthe code becomes impossible to manage because the file has become too large for anyone to work with the term code is used broadly in this particular case code groupings can includeclasses functions variables runnable code the collection of classesfunctionsvariablesand runnable code within module is known as attributes module has attributes that you access by that attribute' name later sections in this discuss precisely how module access works the runnable code can actually be written in language other than python for exampleit' somewhat common to find modules that are written in / +instead of python the reason that some developers use runnable code is to make the python application fasterless resource intensiveand better able to use particular platform' resources howeverusing runnable code comes with the downside of making your application less portable (able to run on other platformsunless you have runnable code modules for each platform