Originally Presented at PyCon 2008, March 13, 2008, Chicago, Illinois.

Revised and updated for Python 3.7, October 29, 2018.

This tutorial discusses various techniques for using generator functions and generator expressions in the context of systems programming. This topic loosely includes files, file systems, text parsing, network programming, and programming with threads.

Presentation Slides (PDF) Also available at https://speakerdeck.com/dabeaz/generator-tricks-for-systems-programmers-version-3-dot-0

Come to Chicago and take a Course.

The examples directory contains various code samples and data files used for the tutorial. The presentation slides also specify a filename. This tutorial assumes the use of Python 3.4 or newer.

All of the example programs should be executed within the examples directory. Certain programs might require additional support programs to be running. This is indicated in the description below.

• nongenlog.py. Calculate the number of bytes transferred in an Apache server log using a simple for-loop. Does not use generators.
• genlog.py. Calculate the number of bytes transferred in an Apache server log using a series of generator expressions.
• makebig.py. Make a large access-log file for performance testing. This will create a file "big-access-log". For the numbers used in the presentation, I used python makebig.py 2000.

• genfind.py. An example of using pathlib and the rglob() method to yield filenames matching a given filename pattern.
• genopen.py. A generator function that yields filenames matching a given filename pattern.
• gencat.py. A generator function that concatenates a sequence of generators into a single sequence.
• gengrep.py. A generator that greps a series of lines for those that match a regex pattern.

• bytesgen.py. Example that finds out how many bytes were transferred for a specific file in a whole directory of log files.
• retuple.py. Parse a sequence of lines into a sequence of tuples using regular expressions.
• redict.py. Parse a sequence of lines into a sequence of dictionaries with named fields.
• fieldmap.py. Remap fields in a sequence of dictionaries.
• linesdir.py. Generate lines from files in a directory.
• apachelog.py. Parse an Apache log file.
• query404.py. Find the set of all documents that are broken (404).
• largefiles.py. Find all requests that transferred over a megabyte.
• largest.py. Find the largest document.
• hosts.py. Find unique host IP addresses.
• downloads.py. Find number of downloads of a specific file.
• robots.py. Find out who has been hitting robots.txt.

• follow.py. Follow a log-file in real-time like tail -f in Unix. To run this program, you need to have a log-file to work with. Run the program runservers.py to start a simulated web-server. This will write a series of log lines for you to follow.
• realtime404.py. Print all 404 requests as they happen in real-time on a log file.

• genreceive.py. Generate clients that connect to a TCP socket.
• genmessages.py. Generate UDP messages.

• genpickle.py. Turn sequences of objects into a sequence of pickles.
• sendto.py. Send a sequence of items to a remote machine via a socket. Uses genpickle above.
• receivefrom.py Receive a sequence of items from a socket. Uses genpickle above.
• genqueue.py. Consume items on a queue.

• genmulti.py. Generate items from more than one generator at once (multiplexing).
• broadcast.py Broadcast a sequence of items to a collection of consumers.
• netsend.py. Send items to another host on the network. Requires a receiver (use receivefrom.py above).
• thrsend.py. Send items to multiple consumer threads.

• gentrace.py. Example of debugging a generator component.
• storelast.py. Store the last value of a generator (for access later in the processing pipeline)
• genshutdown.py. Simple example of shutting down a generator.
• shutdownevt.py. Shutting down a generator with an event.

No sample programs.

• recvcount.py. A co-routine example.
• consumer.py. Co-routine example with a consumer decorator.
• logcoroutine.py. Processing log files with co-routines.

Bug reports and pull requests to the sample code are welcome. Comments to [email protected].