Excerpts from Jeremy Stanley's message of 2015-07-14 13:08:46 +:
> On 2015-07-14 08:38:57 -0400 (-0400), Sean Dague wrote:
> > There is trove classification in the projects themselves right?
> [...]
> > That seems like it should be enough information to know the 2.6 question.
>
> I got to thin
On 2015-07-14 08:38:57 -0400 (-0400), Sean Dague wrote:
> There is trove classification in the projects themselves right?
[...]
> That seems like it should be enough information to know the 2.6 question.
I got to thinking through what this might look like, and while
filtering down the markers base
On 2015-07-14 08:38:57 -0400 (-0400), Sean Dague wrote:
> There is trove classification in the projects themselves right?
[...]
> That seems like it should be enough information to know the 2.6 question.
Only if it's kept up to date. If we're going to rely on it (not a
terrible idea) then we shoul
On 07/14/2015 08:11 AM, Andrey Kurilin wrote:
> Hi!
> It looks like novaclient still supports py26 :) At least, there is a
> gate-python-novaclient-python26 job.
> Also, I checked several commands(boot, *list, delete ) with python 2.6
> env and they work as expected for me.
Ah, right fair, my bad.
On 07/14/2015 08:32 AM, Jeremy Stanley wrote:
> On 2015-07-14 07:03:34 -0400 (-0400), Sean Dague wrote:
>> I just saw this Nova review come in -
>> https://review.openstack.org/#/c/200908
>>
>> Why are we merging 2.6 requirements for projects that don't support 2.6?
>> That seems potentially confus
On 2015-07-14 07:03:34 -0400 (-0400), Sean Dague wrote:
> I just saw this Nova review come in -
> https://review.openstack.org/#/c/200908
>
> Why are we merging 2.6 requirements for projects that don't support 2.6?
> That seems potentially confusing to end users that now think the project
> does,
Hi!
It looks like novaclient still supports py26 :) At least, there is a
gate-python-novaclient-python26 job.
Also, I checked several commands(boot, *list, delete ) with python 2.6 env
and they work as expected for me.
On Tue, Jul 14, 2015 at 2:03 PM, Sean Dague wrote:
> I just saw this Nova rev
I just saw this Nova review come in -
https://review.openstack.org/#/c/200908
Why are we merging 2.6 requirements for projects that don't support 2.6?
That seems potentially confusing to end users that now think the project
does, because there are still references in the code.
-Sean
--