Hi,
I've noticed a new behavior from the python-neutronclient which
disturbs me. For me, this just started happening with my latest build
of devstack which I built yesterday. It didn't happen with another
recent but little bit older devstack.
The issue is that the client is now wrapping content
I ran this by our all-knowing PTL who told me to go back to
cliff==1.15.0. My devstack had picked up cliff==2.0.0 which is what
seems to have introduced this behavior. Reverting to the older
version fixed this quirky behavior.
Before today, I didn't even know what cliff was. :)
Carl
On Wed, F
cliff-based client including neutronclient and openstackclient
supports various formatters.
I don't think it is a good idea to depend on the output of 'table' formatter.
My understanding is 'table' formatter (the default formatter) is for
human readability.
IMHO it is better to use json formatter o
On 02/24/2016 09:46 AM, Akihiro Motoki wrote:
cliff-based client including neutronclient and openstackclient
supports various formatters.
I don't think it is a good idea to depend on the output of 'table' formatter.
My understanding is 'table' formatter (the default formatter) is for
human readab
Right, but it breaks for humans too because it interferes with copy-paste.
:)
On Wed, Feb 24, 2016 at 9:46 AM, Akihiro Motoki wrote:
> cliff-based client including neutronclient and openstackclient
> supports various formatters.
> I don't think it is a good idea to depend on the output of 'table
On 25/02/16 06:23, Carl Baldwin wrote:
Hi,
I've noticed a new behavior from the python-neutronclient which
disturbs me. For me, this just started happening with my latest build
of devstack which I built yesterday. It didn't happen with another
recent but little bit older devstack.
The issue i
On 2/24/16 3:58 PM, Steve Baker wrote:
On 25/02/16 06:23, Carl Baldwin wrote:
Hi,
I've noticed a new behavior from the python-neutronclient which
disturbs me. For me, this just started happening with my latest build
of devstack which I built yesterday. It didn't happen with another
recent but
On Wed, Feb 24, 2016 at 2:58 PM, Steve Baker wrote:
> My intention was that it be a usability improvement rather than merely an
> aesthetic one. Yes, it is unfortunate that it affects this specific copy
> paste scenario but there are others where it is improved. I've often been in
> the situation
