-
Notifications
You must be signed in to change notification settings - Fork 67
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
Fix crash when uname -rs
output is empty
#304
Conversation
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.
Looks good to me!
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.
Thanks for opening this, instead of changing _uname_info()
instead can we change _parse_uname_content
to tolerate any input? (And return {}
if it gets anything it's not expecting.
Done ! Don't forget to squash my mess. |
Up @brejoc 🙇 |
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.
Looks good! 👍
Anyone who wants to backport anything to the 2.6/7 branches is more than welcome. The reason we don't officially support EOL is rather obvious, but the branches are there for anyone willing to maintain them. |
Yes I was actually on it (for the 2.7) 😉 |
EDIT : I can backport this patch to the
python2.7-support
branch if you're OK with that.