PrettyTable 0.6 Release Candidate 2
7 views
Skip to first unread message
Luke Maurits
May 1, 2012, 10:56:25 PM5/1/12
to prettytable-devel
Greetings prettytable-devel,
After yet another prolonged period of inactivity, I am gearing up to
release PrettyTable 0.6. And I mean it this time!
Tonight I have tagged 0.6-RC2 in the subversion repository (trunk is
exactly the same). I would appreciate it if people using PrettyTable
who are interested in upgrading to 0.6 would make down to download and
test this new version in their apps in the near future. I am
especially interested in hearing from people using PrettyTable in
Python 3 applications (0.6-RC2 should work equally well with Python
2.6, 2.7 and any version of 3.x) and people using PrettyTable in
unicode-rich environments.
0.6-RC2 contains many bug fixes and new features. For now the new
features are largely undocumented. You may use the Issue browser at
http://code.google.com/p/prettytable/issues/list to get an idea of
things which have happened - search for All Issues rather than just
Open Issues to see bugs and feature requests which have been dealt
with. However, making sure that existing applications which make no
use of the new features still work as expected is just as important as
testing the new features, so please do not feel under any obligation
to test new features if they aren't an obvious fit to your
application.
Please remember that there have been significant API changes between
0.5 and 0.6. The Wiki page at http://code.google.com/p/prettytable/wiki/Tutorial06
is a tutorial for the 0.6 API which you may like to read through
quickly before you try to convert your existing applications so you
know what to expect. If you find any problems with the Wiki page - if
the page says something should act one way but it acts differently, or
you feel like something should be better explained, or you just find a
spelling or grammar mistake - then please use the "Enter a comment"
box at the bottom of the page to let me know about it.
Because I am very keen to not lose momentum and genuinely do a release
this time, I do not want to wait a long time for feedback on RC2. My
current plan is to release 0.6 on Saturday the 5th of May (PDT),
unless feedback on RC2 reveals a lot of terrible problems. This
leaves less than a week for people to do testing.
I want to thank everybody who made bug reports and/or feature
suggestions and who contributed patches that have gone toward 0.6. I
apologise that for so long your work has sat in the svn trunk instead
of getting out into the wild as part of a new release. Hopefully
everybody's work will see the light of day soon.
Regards,
Luke
After yet another prolonged period of inactivity, I am gearing up to
release PrettyTable 0.6. And I mean it this time!
Tonight I have tagged 0.6-RC2 in the subversion repository (trunk is
exactly the same). I would appreciate it if people using PrettyTable
who are interested in upgrading to 0.6 would make down to download and
test this new version in their apps in the near future. I am
especially interested in hearing from people using PrettyTable in
Python 3 applications (0.6-RC2 should work equally well with Python
2.6, 2.7 and any version of 3.x) and people using PrettyTable in
unicode-rich environments.
0.6-RC2 contains many bug fixes and new features. For now the new
features are largely undocumented. You may use the Issue browser at
http://code.google.com/p/prettytable/issues/list to get an idea of
things which have happened - search for All Issues rather than just
Open Issues to see bugs and feature requests which have been dealt
with. However, making sure that existing applications which make no
use of the new features still work as expected is just as important as
testing the new features, so please do not feel under any obligation
to test new features if they aren't an obvious fit to your
application.
Please remember that there have been significant API changes between
0.5 and 0.6. The Wiki page at http://code.google.com/p/prettytable/wiki/Tutorial06
is a tutorial for the 0.6 API which you may like to read through
quickly before you try to convert your existing applications so you
know what to expect. If you find any problems with the Wiki page - if
the page says something should act one way but it acts differently, or
you feel like something should be better explained, or you just find a
spelling or grammar mistake - then please use the "Enter a comment"
box at the bottom of the page to let me know about it.
Because I am very keen to not lose momentum and genuinely do a release
this time, I do not want to wait a long time for feedback on RC2. My
current plan is to release 0.6 on Saturday the 5th of May (PDT),
unless feedback on RC2 reveals a lot of terrible problems. This
leaves less than a week for people to do testing.
I want to thank everybody who made bug reports and/or feature
suggestions and who contributed patches that have gone toward 0.6. I
apologise that for so long your work has sat in the svn trunk instead
of getting out into the wild as part of a new release. Hopefully
everybody's work will see the light of day soon.
Regards,
Luke
Sandro Tosi
May 3, 2012, 5:51:39 PM5/3/12
to prettyta...@googlegroups.com
Hello Luke
On Wed, May 2, 2012 at 4:56 AM, Luke Maurits <lu...@maurits.id.au> wrote:
> Greetings prettytable-devel,
>
> After yet another prolonged period of inactivity, I am gearing up to
> release PrettyTable 0.6. And I mean it this time!
Good to see your back to PrettyTable!
> Tonight I have tagged 0.6-RC2 in the subversion repository (trunk is
> exactly the same). I would appreciate it if people using PrettyTable
I'm surely interested in testing this new versions, I'll try to do that asap.
> who are interested in upgrading to 0.6 would make down to download and
> test this new version in their apps in the near future. I am
> especially interested in hearing from people using PrettyTable in
> Python 3 applications (0.6-RC2 should work equally well with Python
> 2.6, 2.7 and any version of 3.x) and people using PrettyTable in
> unicode-rich environments.
In Debian I've recently introduced a python3 package, but having
upstream support is surely better than what we have today!
> 0.6-RC2 contains many bug fixes and new features. For now the new
> features are largely undocumented. You may use the Issue browser at
> http://code.google.com/p/prettytable/issues/list to get an idea of
> things which have happened - search for All Issues rather than just
> Open Issues to see bugs and feature requests which have been dealt
> with. However, making sure that existing applications which make no
> use of the new features still work as expected is just as important as
> testing the new features, so please do not feel under any obligation
> to test new features if they aren't an obvious fit to your
> application.
>
> Please remember that there have been significant API changes between
> 0.5 and 0.6. The Wiki page at http://code.google.com/p/prettytable/wiki/Tutorial06
> is a tutorial for the 0.6 API which you may like to read through
> quickly before you try to convert your existing applications so you
> know what to expect. If you find any problems with the Wiki page - if
> the page says something should act one way but it acts differently, or
> you feel like something should be better explained, or you just find a
> spelling or grammar mistake - then please use the "Enter a comment"
> box at the bottom of the page to let me know about it.
It would also be nice, from a distribution point of view, if you could
include all those docs in the 0.6 official tarball.
> Because I am very keen to not lose momentum and genuinely do a release
> this time, I do not want to wait a long time for feedback on RC2. My
> current plan is to release 0.6 on Saturday the 5th of May (PDT),
> unless feedback on RC2 reveals a lot of terrible problems. This
> leaves less than a week for people to do testing.
Great, I like aggressive plans! :)
Cheers,
--
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
On Wed, May 2, 2012 at 4:56 AM, Luke Maurits <lu...@maurits.id.au> wrote:
> Greetings prettytable-devel,
>
> After yet another prolonged period of inactivity, I am gearing up to
> release PrettyTable 0.6. And I mean it this time!
> Tonight I have tagged 0.6-RC2 in the subversion repository (trunk is
> exactly the same). I would appreciate it if people using PrettyTable
> who are interested in upgrading to 0.6 would make down to download and
> test this new version in their apps in the near future. I am
> especially interested in hearing from people using PrettyTable in
> Python 3 applications (0.6-RC2 should work equally well with Python
> 2.6, 2.7 and any version of 3.x) and people using PrettyTable in
> unicode-rich environments.
upstream support is surely better than what we have today!
> 0.6-RC2 contains many bug fixes and new features. For now the new
> features are largely undocumented. You may use the Issue browser at
> http://code.google.com/p/prettytable/issues/list to get an idea of
> things which have happened - search for All Issues rather than just
> Open Issues to see bugs and feature requests which have been dealt
> with. However, making sure that existing applications which make no
> use of the new features still work as expected is just as important as
> testing the new features, so please do not feel under any obligation
> to test new features if they aren't an obvious fit to your
> application.
>
> Please remember that there have been significant API changes between
> 0.5 and 0.6. The Wiki page at http://code.google.com/p/prettytable/wiki/Tutorial06
> is a tutorial for the 0.6 API which you may like to read through
> quickly before you try to convert your existing applications so you
> know what to expect. If you find any problems with the Wiki page - if
> the page says something should act one way but it acts differently, or
> you feel like something should be better explained, or you just find a
> spelling or grammar mistake - then please use the "Enter a comment"
> box at the bottom of the page to let me know about it.
include all those docs in the 0.6 official tarball.
> Because I am very keen to not lose momentum and genuinely do a release
> this time, I do not want to wait a long time for feedback on RC2. My
> current plan is to release 0.6 on Saturday the 5th of May (PDT),
> unless feedback on RC2 reveals a lot of terrible problems. This
> leaves less than a week for people to do testing.
Cheers,
--
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
Luke Maurits
May 3, 2012, 10:34:14 PM5/3/12
to prettyta...@googlegroups.com
Hello Sandro! Glad to see you are still following this list and packaging PrettyTable for Debian. :)
> Good to see your back to PrettyTable!
Yes, it really has been ridiculously too long!
> I'm surely interested in testing this new versions, I'll try to do that asap.
I really appreciate your helpfulness, and look forward to hearing back from you.
> In Debian I've recently introduced a python3 package, but having
> upstream support is surely better than what we have today!
Oh, interesting! How was this handled, is apt set up to automatically apply a patch from 2to3 or something like that?
> It would also be nice, from a distribution point of view, if you could
> include all those docs in the 0.6 official tarball.
That's a good idea, I'll make sure to do that. I've been reading up on Python package distribution lately in preparation for 0.6, because it's been a while! I understand that distutils these days automatically puts any files that are version controlled into the distribution, even if they're not in a MANIFEST.in. So I'll make sure to put some documentation in the repo before I upload the tarball to PyPi.
> Great, I like aggressive plans! :)
I'm hoping this one pays off!
Cheers,
Luke
> Good to see your back to PrettyTable!
> I'm surely interested in testing this new versions, I'll try to do that asap.
> In Debian I've recently introduced a python3 package, but having
> upstream support is surely better than what we have today!
> It would also be nice, from a distribution point of view, if you could
> include all those docs in the 0.6 official tarball.
> Great, I like aggressive plans! :)
Cheers,
Luke
Sandro Tosi
May 5, 2012, 1:07:21 PM5/5/12
to prettyta...@googlegroups.com
On Fri, May 4, 2012 at 4:34 AM, Luke Maurits <lu...@maurits.id.au> wrote:
>> In Debian I've recently introduced a python3 package, but having
>> upstream support is surely better than what we have today!
>
> Oh, interesting! How was this handled,
we run 2to3 and get the resulting file installed for the python3 package.
>> In Debian I've recently introduced a python3 package, but having
>> upstream support is surely better than what we have today!
>
> Oh, interesting! How was this handled,
>> It would also be nice, from a distribution point of view, if you could
>> include all those docs in the 0.6 official tarball.
>
> That's a good idea, I'll make sure to do that. I've been reading up on Python package distribution lately in preparation for 0.6, because it's been a while! I understand that distutils these days automatically puts any files that are version controlled into the distribution, even if they're not in a MANIFEST.in. So I'll make sure to put some documentation in the repo before I upload the tarball to PyPi.
the license: it would be interesting to have them too in the released
tarball.
i've tested the 06 RC2 and it works fine, so the packaging is ready to
receive the 0.6 final :)
Julien Koesten - Gmail
May 6, 2012, 3:49:50 AM5/6/12
to prettyta...@googlegroups.com
Great news Luke !
I will definitely test this new version and will report you if I see
some bugs !
Good to see you back !
Best regards,
Le 05/05/2012 19:07, Sandro Tosi a �crit :
I will definitely test this new version and will report you if I see
some bugs !
Good to see you back !
Best regards,
Le 05/05/2012 19:07, Sandro Tosi a �crit :
Luke Maurits
May 6, 2012, 8:01:52 PM5/6/12
to prettyta...@googlegroups.com
Hi everyone,
I've uploaded 0.6 to the Cheeseshop now, so you should be able to install/upgrade PrettyTable using easy_install or pip or similar tools. I will post an official announcement to the prettytable-announce list tomorrow. If anybody has trouble installing/updating the new version, please let me know ASAP so I can fix any problems before making the official announcement.
Sandro, currently the tarballs at PyPi do not contain the CHANGELOG or COPYING files as we discussed, but they do contain a README file which is based off the Wiki page for the 0.6 API. It seems like the documentation I read about distutils automatically including files which are in SVN even if there is no MANIFEST.in was either wrong or misleading, because those files did not get pulled in. README did, so I have to assume that distutils explicitly checks for files with that name. I will create a MANIFEST.in file, rebuild the tarballs so that everything is in there and reupload, but it will have to wait until tomorrow. So perhaps it would be best to hold off on making a new Debian package until this is done, so you can include those extra files.
Cheers,
Luke
> --
> You received this message because you are subscribed to the Google Groups "prettytable-devel" group.
> To post to this group, send email to prettyta...@googlegroups.com.
> To unsubscribe from this group, send email to prettytable-de...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/prettytable-devel?hl=en.
>
--
Luke Maurits <lu...@maurits.id.au>
I've uploaded 0.6 to the Cheeseshop now, so you should be able to install/upgrade PrettyTable using easy_install or pip or similar tools. I will post an official announcement to the prettytable-announce list tomorrow. If anybody has trouble installing/updating the new version, please let me know ASAP so I can fix any problems before making the official announcement.
Sandro, currently the tarballs at PyPi do not contain the CHANGELOG or COPYING files as we discussed, but they do contain a README file which is based off the Wiki page for the 0.6 API. It seems like the documentation I read about distutils automatically including files which are in SVN even if there is no MANIFEST.in was either wrong or misleading, because those files did not get pulled in. README did, so I have to assume that distutils explicitly checks for files with that name. I will create a MANIFEST.in file, rebuild the tarballs so that everything is in there and reupload, but it will have to wait until tomorrow. So perhaps it would be best to hold off on making a new Debian package until this is done, so you can include those extra files.
Cheers,
Luke
> You received this message because you are subscribed to the Google Groups "prettytable-devel" group.
> To post to this group, send email to prettyta...@googlegroups.com.
> To unsubscribe from this group, send email to prettytable-de...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/prettytable-devel?hl=en.
>
--
Luke Maurits <lu...@maurits.id.au>
Luke Maurits
May 6, 2012, 6:11:26 AM5/6/12
to prettyta...@googlegroups.com
Hi Sandro,
Thanks very much for getting back to me with the results of your testing, I'm really glad that everything worked. I've had two people sign off on it now, so later today, probably in the evening, I'll release 0.6. Exciting times!
Thanks very much for getting back to me with the results of your testing, I'm really glad that everything worked. I've had two people sign off on it now, so later today, probably in the evening, I'll release 0.6. Exciting times!
Sandro Tosi
May 10, 2012, 5:31:32 PM5/10/12
to prettyta...@googlegroups.com
Hi Luke,
weird only today I see this message in my mailbox, while it's marked
as being sent 4 days ago.
On Mon, May 7, 2012 at 2:01 AM, Luke Maurits <lu...@maurits.id.au> wrote:
> Hi everyone,
>
> I've uploaded 0.6 to the Cheeseshop now, so you should be able to install/upgrade PrettyTable using easy_install or pip or similar tools. I will post an official announcement to the prettytable-announce list tomorrow. If anybody has trouble installing/updating the new version, please let me know ASAP so I can fix any problems before making the official announcement.
>
> Sandro, currently the tarballs at PyPi do not contain the CHANGELOG or COPYING files as we discussed,
it would be nice if you can include them in the next upload.
> but they do contain a README file which is based off the Wiki page for the 0.6 API. It seems like the documentation I read about distutils automatically including files which are in SVN even if there is no MANIFEST.in was either wrong or misleading, because those files did not get pulled in. README did, so I have to assume that distutils explicitly checks for files with that name. I will create a MANIFEST.in file, rebuild the tarballs so that everything is in there and reupload, but it will have to wait until tomorrow. So perhaps it would be best to hold off on making a new Debian package until this is done, so you can include those extra files.
Well, i've already uploaded prettytable the moment I see the package
on pypi, but if you happen to make another release (even if 0.6.1)
I'll be happy to update the package right away.
weird only today I see this message in my mailbox, while it's marked
as being sent 4 days ago.
On Mon, May 7, 2012 at 2:01 AM, Luke Maurits <lu...@maurits.id.au> wrote:
> Hi everyone,
>
> I've uploaded 0.6 to the Cheeseshop now, so you should be able to install/upgrade PrettyTable using easy_install or pip or similar tools. I will post an official announcement to the prettytable-announce list tomorrow. If anybody has trouble installing/updating the new version, please let me know ASAP so I can fix any problems before making the official announcement.
>
> Sandro, currently the tarballs at PyPi do not contain the CHANGELOG or COPYING files as we discussed,
> but they do contain a README file which is based off the Wiki page for the 0.6 API. It seems like the documentation I read about distutils automatically including files which are in SVN even if there is no MANIFEST.in was either wrong or misleading, because those files did not get pulled in. README did, so I have to assume that distutils explicitly checks for files with that name. I will create a MANIFEST.in file, rebuild the tarballs so that everything is in there and reupload, but it will have to wait until tomorrow. So perhaps it would be best to hold off on making a new Debian package until this is done, so you can include those extra files.
on pypi, but if you happen to make another release (even if 0.6.1)
I'll be happy to update the package right away.
Luke Maurits
May 11, 2012, 10:28:08 AM5/11/12
to prettyta...@googlegroups.com
Hi Sandro,
Yes, I'm not sure what has happened here. I sent this message and only several days later did I get an email from Google Groups telling me it needed moderating (along with another one from somebody else). I do not know why it asked me to moderate my own mail, because I have told it in the past to always allow posts from my address. I also don't know why it took so long for me to get the moderation email, usually these come in pretty quickly after someone posts to the list.
Now I understand why you opened the Issue about CHANGELOG etc. that you did! You hadn't seen my email about it on the devel list, even though I sent it about a day before. Sorry for any confusion.
In a reply to your Issue I asked for your opinion on how best to include the unit tests. Lately I have been thinking of just including them as a separate module even though it feels wrong, since it can always be changed later and I am eager to get to work on changes for 0.7. However, if you do have some ideas on the matter I would love to hear them.
Cheers,
Luke
Yes, I'm not sure what has happened here. I sent this message and only several days later did I get an email from Google Groups telling me it needed moderating (along with another one from somebody else). I do not know why it asked me to moderate my own mail, because I have told it in the past to always allow posts from my address. I also don't know why it took so long for me to get the moderation email, usually these come in pretty quickly after someone posts to the list.
Now I understand why you opened the Issue about CHANGELOG etc. that you did! You hadn't seen my email about it on the devel list, even though I sent it about a day before. Sorry for any confusion.
In a reply to your Issue I asked for your opinion on how best to include the unit tests. Lately I have been thinking of just including them as a separate module even though it feels wrong, since it can always be changed later and I am eager to get to work on changes for 0.7. However, if you do have some ideas on the matter I would love to hear them.
Cheers,
Luke
Reply all
Reply to author
Forward
0 new messages