the CI is failing now

[gaborbernat]

due to pypa/pip#6434; we'll have to pin the dev environment to an earlier pip 🤔 it seems

[gvanrossum]

Do you have an example PR that's failing? Do you have a suggested change to make it pass? I don't have time to read and understand that entire PIP issue.

[gaborbernat]

master at the moment, we have two option, either pin pip to 19.0.3 or disable the dev target in Travis

[gvanrossum]

I don't know what you mean by "dev target". I support pinning pip is a quick fix but not tenable long term. Are they planning a fix?

[gaborbernat]

we'll see it tomorrow what's the plan to solve it, will create either way a PR to fix it

…

On Wed, Apr 24, 2019, 18:29 Guido van Rossum ***@***.***> wrote: I don't know what you mean by "dev target". I support pinning pip is a quick fix but not tenable long term. Are they planning a fix? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#6716 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAFIQPUEKQEHOITB2T57YZ3PSCKFZANCNFSM4HIDXUTQ> .

[gvanrossum]

Sully just put up a PR, #6718

[gaborbernat]

Thanks, will make a final fix PR when pip agrees how to handle this case. That will do in the meantime.

[gvanrossum]

Reopening the bug, awaiting the final fix.