Package: keyring-subprocess
keyring-subprocessA minimal dependency keyring backend for lean virtual environments.This is achieved by locating a virtual environment which haskeyring-subprocess[landmark]installed whosekeyring-subprocesscan be found
on the PATH.keyring-subprocessis effectively a renamedkeyringexecutable and serves as a more unique landmark file.The virtual environment that is found this way should have the actualkeyringbackend(s) you need installed into it.ProsMinimal dependencies for a cleanpip listcommand and to always be
compatible with the rest of your dependencies. Which makes it more
suitable to be added toPYTHONPATHafter installing with Pip's--targetflag.Haskeyringand the minimal required
dependencies vendored to make thechainerandnullbackends work.It uses the ModuleSpec apis provided byPEP451to make the vendoredkeyringimportable.Provices an extra namedlandmarkthat will provide thekeyring-subprocessexecutable.Provides avirtualenvSeedernamedkeyring-subprocess.SetVIRTUALENV_SEEDERtokeyring-subprocessor setseederin the
config file to the same value.Provides asitecustomizeentry point for thesitecustomize-entrypointspackage. This can be useful if you install it somewhere that is not a
so-called site directory by using Pip's--targetflag.You can install bothkeyring-subprocessandsitecustomize-entrypointsin one go by executingpip install keyring-subprocess[sitecustomize].sitecustomize-entrypointsis required if you ifkeyring-subprocessis installed into aPYTHONPATHlocation.ConsIt does requirekeyring-subprocess[landmark]to be installed into a virtual
environment whosekeyring-subprocesscan be found on the PATH.Adds, or replaces, points of failures. Depending on how you look at it.Being able to importkeyring,importlib_metadataandzippbutpip listnot listing them might be confusing and not very helpful during
debugging.Example on WindowsThis is a Powershell script which installsPipxintoC:\Users\Public\.local\pipx.First it sets some environment variables, includingVIRTUALENV_SEEDER.Then it installs keyring via Pipx and injects artifacts-keyring and
keyring-subprocess[landmark] into the virtual environment of keyring.Lastly it installs keyring-subprocess and sitecustomize-entrypoints into
Pipx's shared virtualenv which Pipx makes sure is available to all virtual
environments it manages.When using your new Pipx installation to install Poetry or Pipenv the virtual
environment created by virtualenv will contain keyring-subprocess. This should
cause installing the project dependencies from your private repository to
succeed!Assuming of couse that your private repository requires artifacts-keyring to
authenticate, and is therefor a Azure DevOps Artifact Feed. If this is not the
case this should be easily fixed by replacing artifacts-keyring by the
package that provides the keyring backend that you actually need.$EnvironmentVariableTarget=$(Read-Host"Target environment (User/Machine) [Machine]").Trim();`if($EnvironmentVariableTarget-eq""){$EnvironmentVariableTarget="Machine";}`if($EnvironmentVariableTarget-inotin@("User","Machine")){Write-Host"Invalid option.";}else{try{$PATH=$env:PATH;$PIP_NO_INPUT=$env:PIP_NO_INPUT;$PIP_INDEX_URL=$env:PIP_INDEX_URL;$ExecutionPolicy=Get-ExecutionPolicy;try{if(!$env:PIPX_HOME){$env:PIPX_HOME=[Environment]::GetEnvironmentVariable("PIPX_HOME",$EnvironmentVariableTarget);};if(!$env:PIPX_HOME){[Environment]::SetEnvironmentVariable("PIPX_HOME","C:\Users\Public\.local\pipx",$EnvironmentVariableTarget);$env:PIPX_HOME=[Environment]::GetEnvironmentVariable("PIPX_HOME",$EnvironmentVariableTarget);};if(!$env:PIPX_BIN_DIR){$env:PIPX_BIN_DIR=[Environment]::GetEnvironmentVariable("PIPX_BIN_DIR",$EnvironmentVariableTarget);};if(!$env:PIPX_BIN_DIR){[Environment]::SetEnvironmentVariable("PIPX_BIN_DIR","C:\Users\Public\.local\bin",$EnvironmentVariableTarget);$env:PIPX_BIN_DIR=[Environment]::GetEnvironmentVariable("PIPX_BIN_DIR",$EnvironmentVariableTarget);};if(!$env:VIRTUALENV_SEEDER){$env:VIRTUALENV_SEEDER=[Environment]::GetEnvironmentVariable("VIRTUALENV_SEEDER",$EnvironmentVariableTarget);};if(!$env:VIRTUALENV_SEEDER){[Environment]::SetEnvironmentVariable("VIRTUALENV_SEEDER","keyring-subprocess",$EnvironmentVariableTarget);$env:VIRTUALENV_SEEDER=[Environment]::GetEnvironmentVariable("VIRTUALENV_SEEDER",$EnvironmentVariableTarget);};if(Test-Path"C:\Users\Public\.local\bin\pipx.exe"){try{$env:PATH=[Environment]::GetEnvironmentVariable("PATH",$EnvironmentVariableTarget);Get-Command-Namepipx-OutVariablepipx>$null;}catch{}finally{$env:PATH=$PATH}if(-not$pipx){$env:PATH=$PATH="C:\Users\Public\.local\bin;"+$env:PATH;};return};[Environment]::SetEnvironmentVariable("Path","C:\Users\Public\.local\bin;"+[Environment]::GetEnvironmentVariable("Path",$EnvironmentVariableTarget),$EnvironmentVariableTarget);$env:PATH=$PATH="C:\Users\Public\.local\bin;"+$env:PATH;$env:PIP_NO_INPUT='1';$env:PIP_INDEX_URL='https://pypi.org/simple/';}catch{throw"Run as Administrator or choose`"User`"as the target environment"};$venv=Join-Path$env:TEMP".venv"<# Use the py executable if it can be found and default to the python executable #>Get-Command-Namepy,python-OutVariablepy2>&1>$null;$py=$py[0];$env:PATH=$(&$py-c"import sys; import sysconfig; import os; from pathlib import Path; from itertools import chain; print(os.pathsep.join(chain(set([str(Path(sys.executable).parent), sysconfig.get_path(`"`"scripts`"`")]), [os.environ[`"`"PATH`"`"]])))");&$py-mvenv"$venv";Set-ExecutionPolicy-ExecutionPolicyBypass-ScopeProcess-Force;."$venv\Scripts\Activate.ps1";&$py-mpipinstall-qqq--no-input--isolatedpipx;pipxinstall--pip-args="--no-input --isolated"pipx;pipxinstall--pip-args="--no-input --isolated"keyring;pipxinject--pip-args="--no-input --isolated"keyringartifacts-keyring;pipxinject--pip-args="--no-input --isolated"--include-apps--include-depskeyringkeyring-subprocess[landmark];pipxinstall--pip-args="--no-input --isolated"virtualenv;<# Minor hack since Pipx does not allow us to do this via the cli #>&"$env:PIPX_HOME\shared\Scripts\pip.exe"install--no-input--isolatedkeyring-subprocess[sitecustomize];deactivate;if(Test-Path-Path$venv){Remove-Item-Path"$venv"-Recurse-Force;}<# Fill virtualenv's wheel cache with keyring-subprocess and up-to-date versions of the embeded wheels #><# I might take a stab at making keyring-subprocess a Quine at some point... #><# Update: I started and figured out that the size of the vendored dependencies are a problem #><# DEFLATE uses a 32KiB sliding window so the size of the .whl before making it a quine should definately be below 64KiB #><# Maybe I can get Pip to vendor keyring and keyring-subprocess? #>virtualenv--upgrade-embed-wheels;virtualenv--seederkeyring-subprocess--download$venv;}catch{$Error;$env:PATH=$PATH;}finally{if($venv-and(Test-Path-Path$venv)){Remove-Item-Path"$venv"-Recurse-Force;}$env:PIP_NO_INPUT=$PIP_NO_INPUT;$env:PIP_INDEX_URL=$PIP_INDEX_URL;if($ExecutionPolicy){Set-ExecutionPolicy-ExecutionPolicy$ExecutionPolicy-ScopeProcess-Force;}}}