On 07/17/2013 04:19 PM, Monty Taylor wrote:
On 07/17/2013 08:54 AM, Matt Riedemann wrote:
What do you mean in (b) about upstream python not supporting python 2.6?
From what I understand here, it's the version of testrepository being
used that doesn't support py26, not python itself or openstack.
I believe he means that upstream python does not intend to make any
further releases of python 2.6.
Anyone doing development or test on RHEL 6 (which doesn't have python
2.7) is going to have an issue with this.
Yeah. Us dropping support for 2.6 right now is not an option.
It is worth noting that it's possible we might have more and more
problems over time with libraries or tools we consume ceasing to care
about 2.6 - but thusfar we're in good shape and regularly test all of
openstack on 2.6.
So this opens up an idea that came up over beers in NYC. There are
certain projects that are important enough to our functioning gate, like
testrepository and subunit, that we might want to do better than waiting
for releases to figure out if they work in all our configs.
Having a nightly tracking job on some of these projects which does a
handful of useful tests against their upstream SCM could provide useful
feedback to upstream maintainers before releases of those projects are made.
-Sean
--
Sean Dague
http://dague.net
_______________________________________________
OpenStack-dev mailing list
[email protected]
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
