You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pip's "process-dependency-links" flag is vital to some use cases involving nested private repos, but using it today spits out a warning (in red) that says:
DEPRECATION: Dependency Links processing has been deprecated and will be removed in a future release.
There isn't a good alternative to using this flag right now. Until something else comes along to be the better "right way" to do something, the old way can't really be called deprecated.
So it shouldn't be telling the user what they are doing is wrong.
I've circled back across the above article at least 6 times in the last 2 years, while trying in vain to figure out what I should have been doing to fix the warning.
Pip's "process-dependency-links" flag is vital to some use cases involving nested private repos, but using it today spits out a warning (in red) that says:
DEPRECATION: Dependency Links processing has been deprecated and will be removed in a future release.
There isn't a good alternative to using this flag right now. Until something else comes along to be the better "right way" to do something, the old way can't really be called deprecated.
So it shouldn't be telling the user what they are doing is wrong.
Background:
The first google result for "pip dependency_links" leads to stack overflow.
https://stackoverflow.com/questions/12518499/pip-ignores-dependency-links-in-setup-py
I've circled back across the above article at least 6 times in the last 2 years, while trying in vain to figure out what I should have been doing to fix the warning.
That stack overflow trail leads back a maintainer discussion.
https://groups.google.com/forum/#!topic/pypa-dev/tJ6HHPQpyJ4
Can the warning be softened, or removed until it actually is deprecated?
The text was updated successfully, but these errors were encountered: