On 21/06/15 01:32, Doug Hellmann wrote:
Excerpts from Dave Walker's message of 2015-06-20 14:05:48 +0100:
On 20 Jun 2015 1:05 pm, "Doug Hellmann" <d...@doughellmann.com> wrote:
<SNIP>
Whether we want to support 3.4 and 3.5, or just 3.4 and then just 3.5
is an ecosystem question IMO, not an upstream one. 3.4 and 3.5 are
very similar when you consider the feature set crossover with 2.7.
Right, and IIRC that's why we said at the summit that we would rather
not take the resources (in terms of people and CI servers) to run tests
against both, yet. Let's get one project fully working on one version of
python 3, and then we can start thinking about whether we need to
test multiple versions.
Having information available, even if there is not immediate intent to
support seems like something we should constantly be driving for. It
should certainly be non-voting, but if resources are limited - perhaps a
periodic job, rather that gate?
OTOH, if Canonical doesn't release a version of 3.4 that removes the
core dump bug soon, I will support moving fully to 3.5 or another test
platform, because that bug is causing us trouble in Oslo still.
s/Canonical/ubuntu
Can you link to the bug? I did a quick search, but couldn't find it quickly.
Hmm, https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1367907 is
marked as released but somehow it's still being triggered for
oslo.messaging.
FWIW http://packages.ubuntu.com/search?keywords=python3.4 suggests that
Trusty is still using python 3.4.0, and you don't get 3.4.3 until Vivid,
which is a bit sad - definitely worth quizzing the Ubuntu folks about
what the plan is there.
Regards
Mark
__________________________________________________________________________
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
