Excerpts from Robert Collins's message of 2015-06-20 16:22:51 +1200: > On 19 June 2015 at 02:18, Ian Cordasco <ian.corda...@rackspace.com> wrote: > > > > > > On 6/18/15, 08:44, "Thomas Goirand" <z...@debian.org> wrote: > > > Does this mean that Debian is going to ignore classifiers for all projects > > that list 3.4 without listing 3.5 and will start reporting bugs against > > them before upstream projects have time to start testing against 3.5? Why > > is Debian running tests against versions of python that upstream doesn't > > claim to support? > > I think this is taking a rather extreme interpretation of Thomas' > email. Here's what I read: > > - Debian 9.0 is hoping to be 3.5 not 3.4 > - The experimental staging area in Debian has 3.5 already and is > starting to find out what packages are going to have issues > - Some of OpenStack does. > - Please introduce 3.5 as a supported Python as soon as we can. > > Which is I think a reasonable request.
+1 > 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. 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. Doug __________________________________________________________________________ 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
