![]() The inspect and installation report formats are now declared stable, and their version ( #11381)Įnable the use of keyring found on PATH. Modify the externally managed environment. This allows a downstream Python distributor to prevent users from using pip to Implement logic to read the EXTERNALLY-MANAGED file as specified in PEP 668. Emit theĪrchive_info.hashes dictionary in direct_url.json. ( #11773)Ĭhange the hashes in the installation report to be a mapping. Improve handling of isolated build environments on platforms thatĬustomize the Python’s installation schemes, such as Debian andĭo not crash in presence of misformatted hash field in direct_url.json. Implement -break-system-packages to permit installing packages intoĮXTERNALLY-MANAGED Python installations. Ignore PIP_REQUIRE_VIRTUALENV for pip index ( #11671) Make it clear that requirements/constraints file can be a URL ( #11954) Quote extras in the pip install docs to guard shells with default glob ( #11809)Īdd username to Git over SSH example. ( #11775)Īdd SECURITY.md to make the policy offical. Patch pkg_resources to remove dependency on jaraco.text.Ĭross-reference the -python flag from the -prefix flag,Īnd mention limitations of -prefix regarding script installation. When installing an archive from a direct URL or local file, populateĭownload_ in the installation report, in addition to the legacy Specified for a local directory installation. When package A depends on package B provided as a direct URL dependency including a hashĮmbedded in the link, the -require-hashes option did not warn when user supplied hashesĬorrectly report requested_extras in the installation report when extras are ( #11889)įix and improve the parsing of hashes embedded in URL fragments. Instead, these results areĬached for the duration of an uninstall operation, resulting in improved Normalize_path() repeatedly on the same paths. The uninstall and install -force-reinstall commands no longer call More consistent resolution backtracking by removing legacy hack related to setuptools resolution ( #11837) ( #11719)Ĭorrect the way to decide if keyring is available. Normalize paths before checking if installed scripts are on PATH. ( #9752)įix grammar by changing “A new release of pip available:” to “A new release of pip is available:” in the notice used for indicating that. In the case of virtual environments, configuration files are now also included from the base installation. See the Authentication page in the documentation for more info. Support wheel cache when using -require-hashes. ![]() Settings to several requirements, users should provide the requirements as CLI Not propagate to requirements provided in requirement files. Stop propagating CLI -config-settings to the build dependencies. Warn if -hash is used on a line without requirement in a requirements file. This also makes pathological cases fail quicker. Reduce the number of resolver rounds, since backjumping makes the resolver more efficient in finding solutions. ( #11681)Īdd -C as a short version of the -config-settings option. Only pass the last value if the same key was used multiple times. The build backend as a list, as opposed to the previous behavior, where pip would When the same key is specified multiple times, all values are passed to The -config-settings/ -C option now supports using the same key multiple Support a per-requirement -config-settings option in requirements files. Present conflict information during installation after each choice that is rejected (pass -vv to pip install to show it) ( #10937)ĭisplay dependency chain on each Collecting/Processing log line. Specify egg-link location in assertion message when it does not match installed location to provide better error message for debugging. Instead of setup.py install and setup.py develop for project without When the wheel package is not installed, pip now uses the default build backend Remove setup.py install fallback when building a wheel failed for projects without In the future the presence of config settings will automaticallyĮnable the default build backend for legacy projects and pass the setttings to it. Using -config-settings with projects that don’t have a pyproject.toml now printsĪ deprecation warning. It onlyĭeprecate -build-option and -global-option. no-binary does not disable the cache of locally built wheels anymore. ![]() no-binary does not imply setup.py install anymore. Remove support for the deprecated -install-options. Update documentation to reflect the new behavior of using the cache of locallyīuilt wheels in hash-checking mode. Revert pkg_resources (via setuptools) back to 65.6.3 Revert #11487, as it causes issues with virtualenvs created by the Windows Store distribution of Python. ![]() Major and minor releases of pip also include changes listed within ![]()
0 Comments
Leave a Reply. |