PrettyTable 0.6.1
7 views
Skip to first unread message
Luke Maurits
Jun 3, 2012, 6:45:25 PM6/3/12
to prettytabl...@googlegroups.com
Hi PrettyTable users,
Today I have release PrettyTable 0.6.1. It is available from PyPi, so you can upgrade with easy_install, pip, etc. This is a bug fix release that corrects a few problems which have turned up with the recently released 0.6:
Firstly, despite 0.6 being supposed to introduce Python 3 compatibility, it was in fact only compatible with 3.2, not with 3.1 or 3.0, as I had unwittingly used a feature new to 3.2. This has been fixed.
Secondly, the __str__() method for PrettyTable objects was forcing use of the ASCII encoding, replacing all non-ASCII characters with question marks. However, the get_string() method returned an unencoded Unicode object. This meant that tables with non-ASCII characters would look correct with "print x.get_string()", but be fully of question marks with "print x". This has been fixed and __str__ now uses a user-definable encoding (which defaults to UTF-8). Thanks to Google Code user kevincobain2000 for reporting this problem.
0.6.1 now also includes the CHANGELOG, COPYING and README text files, as well as the test suite file prettytable_test.py in the source package. This change will not concern most users of PrettyTable, but people who repackage PrettyTable into other formats like .deb or .rpm may wish to take advantage of this change.
Happy hacking!
Luke
Today I have release PrettyTable 0.6.1. It is available from PyPi, so you can upgrade with easy_install, pip, etc. This is a bug fix release that corrects a few problems which have turned up with the recently released 0.6:
Firstly, despite 0.6 being supposed to introduce Python 3 compatibility, it was in fact only compatible with 3.2, not with 3.1 or 3.0, as I had unwittingly used a feature new to 3.2. This has been fixed.
Secondly, the __str__() method for PrettyTable objects was forcing use of the ASCII encoding, replacing all non-ASCII characters with question marks. However, the get_string() method returned an unencoded Unicode object. This meant that tables with non-ASCII characters would look correct with "print x.get_string()", but be fully of question marks with "print x". This has been fixed and __str__ now uses a user-definable encoding (which defaults to UTF-8). Thanks to Google Code user kevincobain2000 for reporting this problem.
0.6.1 now also includes the CHANGELOG, COPYING and README text files, as well as the test suite file prettytable_test.py in the source package. This change will not concern most users of PrettyTable, but people who repackage PrettyTable into other formats like .deb or .rpm may wish to take advantage of this change.
Happy hacking!
Luke
Reply all
Reply to author
Forward
0 new messages