FTBFS in Wily

Bug #1491162 reported by Barry Warsaw on 2015-09-01
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
six (Ubuntu)
Undecided
Unassigned

Bug Description

Upstream six 1.9.0 is incompatible with Python 3.5 due to an ast module API change (ast API is not guaranteed to be stable across Python releases). This causes six to FTBFS in Wily, where we've enabled Python 3.5 as a supported version.

https://bitbucket.org/gutworth/six/issues/131/python-35-test-failures

Colin Watson (cjwatson) wrote :

I thought (from https://github.com/pytest-dev/pytest/issues/744) that you were planning to fix this by backporting the pytest fix instead?

On Sep 01, 2015, at 10:57 PM, Colin Watson wrote:

>I thought (from https://github.com/pytest-dev/pytest/issues/744) that
>you were planning to fix this by backporting the pytest fix instead?

I think I forgot to do that. I'll look at that tomorrow and back out the six
change if it works out. I was hoping upstream would have landed and released
the fix by now.

Barry Warsaw (barry) wrote :

On Sep 01, 2015, at 10:57 PM, Colin Watson wrote:

>I thought (from https://github.com/pytest-dev/pytest/issues/744) that
>you were planning to fix this by backporting the pytest fix instead?

I admit I'm thoroughly confused. pytest already has the py35 patch and now
after building a six 1.9.0-5 with the -4 change reverted, it builds fine. I'm
sure I did several rebuilds with 1.9.0-3. Either I was living in an
alternative universe yesterday, or a good night's sleep scared away the
gremlins.

Sorry for the false alarm.

Changed in six (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers