Closed pepie34 closed 1 year ago
Don't use the system python path but the current python env path so the building process can be done on custom python environments.
This is needed for example to compile the project on macOS under conda python env.
/usr/bin/env python3 resolves to /usr/bin/python3 when no custom python env is activated
Looks OK to me. I've just had a grep through all the Python 3 modules I package for a distribution, and it's about equally common to have a #! line using env and to not have a #! line at all.
Don't use the system python path but the current python env path so the building process can be done on custom python environments.
This is needed for example to compile the project on macOS under conda python env.
/usr/bin/env python3 resolves to /usr/bin/python3 when no custom python env is activated