On 2016-08-25 21:27, Ben Finney wrote:
That's exactly the wrong thing to do. Your shebang line should *not*
assume a custom location of the Python interpreter.
It's the responsibility of the operating system or virtualenv to
provide
the Python interpreter command in a standard place.
Instead, use:
#! /usr/bin/env python3
or:
#! /usr/bin/python3
and leave it to the operating system and the virtualenv to provide the
Python interpreter correctly.
Thanks, Ben, for your input.
Am I to assume that if I have activated a virtualenv, then the following
shebang
#!/usr/bin/env python
will use the python specified in the venv/bin/?
_______________________________________________
Tutor maillist - Tutor@python.org
To unsubscribe or change subscription options:
https://mail.python.org/mailman/listinfo/tutor
