* Actually filter out missing interpreters
This fixes https://github.com/pypa/pipenv/issues/5261.
Before this change, I would get a "The Python interpreter can't be
found" error when running `pipenv install --system` with a python3 but
no python.
* Depend on requests and certifi from vendored pip and remove it as explicit vendor dependency.
* Documentation tweak.
* Add a news fragment.
* Update remaining vendor dependencies to point at the pip requests.
* vendoring task needs requests.
* vendor in pip==22.0.4
* updating vendor packaging version
* update pipdeptree to fix pipenv graph with new version of pip.
* Vendoring of pip-shims 0.7.0
* Vendoring of requirementslib 1.6.3
* Update pip index safety restrictions patch for pip==22.0.4
* Update patches
* exclude pyptoject.toml from black to see if that helps.
* Move this part of the hash collection back to the top (like prior implementation) because it affects the outcome of this test now in pip 22.0.4
* Add pytest-cov; Remove code references to pip-tools and refactor method _build_package_list
* Regenerate lock file.
* Add back required typing-extensions, not sure how it got dropped from locking previously.
* Adopt the setup.cfg for coverage config.
* Actually pin to the version of click we have vendored in.
* Do not adopt coverage for CI since it slows everything down. Fix py36 dependency pinning.
* Drop support for 3.6 in this PR.
* No need to exclude the vendor and patched directory from the coverage reprot.
* Add .pre-commit-config.yaml to the project and exclude tests (for now). This does not include the MyPy linting that pip does but does include everything else.
- Automatically release when tags are pushed to master
- Release automation will build wheel and sdist + upload to pypi
- Added test pypi as initial target
- Updated version update scripts to help with automatic version
management
Signed-off-by: Dan Ryan <dan@danryan.co>
Matt Davis