Skip to content
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 import of parse_requirements #81

Closed
wants to merge 1 commit into from

Conversation

mark-adams
Copy link

Starting in pip 10.x, parse_requirements was moved to an internal
namespace to help demonstrate the fact that it is not a public API.

As a workaround until a broader decision can be made about how this
should look long term, this change attepts to perform the import using
the pip 10.x path and if it fails, falls back on the older path.

Fixes #80.

Starting in pip 10.x, parse_requirements was moved to an internal
namespace to help demonstrate the fact that it is not a public API.

As a workaround until a broader decision can be made about how this
should look long term, this change attepts to perform the import using
the pip 10.x path and if it fails, falls back on the older path.

Fixes launchdarkly#80.
@mark-adams mark-adams requested a review from ashanbrown as a code owner April 16, 2018 13:22
@eli-darkly
Copy link
Contributor

We're going to go with a different approach just to avoid importing any internal APIs, but thanks for submitting this.

@eli-darkly eli-darkly closed this Apr 16, 2018
@mark-adams
Copy link
Author

No worries. Just trying to get something out quick and fast since this caused a lot of pain for a lot of people when pip 10.x was released. 👍

eli-darkly added a commit that referenced this pull request Jan 16, 2019
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