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

Invoke python all via Python3_EXECUTABLE #3680

Closed
ye-luo opened this issue Dec 18, 2021 · 3 comments · Fixed by #3745
Closed

Invoke python all via Python3_EXECUTABLE #3680

ye-luo opened this issue Dec 18, 2021 · 3 comments · Fixed by #3745
Assignees
Labels

Comments

@ye-luo
Copy link
Contributor

ye-luo commented Dec 18, 2021

Describe the bug

../CMake/compareGCOV.cmake:  execute_process(COMMAND python ${CTEST_SOURCE_DIRECTORY}/tests/coverage/compare_gcov.py --action merge --base-dir
../CMake/compareGCOV.cmake:  execute_process(COMMAND python ${CTEST_SOURCE_DIRECTORY}/tests/coverage/compare_gcov.py --action compare --base-dir
../CMake/run_pyscf.cmake:  add_pyscf_test(${BASE_NAME} python ${MY_WORKDIR} ${TEST_INPUT_PREFIX}.py)
../CMake/macros.cmake:            ${qmcpack_SOURCE_DIR}/tests/scripts/check_scalars.py
../CMake/test_labels.cmake:      COMMAND ${qmcpack_SOURCE_DIR}/tests/scripts/test_labels.py ${TEST_NAME} ${QMC_CUDA} ${QMC_COMPLEX}

There are more if I looked into tests folder.

Are there ways to stop running python via shebang so we can caught all places?

@ye-luo ye-luo added the bug label Dec 18, 2021
@PDoakORNL
Copy link
Contributor

sed the shebang out, run everything, put them back?

@quantumsteve
Copy link
Contributor

Which, if any, shebangs do we need to keep in the repository?

@jtkrogel
Copy link
Contributor

Please keep all that are present in the nexus sub-directory. I don't want anyone to have to do python3 qmca ..., etc.

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

Successfully merging a pull request may close this issue.

4 participants