I'm fine with #2 or #1

The oslo automaton lib also uses pretty table to generate state-machine tables (a useful feature to have, but not a necessity).

https://github.com/openstack/automaton/blob/master/requirements.txt#L14

So I'd def help keep prettytable going, of course another option is to move to https://pypi.python.org/pypi/tabulate (which does seem active and/or maintained); tabulate provides pretty much the same thing (actually more table formats @ https://pypi.python.org/pypi/tabulate#table-format ) than prettytable and the api is pretty much the same (or nearly).

So that's another way to handle this (just to move off prettytable entirely).

-Josh

Davanum Srinivas wrote:
#2 please :)

Thanks,
Dims

On Fri, Jan 8, 2016 at 8:06 AM, Flavio Percoco<fla...@redhat.com>  wrote:
Greetings,

As some of you know already, google code is going to be shutdown. Some
projects we're using are hosted and, unfortunately, some of them are
unmaintained and perhaps going away.

One of these projects is PrettyTable. This point was raised by Erno in
this patch[0] from jd__. PrettyTable is not just being used in several
openstack specific projects but it's also a transitive dependency for
all client libraries using cliff.

With all that in mind, I've contacted the author of the library and
asked him if it'd be ok for us (OpenStack) to adopt this library. The
author accepted and granted me access to the project on pypi.

I'm saying all the above because we now need to find a home for it in
OpenStack.

I've identified 2 possible places:

1) Oslo, as we maintaing cross-project libraries and some of them are
not in the oslo namespace

2) OpenStack Client team as they maintain cliff already and it'd
perhaps make more sense to have this library there.

One thing to note is that this library has been quite stable, which
means it won't, hopefully, add too much work to the team.

Thoughts?

[0] https://review.openstack.org/#/c/234340/

--
@flaper87
Flavio Percoco

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev





__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to