-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update Noxfiles to use new Nox #6170
Comments
Reopening: the root noxfile needs updating as well. |
@theacodes it looks like making the new |
I'll leave that up to @busunkim96. Holler if y'all need help. |
@busunkim96 #6196 has a patch for the |
Should we just switch it over to the same one we use for Kokoro?
…On Thu, Oct 11, 2018 at 9:45 AM Tres Seaver ***@***.***> wrote:
@busunkim96 <https://github.com/busunkim96> #6196
<#6196> has a patch
for the nox.py -> noxfile.py part, but don't have the keys / know-how to
publish a new Docker image to googleapis/nox.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#6170 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAPUc5jnm6rq771Kc3bH92d6yKSRFLPJks5uj3W3gaJpZM4XK1WG>
.
|
AFAICT, the # Remove old nox
python3.6 -m pip uninstall --yes --quiet nox-automation
# Install nox
python3.6 -m pip install --upgrade --quiet nox
python3.6 -m nox --version |
Nox recently made a big change from declarative to imperative and broke the Noxfile API.
We need to update our Noxfiles to work with the new API and update our test scripts to install
nox
(instead ofnox-automation
) and invokepython3 -m nox {args}
.Most projects just need to do a few steps:
session_{name}
sessions and use@nox.session
instead.session.interpreter
, use@nox.session(py='...')
nox.parametrize
for multiple Pythons, use@nox.session(py=['..', '..'])
.The text was updated successfully, but these errors were encountered: