From 53d8d2f45282a402efc864591757f83f991c31dd Mon Sep 17 00:00:00 2001 From: David Hotham Date: Sat, 16 Mar 2024 14:29:03 +0000 Subject: [PATCH] remove advice re seeding keyring backends (#9164) (cherry picked from commit 75453c2dc3086e0c183d24cd4ab5c16ca860ea7e) --- docs/repositories.md | 6 ------ 1 file changed, 6 deletions(-) diff --git a/docs/repositories.md b/docs/repositories.md index 4083cb8e057..f8fe201821e 100644 --- a/docs/repositories.md +++ b/docs/repositories.md @@ -532,12 +532,6 @@ Microsoft's [artifacts-keyring](https://pypi.org/project/artifacts-keyring/) get valid credentials. It will need to be properly installed into Poetry's virtualenv, preferably by installing a plugin. -If you are letting Poetry manage your virtual environments you will want a virtualenv -seeder installed in Poetry's virtualenv that installs the desired keyring backend -during `poetry install`. To again use Azure DevOps as an example: [azure-devops-artifacts-helpers](https://pypi.org/project/azure-devops-artifacts-helpers/) -provides such a seeder. This would of course best achieved by installing a Poetry plugin -if it exists for you use case instead of doing it yourself. - {{% /note %}} Alternatively, you can use environment variables to provide the credentials: