# Stop Using print for Debugging: A 5 Minute Quickstart Guide to Pythons logging Module

<http://inventwithpython.com/blog/2012/04/06/stop-using-print-for-debugging-a-5-minute-quickstart-guide-to-pythons-logging-module/>

- Host: [inventwithpython.com](https://links.thingelstad.xyz/hosts/inventwithpython.com/)
- Saved: April 9, 2012 (2012-04-09T16:22:25Z)
- Record: https://links.thingelstad.xyz/links/bb9db2864c00/
- JSON: https://links.thingelstad.xyz/links/bb9db2864c00.json

## From the page (probably an excerpt, not Jamie's words)

This tutorial is short. To figure out bugs in your code, you might put in print statements/print() calls to display the value of variables. Dont do this. Use the Python logging module.

## Facts

- Kind: [Page](https://links.thingelstad.xyz/kinds/page/)

## Same host

- [Invent Your Own Computer Games with Python](https://links.thingelstad.xyz/links/703dd3acac39/) (inventwithpython.com, December 25, 2012)

## Saved the same week

- [Did everybody see what just happened? The pendulum has swung.](https://links.thingelstad.xyz/links/95e51c8619f4/) (blog.42floors.com, April 9, 2012)
- [Pragmatic Programming Techniques: MongoDb Architecture](https://links.thingelstad.xyz/links/b5d0d105b6e5/) (horicky.blogspot.com, April 9, 2012)
- [How I do my Computing](https://links.thingelstad.xyz/links/e0fe12765d43/) (stallman.org, April 9, 2012)
- [How I Use OmniFocus](https://links.thingelstad.xyz/links/de573440e2e5/) (technicallysimple.com, April 9, 2012)
- [Burnout](https://links.thingelstad.xyz/links/ae92e70f48fb/) (geon.github.io, April 9, 2012)

## Elsewhere

- Wayback Machine: https://web.archive.org/web/*/http://inventwithpython.com/blog/2012/04/06/stop-using-print-for-debugging-a-5-minute-quickstart-guide-to-pythons-logging-module/