-
-
Notifications
You must be signed in to change notification settings - Fork 611
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
Add compatibility with the pip master (upcoming pip==19.3) #864
Conversation
This comment has been minimized.
This comment has been minimized.
Codecov Report
@@ Coverage Diff @@
## master #864 +/- ##
==========================================
+ Coverage 99.05% 99.06% +<.01%
==========================================
Files 35 35
Lines 2230 2237 +7
Branches 285 286 +1
==========================================
+ Hits 2209 2216 +7
Misses 13 13
Partials 8 8
Continue to review full report at Codecov.
|
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.
To be in line with the improvements in pip (lazy import / creation), I think it would be good if _compat.pip_compat
would do less also - specifically not doing the InstallCommand = do_import("commands.install", "InstallCommand")
anymore. This should be done via/in create_install_command
then only.
69d412b
to
66c261d
Compare
Master broken again, see #876 |
I've used |
The |
FTR, pip-tools/piptools/repositories/pypi.py Lines 188 to 199 in b387e5e
|
I've fixed the latest compatibility issue. I hope it's the last breaking change in upcoming We should check this before release in October, see pypa/pip#6993 (comment). Otherwise, it'll break pip-tools again. /cc @vphilippon @davidovich @blueyed @jdufresne @jcushman @codingjoe Sorry for disturbing you guys. Pinging the most recently active members 🙏 |
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.
LGTM, I would probably prefer it though, if you would skip the broken pytest version in a separate PR and rebase. Is there maybe a way to already test against the new version in the tox setup? I mean it does test against master, but we should maybe also add the version you wrote the exception handling for later.
Hey @codingjoe, thanks for reviewing this!
Do I understand correctly that you want to remove 9f02db5 from this PR and open a separate PR for this commit?
Do you mean to add to tox.ini new env
And change it later to |
@atugushev yes, yes and yes ;) |
Function is_vcs_url has been replaced by is_vcs Link property. See pypa/pip#6883
The `get_best_candidate` has been renamed to `compute_best_candidate`, which now returns an instance of `BestCandidateResult`. See pypa/pip#6787
Add pip19.3 the tox envlist.
9f02db5
to
8b05751
Compare
Addressed in 8b05751. Also, I've rebased to the latest master. |
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.
LGTM 👍 thanks for adressing my change requests
@codingjoe thanks for reviewing this. Appreciate it! |
create_command
function to instantiate a command (e.g., InstallCommand), see Address #6692: Only import a Command class when needed pypa/pip#6694.is_vcs_url
function, see consolidate vcs link detection pypa/pip#6883, closes pip: function is_vcs_url moved to is_vcs Link property #876.PackageFinder
, see Simplify PackageFinder best candidate API some more pypa/pip#6787.Resolver
, see Reduce context/options passed to Resolver pypa/pip#6986.Changelog-friendly one-liner: Add compatibility with
pip==19.3
Contributor checklist