PrettyTable 0.7 released

14 views
Skip to first unread message

Luke Maurits

unread,
Feb 17, 2013, 1:20:04 PM2/17/13
to prettytabl...@googlegroups.com
Hi PrettyTable users,

I am pleased to announce the release of PrettyTable 0.7! The new
release is available to download from the "Downloads" tab of the
project home page and has also been uploaded to PyPI so you can install
it using easy_install, pip or other tools.

Changes from 0.6 to 0.7 include:

* Improved Python version compatibility. PrettyTable should now work
all Python releases between 2.4 and 3.2.
* Improved support for non-Latin characters. Table widths etc. should
now be calculated correctly for tables with e.g. Chinese, Japanese,
or Korean text. If PrettyTable seems to produce incorrectly formatted
tables using text in your native language, I consider this a bug, so
please report it!
* Table contents can now be read in from a .csv file.
* Table contents can now be read in from a DB-API compatible cursor
* Table contents can now be read in from a string containing a
HTML table (thanks to Christoph Robbert for submitting this patch!)
* new valign attribute controls vertical alignment of text when
some cells in a row have multiple lines of text and others don't.
(thanks to Google Code user maartendb for submitting this patch!)
* hrules attribute can now be set to HEADER, which draws a rule only
under the header row.
* new vrules attribute controls drawing of vertical rules and can
be set to FRAME, ALL or NONE.
* new header_style attribute controls formatting of text in table
headers and can be set to "cap", "title", "upper", "lower" or None.
* Fixed a simple bug regarding validation of max_width (thanks to
Anthony Toole for pointing out this bug and providing a patch).
* Fixed a simple bug regarding initialisation of int_format value
for new tables (thanks to Ingo Schmiegel for pointing out this
bug!)
* Fixed a bug regarding some constructor keywords, such as "border",
being ignored (thanks to Google Code user antonio.s.messina for
reporting this bug).

Unlike the change from 0.5 to 0.6, there have been no deliberate
compatibility breaks in the API going from 0.6 to 0.7, so you should
find that your existing applications "just work" after an upgrade. If
they do not, this is probably the result of a bug so please email me
or make an Issue report at the project website!

I will be updating the Wiki documentation today to reflect all new
features of 0.7.

Thanks to everybody who reported bugs, made feature suggestions,
submitted patches or helped test the 0.7 release candidates. Special
thanks go to Chris Clark for his testing help and advice on matters
related to unicode.

Happy hacking!
Luke
Reply all
Reply to author
Forward
0 new messages