Comment 10 for bug 1504288

Hi all,

I haven't yet had time to fix the code. From the conversation it looks
like this change was introduced in python 3.4 upstream, right? And
this was done after the latest 3.4 was released (which would explain
why the tests didn't fail for me on the other 3.4 environments --
docker, arch, etc). If we don't revert this change upstream I expect
this to be included in the next 3.4 and 3.5 official python releases,
correct?

If this change is part of the official python release, then I think
the sensible thing is to

a) mark it as a backwards incompatible change
b) fix the code that relies on the "old" behavior

I'll try to find some time to fix this in configglue so that it works
with all 3.4/3.5 versions

On Tue, Oct 13, 2015 at 12:38 PM, Barry Warsaw
<email address hidden> wrote:
> Thanks Lukasz. The question is whether we should push more aggressively
> to revert the upstream change (which of course takes a while in and of
> itself to trickle down) or just fix it in the affected packages and move
> on?
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1504288
>
> Title:
> Test suite failure with Python 3.4 & 3.5
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/configglue/+bug/1504288/+subscriptions