You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm working in an Azure devOps company environment so we use a custom feed for our private Python packages. In my CI I set an environment variable PIP_EXTRA_INDEX_URL to have access to this feed.
As this is an env variable it will crash if I don't start by installing both keyring and artifacts-keyring for authentication.
At the moment I'm forced to run the following in each session definition:
@nox.session(reuse_venv=True)defsomething(session):
session.install("keyring", "artifacts-keyring") # need to be the first thing I dosession.install("pre-commit")
session.run("pre-commit", "run", "--a", *session.posargs)
The text was updated successfully, but these errors were encountered:
I think what is missing is the inverse of session.notify("other_session") + share the venv. Right now you can construct a chain of things that are done after, but not what should be done before.
Something like session.require("common", share_venv=True), which would invoke the "common" session where you define whatever you need as preparation BEFORE the rest of this session, and it is executed on the venv of the invoking session. The notify alone does not cut it because from the point of view of common you have no idea of what should be done after.
The share_venv would also be useful for .notify, so you can pile up actions happening on the same environment?
How would this feature be useful?
I'm working in an Azure devOps company environment so we use a custom feed for our private Python packages. In my CI I set an environment variable
PIP_EXTRA_INDEX_URL
to have access to this feed.As this is an env variable it will crash if I don't start by installing both
keyring
andartifacts-keyring
for authentication.At the moment I'm forced to run the following in each session definition:
The text was updated successfully, but these errors were encountered: