PrettyTable

PrettyTable is a simple Python library designed to make it quick and easy to represent tabular data in visually appealing ASCII tables. It was inspired by the ASCII tables used in the PostgreSQL shell psql. PrettyTable allows for selection of which columns are to be printed, independent alignment of columns (left or right justified or centred) and printing of "sub-tables" by specifying a row range.

PrettyTable has moved!

As of PrettyTable 0.5 (released May 26, 2009), PrettyTable development has moved to a Google code project. All future releases, documentation, etc. will be published at that page and not at this one, so please update your bookmarks! PrettyTable was an unexpected hit and quickly outgrew the sorts of facilities I could easily provide myself. The Google code page features a Wiki for documentation, three "Google groups" (mailing lists, basically) and a web-browsable Subversion repository. Check it out!

Links to old pages associated with PrettyTable 0.1 through 0.4 are maintained below for historical interest.

Added padding_width option to control the number of spaces between the vertical line rules at the edges of a column and its content. This can be set as a keyword argument to the constructor or after instantiation using the set_padding_width method. The value is set to 1 by defaut. If your table is too wide for a small screen with this value, setting it to 0 might help you squeeze it in.

Thanks to Chris Clark for contributing a patch against 0.2.1 to add this feature!

This is a bug fix release to take care of some serious problems in 0.2, which was obviously released with insufficient testing!

Caching no longer breaks when using the printt(fields=[...]) syntax. The list of fields was not hashable and hence could not be used as a dictionary key. I fixed this using the output of the cPickle module's dumps function as the dictionary key instead.

Horizontal lines are now the appropriate length when the above syntax is used.

Thanks to Julien Koesten for reporting these bugs and testing the fixes almost immediately after the release of 0.2!