-
Notifications
You must be signed in to change notification settings - Fork 3.8k
Force Python 3.x from env in shebang lines #18285
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.
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
Conversation
|
FWIW this is useful for FreeBSD (so ports system can replace shebang lines, but it has to be consistent) per @rootwyrm |
CoffeeFlux
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fine in theory, though the test failures are relevant and should be resolved. Looks like the results of subprocess.check_output in both outgoingPath and incomingPath need to be converted to a string since that function returns a byte array?
|
Apparently RHEL6 is Py2.x and supported until Nov. @marek-safar once the build failures are fixed, is this safe to merge given the state of py2 support overall or do we have to hold off? |
7355a51 to
18299f0
Compare
|
Switching to python3 is fine and actually desirable going forward |
akoeplinger
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems ready to me.
|
@monojenkins build failed |
|
The webassembly failures are unrelated, merging. |
* Fix byte/string incompatiblity in Python 3 Commit migrated from mono/mono@524a829
|
@monojenkins backport 2019-12 |
* Fix byte/string incompatiblity in Python 3
Extracted from #18284