python-setup: Update comment with fully qualified configuration name
This commit is contained in:
parent
5566638d56
commit
3b0a2f607d
1 changed files with 4 additions and 4 deletions
|
|
@ -38,10 +38,10 @@ def install_packages_with_poetry():
|
||||||
# add a workaround. See
|
# add a workaround. See
|
||||||
# https://github.com/python-poetry/poetry/issues/2692#issuecomment-1235683370
|
# https://github.com/python-poetry/poetry/issues/2692#issuecomment-1235683370
|
||||||
"PYTHON_KEYRING_BACKEND": "keyring.backends.null.Keyring",
|
"PYTHON_KEYRING_BACKEND": "keyring.backends.null.Keyring",
|
||||||
# Projects that specify `in-project = true` in their poetry.toml would get the
|
# Projects that specify `virtualenvs.in-project = true` in their poetry.toml
|
||||||
# venv created inside the repo directory, which would cause CodeQL to consider
|
# would get the venv created inside the repo directory, which would cause CodeQL
|
||||||
# it as user-written code. We don't want this to happen.
|
# to consider it as user-written code. We don't want this to happen. see
|
||||||
# see https://python-poetry.org/docs/configuration/#virtualenvsin-project
|
# https://python-poetry.org/docs/configuration/#virtualenvsin-project
|
||||||
"POETRY_VIRTUALENVS_IN_PROJECT": "False",
|
"POETRY_VIRTUALENVS_IN_PROJECT": "False",
|
||||||
}
|
}
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue