If virtualenv is not available, we can look for py3's venv instead. We only use this particular env for installing and running the test suite.
Diff Detail
- Repository
- rG LLVM Github Monorepo
Unit Tests
Event Timeline
I created this to make it easier to run builds on systems that have python3 but don't have virtualenv installed. python3 comes with venv.
https://docs.python.org/3/library/venv.html says that at one time pyvenv was recommended but that was deprecated in favor of "python3 -m venv" which works very similar to virtualenv.
llvm/utils/release/test-release.sh | ||
---|---|---|
309 | Should this be inside an if [ $do_test_suite = "yes" ]; ? I think virtualenv is only used for test_suite. |
llvm/utils/release/test-release.sh | ||
---|---|---|
309 |
Yes, that seems right. I will change it. |
llvm/utils/release/test-release.sh | ||
---|---|---|
497–503 | I think this would be a better place to set up ${venv} (more related to test-suite) than in export_sources() |
Should this be inside an if [ $do_test_suite = "yes" ]; ?
I think virtualenv is only used for test_suite.