Program Arcade GamesWith Python And Pygame
Dutch - Nederlands
Hungarian - Magyar
Portuguese - Português
Russian - Русский
Spanish - Español
Turkish - Türkçe
A library is a collection of code for functions and classes. Often, these libraries are written by someone else and brought into the project so that the programmer does not have to “reinvent the wheel.” In Python the term used to describe a library of code is module.
By using import pygame and import random, the programs created so far have already used modules. A library can be made up of multiple modules that can be imported. Often a library only has one module, so these words can sometimes be used interchangeably.
Modules are often organized into groups of similar functionality. In this class programs have already used functions from the math module, the random module, and the pygame library. Modules can be organized so that individual modules contain other modules. For example, the pygame module contains submodules for pygame.draw, pygame.image, and pygame.mouse.
Modules are not loaded unless the program asks them to. This saves time and computer memory. This chapter shows how to create a module, and how to import and use that module.
There are three major reasons for a programmer to create his or her own libraries:
- It breaks the code into smaller, easier to use parts.
- It allows multiple people to work on a program at the same time.
- The code written can be easily shared with other programmers.
Some of the programs already created in this book have started to get rather long. By separating a large program into several smaller programs, it is easier to manage the code. For example, in the prior chapter's sprite example, a programmer could move the sprite class into a separate file. In a complex program, each sprite might be contained in its own file.
If multiple programmers work on the same project, it is nearly impossible to do so if all the code is in one file. However, by breaking the program into multiple pieces, it becomes easier. One programmer could work on developing an “Orc” sprite class. Another programmer could work on the “Goblin” sprite class. Since the sprites are in separate files, the programmers do not run into conflict.
Modern programmers rarely build programs from scratch. Often programs are built from parts of other programs that share the same functionality. If one programmer creates code that can handle a mortgage application form, that code will ideally go into a library. Then any other program that needs to manage a mortgage application form at that bank can call on that library.
In this example we will break apart a short program into multiple files. Here we have a function in a file named test.py, and a call to that function:
# Foo function def foo(): print("foo!") # Foo call foo()
Yes, this program is not too long to be in one file. But if both the function and the main program code were long, it would be different. If we had several functions, each 100 lines long, it would be time consuming to manage that large of a file. But for this example we will keep the code short for clarity.
We can move the foo function out of this file. Then this file would be left with only the main program code. (In this example there is no reason to separate them, aside from learning how to do so.)
To do this, create a new file and copy the foo function into it. Save the new file with the name my_functions.py. The file must be saved to the same directory as test.py.
# Foo function def foo(): print("foo!")
# Foo call that doesn't work foo()
Unfortunately it isn't as simple as this. The file test.py does not know to go and look at the my_functions.py file and import it. We have to add the command to import it:
# Import the my_functions.py file import my_functions # Foo call that still doesn't work foo()
That still doesn't work. What are we missing? Just like when we import pygame, we have to put the package name in front of the function. Like this:
# Import the my_functions.py file import my_functions # Foo call that does work my_functions.foo()
This works because my_functions. is prepended to the function call.
A program might have two library files that need to be used. What if the libraries had functions that were named the same? What if there were two functions named print_report, one that printed grades, and one that printed an account statement? For instance:
def print_report(): print("Student Grade Report:" )
def print_report(): print("Financial Report:" )
How do you get a program to specify which function to call? Well, that is pretty easy. You specify the namespace. The namespace is the work that appears before the function name in the code below:
import student_functions import financial_functions student_functions.print_report() financial_functions.print_report()
So now we can see why this might be needed. But what if you don't have name collisions? Typing in a namespace each and every time can be tiresome. You can get around this by importing the library into the local namespace. The local namespace is a list of functions, variables, and classes that you don't have to prepend with a namespace. Going back to the foo example, let's remove the original import and replace it with a new type of import:
# import foo from my_functions import * foo()
This works even without my_functions. prepended to the function call. The asterisk is a wildcard that will import all functions from my_functions. A programmer could import individual ones if desired by specifying the function name.
When working with Python, it is possible to use many libraries that are built into Python.
Take a look at all the libraries that are available here:
It is possible to download and install other libraries. There are libraries that work with the web, complex numbers, databases, and more.
- Pygame: The library used to create games.
- wxPython: Create GUI programs, with windows, menus, and more.
- pydot: Generate complex directed and non-directed graphs
- NumPy: Sophisticated library for working with matrices.
A wonderful list of Python libraries and links to installers for them is available
Going through lists of libraries that are available can help you brainstorm what types of programs you can create. Most programming involves assembling large parts, rather than writing everything from scratch.
Here is an example of what you can do with the third party library “Matplotlib.” If you are only interested in games you can skip this section, but my hope is that looking at this can give you an idea of what is possible by using libraries.
Matplotlib depends on other libraries. So to install, you need all the libraries below. Don't worry, they are all small and easy downloads.
To start with, here is the code to create a simple line chart with four values:
""" Line chart with four values. The x-axis defaults to start at zero. """ import matplotlib.pyplot as plt y = [1, 3, 8, 4] plt.plot(y) plt.ylabel('Element Value') plt.xlabel('Element Number') plt.show()
The x value for Example 1, Figure 15.1 defaults to start at zero. You can change this default and specify your own x values to go with the y values. See Example 2 below.
""" Line chart with four values. The x-axis values are specified as well. """ import matplotlib.pyplot as plt x = [1, 2, 3, 4] y = [1, 3, 8, 4] plt.plot(x, y) plt.ylabel('Element Value') plt.xlabel('Element') plt.show()
It is trivial to add another data series to the graph.
""" This example shows graphing two different series on the same graph. """ import matplotlib.pyplot as plt x = [1, 2, 3, 4] y1 = [1, 3, 8, 4] y2 = [2, 2, 3, 3] plt.plot(x, y1) plt.plot(x, y2) plt.ylabel('Element Value') plt.xlabel('Element') plt.show()
You can add a legend to the graph:
import matplotlib.pyplot as plt x = [1, 2, 3, 4] y1 = [1, 3, 8, 4] y2 = [2, 2, 3, 3] plt.plot(x, y1, label = "Series 1") plt.plot(x, y2, label = "Series 2") legend = plt.legend(loc='upper center', shadow=True, fontsize='x-large') legend.get_frame().set_facecolor('#00FFCC') plt.ylabel('Element Value') plt.xlabel('Element') plt.show()
You can add annotations to a graph:
""" Annotating a graph """ import matplotlib.pyplot as plt x = [1, 2, 3, 4] y = [1, 3, 8, 4] plt.annotate('Here', xy = (2, 3), xycoords = 'data', xytext = (-40, 20), textcoords = 'offset points', arrowprops = dict(arrowstyle="->", connectionstyle="arc,angleA=0,armA=30,rad=10"), ) plt.plot(x, y) plt.ylabel('Element Value') plt.xlabel('Element') plt.show()
Don't like the default lines styles for the graph? That can be changed by adding a third parameter to the plot command.
""" This shows how to set line style and markers. """ import matplotlib.pyplot as plt x = [1, 2, 3, 4] y1 = [1, 3, 8, 4] y2 = [2, 2, 3, 3] # First character: Line style # One of '-', '--', '-.', ':', 'None', ' ', ” # Second character: color # http://matplotlib.org/1.4.2/api/colors_api.html # Third character: marker shape # http://matplotlib.org/1.4.2/api/markers_api.html plt.plot(x, y1, '-ro') plt.plot(x, y2, '--g^') plt.ylabel('Element Value') plt.xlabel('Element') plt.show()
A bar chart is as easy as changing plot to bar.
""" How to do a bar chart. """ import matplotlib.pyplot as plt x = [1, 2, 3, 4] y = [1, 3, 8, 4] plt.bar(x, y) plt.ylabel('Element Value') plt.xlabel('Element') plt.show()
You can add labels to axis values.
""" How to add x axis value labels. """ import matplotlib.pyplot as plt x = [1, 2, 3, 4] y = [1, 3, 8, 4] plt.plot(x, y) labels = ['Frogs', 'Hogs', 'Bogs', 'Slogs'] plt.xticks(x, labels) plt.ylabel('Element Value') plt.xlabel('Element') plt.show()
You can graph functions as well. This uses a different package called numpy to graph a sine function.
""" Using the numpy package to graph a function over a range of values. """ import numpy import matplotlib.pyplot as plt x = numpy.arange(0.0, 2.0, 0.001) y = numpy.sin(2 * numpy.pi * x) plt.plot(x, y) plt.ylabel('Element Value') plt.xlabel('Element') plt.show()
You can fill in a graph if you like.
""" Using 'fill' to fill in a graph """ import numpy import matplotlib.pyplot as plt x = numpy.arange(0.0, 2.0, 0.001) y = numpy.sin(2 * numpy.pi * x) plt.plot(x, y) # 'b' means blue. 'alpha' is the transparency. plt.fill(x, y, 'b', alpha=0.3) plt.ylabel('Element Value') plt.xlabel('Element') plt.show()
Create a pie chart.
""" Create a pie chart """ import matplotlib.pyplot as plt # Labels for the pie chart labels = ['C', 'Java', 'Objective-C', 'C++', 'C#', 'PHP', 'Python'] # Sizes for each label. We use this to make a percent sizes = [17, 14, 9, 6, 5, 3, 2.5] # For list of colors, see: # https://github.com/matplotlib/matplotlib/blob/master/lib/matplotlib/colors.py colors = ['yellowgreen', 'gold', 'lightskyblue', 'lightcoral', 'darkcyan', 'darksage', 'rosybrown'] # How far out to pull a slice. Normally zero. explode = (0, 0.0, 0, 0, 0, 0, 0.2) # Set aspect ratio to be equal so that pie is drawn as a circle. plt.axis('equal') # Finally, plot the chart plt.pie(sizes, explode=explode, labels=labels, colors=colors, autopct='%1.1f%%', shadow=True, startangle=90) plt.show()
You can do really fancy things, like pull stock data from the web and create a candlestick graph for Apple Computer:
""" Create a candlestick chart for a stock """ import matplotlib.pyplot as plt from matplotlib.dates import DateFormatter, WeekdayLocator,\ DayLocator, MONDAY from matplotlib.finance import quotes_historical_yahoo_ohlc, candlestick_ohlc # Grab the stock data between these dates date1 = (2014, 10, 13) date2 = (2014, 11, 13) # Go to the web and pull the stock info quotes = quotes_historical_yahoo_ohlc('AAPL', date1, date2) if len(quotes) == 0: raise SystemExit # Set up the graph fig, ax = plt.subplots() fig.subplots_adjust(bottom=0.2) # Major ticks on Mondays mondays = WeekdayLocator(MONDAY) ax.xaxis.set_major_locator(mondays) # Minor ticks on all days alldays = DayLocator() ax.xaxis.set_minor_locator(alldays) # Format the days weekFormatter = DateFormatter('%b %d') # e.g., Jan 12 ax.xaxis.set_major_formatter(weekFormatter) ax.xaxis_date() candlestick_ohlc(ax, quotes, width=0.6) ax.autoscale_view() plt.setp(plt.gca().get_xticklabels(), rotation=45, horizontalalignment='right') plt.show()
There are many more things that can be done with matplotlib. Take a look at the thumbnail gallery:
You are not logged in. Log in here and track your progress.
|About||Buy the Book||Help Translate||My College||My Twitter||Updates|
English version by Paul Vincent Craven
Spanish version by Antonio Rodríguez Russian version by Vladimir Slav
Turkish version by Güray Yildirim
Portuguese version by Armando Marques Sobrinho and Tati Carvalho
Dutch version by Frank Waegeman
Hungarian version by Nagy Attila
French version by Franco Rossi