Skip to content
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

ENH: Consider delegating to nox #1293

Open
HaoZeke opened this issue May 21, 2023 · 2 comments
Open

ENH: Consider delegating to nox #1293

HaoZeke opened this issue May 21, 2023 · 2 comments

Comments

@HaoZeke
Copy link
Member

HaoZeke commented May 21, 2023

On the Scientific Python Discord it was noted that perhaps existing tools like tox could be used for managing the environments asv needs.

Currently this is bundled into asv itself, and works alright. However, a possible cleanup would be delegating to nox (which also supports conda and virtualenv) and might make it easier to add more flexibility into the environment management, while also being easier to maintain.

@mattip
Copy link
Contributor

mattip commented May 21, 2023

Before work on this, we should have a downstream user clearly state why virtualenv does not suit what they are trying to do with ASV.

@trexfeathers
Copy link

A team I work in adopted Nox for several projects, but we have since decided to switch to Tox. It is easier to write things in Nox, but we felt that the 10x popularity of Tox promised a healthier future and easier collaboration with other developers.

I don't have a strong opinion myself; just thought it was worth sharing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants