Skip to content

bazel: Force python 2 for host tools#7337

Merged
lizan merged 1 commit intoenvoyproxy:masterfrom
keith:ks/force-py2
Jun 20, 2019
Merged

bazel: Force python 2 for host tools#7337
lizan merged 1 commit intoenvoyproxy:masterfrom
keith:ks/force-py2

Conversation

@keith
Copy link
Copy Markdown
Member

@keith keith commented Jun 20, 2019

bazelbuild/bazel#8626

Signed-off-by: Keith Smiley keithbsmiley@gmail.com

Risk Level: Low

bazelbuild/bazel#8626

Signed-off-by: Keith Smiley <keithbsmiley@gmail.com>
@keith
Copy link
Copy Markdown
Member Author

keith commented Jun 20, 2019

I'm not 100% sure this will work for us, but I want to see what CI thinks

@mattklein123
Copy link
Copy Markdown
Member

Do we know where we are not Python 3 compliant? Can we make sure we have an issue to track fixing that? IIRC I thought we could potentially also somehow just force this on specific broken tests which would make it easier to track. cc @lizan

@lizan
Copy link
Copy Markdown
Member

lizan commented Jun 20, 2019

@mattklein123 #7305 was trying to fix it in particular tests but didn't work.

@keith I'm going to merge this to see if bazel ci works. Can you create an issue for tracking?

@lizan lizan merged commit cb7fca2 into envoyproxy:master Jun 20, 2019
@keith keith deleted the ks/force-py2 branch June 20, 2019 20:16
@keith
Copy link
Copy Markdown
Member Author

keith commented Jun 20, 2019

#7342

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants