Skip to content

Conversation

mindflayer
Copy link
Owner

@mindflayer mindflayer commented Dec 2, 2020

I honestly prefer my solution so I'll close the other PR while being thankful to @brycedrennan for underlining the problem with its PR #132.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 98.712% when pulling 0ce88af on fix/pip-unable-to-resolve into 7075f20 on master.

3 similar comments
@coveralls
Copy link

Coverage Status

Coverage remained the same at 98.712% when pulling 0ce88af on fix/pip-unable-to-resolve into 7075f20 on master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 98.712% when pulling 0ce88af on fix/pip-unable-to-resolve into 7075f20 on master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 98.712% when pulling 0ce88af on fix/pip-unable-to-resolve into 7075f20 on master.

@coveralls
Copy link

coveralls commented Dec 2, 2020

Coverage Status

Coverage remained the same at 98.712% when pulling 0ce88af on fix/pip-unable-to-resolve into 7075f20 on master.

@mindflayer mindflayer merged commit 1ee3fb9 into master Dec 2, 2020
@mindflayer mindflayer deleted the fix/pip-unable-to-resolve branch December 2, 2020 22:08
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.

3 participants