Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Support Python 2 and 3 in the same build #3871

Closed
gregestren opened this issue Oct 6, 2017 · 2 comments
Closed

Support Python 2 and 3 in the same build #3871

gregestren opened this issue Oct 6, 2017 · 2 comments
Assignees
@gregestren

Comments

@gregestren
Copy link
Contributor

Context: https://groups.google.com/d/msg/bazel-discuss/nVQ48R94S_8/xbMi3_RWBwAJ

Active work is going on for this (code in review inside Google). Follow this bug to track.
@gregestren gregestren added this to the 0.8 milestone Oct 6, 2017
@gregestren gregestren self-assigned this Oct 6, 2017
@akirabaruah akirabaruah mentioned this issue Oct 7, 2017
Closed
bazel-io pushed a commit that referenced this issue Oct 20, 2017
@gregestren @damienmg
Support Python 2 and 3 in the same build.
8b5bf1f 
This is also an example of the versatility of dynamic configurations: this feature
only requires changes to rules/python/...

Issue #3871

PiperOrigin-RevId: 172775001
@gregestren
Copy link
Contributor Author

8b5bf1f puts in core support for building with both Python 2 and 3 in the same invocation.

I think we'll have to do some more tweaks to properly integrate the Python top, etc. But keep an eye out for this functionality, which alone might go a long way.

@hwright hwright mentioned this issue Nov 13, 2017
Closed
@emcfarlane emcfarlane mentioned this issue Mar 9, 2018
Closed
@brandjon
Copy link
Member

brandjon commented Sep 7, 2018

Closing this as dup: Let's use #4815 to track being able to at least run the "python3" command when the mode is set to PY3, and #3517 to track the broader problem of specifying/overriding the particular py2/py3 runtimes used.

@brandjon brandjon closed this as completed Sep 7, 2018
@samuela samuela mentioned this issue Oct 1, 2018
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gregestren gregestren

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@brandjon @gregestren