Skip to content

Move to python3 by default #235

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

Merged
merged 2 commits into from
Oct 13, 2020
Merged

Move to python3 by default #235

merged 2 commits into from
Oct 13, 2020

Conversation

frozencemetery
Copy link
Member

When moving 2 -> 3, python elected to keep "python" as the name of the
python2 interpreter. As a result, python3-only machines have no
/usr/bin/python. Since python2 is EOL, it should be safe to make our
scripting default to python3.

Signed-off-by: Robbie Harwood rharwood@redhat.com

When moving 2 -> 3, python elected to keep "python" as the name of the
python2 interpreter.  As a result, python3-only machines have no
/usr/bin/python.  Since python2 is EOL, it should be safe to make our
scripting default to python3.

Signed-off-by: Robbie Harwood <rharwood@redhat.com>
virtualenv relies on its executable being ahead of the system ones.  For
setting up the KDC, we don't have a preferencee - we just need the sbins
to be available.

Signed-off-by: Robbie Harwood <rharwood@redhat.com>
@frozencemetery frozencemetery requested a review from simo5 October 13, 2020 15:16
Copy link
Contributor

@simo5 simo5 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@simo5 simo5 merged commit 45fa4f2 into gssapi:master Oct 13, 2020
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.

2 participants