- Add custom rmtree function to handle windows rms
- Only warn on failure to remove a tree
- This should mitigate a large portion of our windows test failures
- After sufficiently substantial time investment I am currently of the
opinion that there is no real elegant way to handle this (I have tried
programmatically finding all processes with open file handles,
terminating them with a 500ms retry and a 15s timeout)
- Close and handle tempfiles in resolvers
- Only create tempfiles for non-editable deps
- set umask and `PIP_SRC` for test context
- Warn instead of throwing exceptions
- Backport TemporaryDirectory for python2/3 compatibility and reliance
on custom rmtree error handling
- Vendor backport of `weakref.finalize` for
`TemporaryDirectory.cleanup()`
- Add PyTest fixtures to wrap and cleanup `PIP_SRC` directory at the module level to avoid permissions errors on appveyor
- Add resource warnings for PY2 compat
Lock instead of installing complex resolver test
- Add a special condition for allowing access errors
- Fixes issues when turning vcs lines into requirements
- At some point there was a regression around this which treats them as
normal paths
- This now follows pip practices as well
- Big todo: clean up duplicate functionality / break out logic for
requirements parsing
- Adds regression test for this case
This updates
test_editable_vcs_install_in_pipfile_with_dependency_resolution_doesnt_traceback
to check (a) that dependency resolution was triggered, and (b) that
there was no traceback (rather than just the specific traceback we are
currently seeing).
- Fixes#1225
- Add checks for Wheel files and archive files specifically
- Adopts egg-fragment parsing for local file paths to allow naming of
filesystem paths as well
- Adds these checks both to the get_requirement() function and the
is_installable_file() function
- Backup resolver was broken when hash resolution was split out into two
functions
- This PR returns the resolver to the caller function
- This is for edge cases where the PyPI json API and the pip resolver
don't return the same authoritative result for a package lookup (a name
can be resolved in one source but not the other)
- Added test to prevent future regression
- Fixes#1195
- Fixes#1079 and #909
- Need to exclude non-editable file/path/URI deps from the list we give
to pip-tools
- We should really separate this logic from the logic that supplies what
is supposed to be a list of packages
Add tests and comments to prevent regression
- Ensure we resolve install_requires from local setup.py files
- Squash commits
Dan Ryan
kennethreitz