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
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 supportsconda and virtualenv) and might make it easier to add more flexibility into the environment management, while also being easier to maintain.
The text was updated successfully, but these errors were encountered:
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.
On the Scientific Python Discord it was noted that perhaps existing tools like
tox
could be used for managing the environmentsasv
needs.Currently this is bundled into
asv
itself, and works alright. However, a possible cleanup would be delegating tonox
(which also supportsconda
andvirtualenv
) and might make it easier to add more flexibility into the environment management, while also being easier to maintain.The text was updated successfully, but these errors were encountered: