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
so I can say that one wheel is plenty for all environments, like
nox.options.one_wheel_for_all=True
I don't think Nox needs as fine-grained controls like tox has – courtesy of Python. But this one use case is common enough to save a lot of CPU and IO cycles.
Describe alternatives you've considered
You can do it by hand, either by passing an argument:
But but both require manual intervention and present sharp edges. E.g. calling nox -s tests -p 3.11 won't rebuild the package and will run the tests against outdated code.
If this would be handled by Nox, I would expect it to make sure the wheel is built when I call session.install('.')
Anything else?
No response
The text was updated successfully, but these errors were encountered:
How would this feature be useful?
Currently, Nox builds and installs a fresh wheel for every session. That is slow & unnecessary for 99.999% of situations.
Describe the solution you'd like
I'd like something akin to tox's
(see also https://hynek.me/articles/turbo-charge-tox/)
so I can say that one wheel is plenty for all environments, like
I don't think Nox needs as fine-grained controls like tox has – courtesy of Python. But this one use case is common enough to save a lot of CPU and IO cycles.
Describe alternatives you've considered
You can do it by hand, either by passing an argument:
Or an explicit environment:
But but both require manual intervention and present sharp edges. E.g. calling
nox -s tests -p 3.11
won't rebuild the package and will run the tests against outdated code.If this would be handled by Nox, I would expect it to make sure the wheel is built when I call
session.install('.')
Anything else?
No response
The text was updated successfully, but these errors were encountered: