pip-api

pip-api copied to clipboard

Bumps the actions group with 2 updates: [softprops/action-gh-release](https://github.com/softprops/action-gh-release) and [actions/upload-artifact](https://github.com/actions/upload-artifact). Updates `softprops/action-gh-release` from 1 to 2 Release notes Sourced from softprops/action-gh-release's releases. v2.0.0 update actions.yml declaration to node20 to address...

dependabot[bot]

Deprecation warning when using `pip_api` on Python 3.11

2

**Reproduction** ``` python3.11 -Wall -c "import pip_api" /lib/python3.11/site-packages/pip_api/_vendor/pyparsing.py:108: DeprecationWarning: module 'sre_constants' is deprecated import sre_constants ``` **Root cause** `sre_constants` is imported by the vendored `pyparsing` module: https://github.com/di/pip-api/blob/5ac3ec840dd4eb0fd20ea69d5d2362472e0d4daf/pip_api/_vendor/pyparsing.py#L108 see: https://github.com/python/cpython/issues/91308

jamesclark-Zapata

Fixes #195.

di

Support `pip install`'s new `--dry-run` and `--report` flags

8

As of version 22.2, `pip` supports two new flags on `pip install`: `--dry-run` to perform a "dry run" of the installation steps, and `--report` to generate a JSON-formatted installation report....

woodruffw

Add link to `pipster` in README?

1

Given @di 's [comment](https://github.com/reynoldsnlp/pipster/issues/45#issuecomment-1553010062), would it be useful to add a link to `pipster` in `pip-api`'s README so that people looking for this functionality can easily find it?

reynoldsnlp

Right now, almost all of `pip-api`'s state revolves around calls to `pip`, which in turn is located by `pip-api` by invoking it relative to the current interpreter (in effect `{sys.executable}...

woodruffw

pyproject: port build to pyproject.toml

7

WIP. Signed-off-by: William Woodruff

woodruffw

Switch to `pyproject.toml` for the project build?

2

`pip-api` is a pure Python package, so switching it fully over to `pyproject.toml` (the way we've done for `pip-audit` and `sigstore-python`) should be pretty straightforward.

woodruffw

Reject requirements that are both hashed and editable?

1

The current requirements parser allows a requirement to specify both `--hash ...` and `-e`, despite the two being incompatible and rejected by `pip` itself (https://github.com/pypa/pip/issues/4995). IMO, we should probably reject...

woodruffw

Preserve comments and pre-evaluated markers when parsing requirements

7

`pip-api` currently (and very reasonably) strips these as part of its `parse_requirements` API, removing all comments and any requirement lines whose environment markers are not satisfied. This is the correct...

woodruffw