Skip to content

Conversation

@mambocab
Copy link
Contributor

@mambocab mambocab commented Nov 5, 2018

We can push this to the next release if timing necessitates it; I'm just PRing because I found this branch lying around.

@mambocab mambocab requested a review from aboudreault November 5, 2018 17:14
Copy link
Contributor

@aboudreault aboudreault left a comment

Choose a reason for hiding this comment

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

LGTM Jim!

@aboudreault
Copy link
Contributor

If our test suite passes, no objection to include this in 3.16.

@mambocab
Copy link
Contributor Author

mambocab commented Nov 5, 2018

Awesome, thanks. Merging then!

@mambocab mambocab force-pushed the python-895_require-only-one-resolved-contact-point branch from d7efc2a to 9c47bcc Compare November 5, 2018 20:47
@mambocab mambocab merged commit 8c1a909 into master Nov 5, 2018
@mambocab mambocab deleted the python-895_require-only-one-resolved-contact-point branch November 5, 2018 20:48
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