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

Share a venv, if possible #155

Merged
merged 10 commits into from
Mar 22, 2022

Conversation

ericsnowcurrently
Copy link
Member

This also includes a few small fixes.

@oraluben
Copy link
Contributor

Are there any risks that dependencies of benchmark a will affect the result of benchmark b when they share a venv? Or this will be resolved manually. e.g. .pth file or something like that.

@ericsnowcurrently
Copy link
Member Author

AFAIK, the only risk is if one benchmark modifies any of the dependencies, which shouldn't happen.

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

Successfully merging this pull request may close these issues.

2 participants