Message260228
Indeed, and in fact *all* scripts written to a venv's bin directory hard-code the path to that venv's interpreter. This confers the benefit that such scripts never need the venv to be explicitly activated - you can e.g. point crontab entries to them directly.
You're better off making the Jenkins job build the environment in its workspace before using it - venvs are intended to be reproducible and, consequently, disposable. |
|
Date |
User |
Action |
Args |
2016-02-13 09:47:36 | vinay.sajip | set | recipients:
+ vinay.sajip, barry, r.david.murray, moorecm, André Caron |
2016-02-13 09:47:36 | vinay.sajip | set | messageid: <1455356856.21.0.419718426797.issue25833@psf.upfronthosting.co.za> |
2016-02-13 09:47:36 | vinay.sajip | link | issue25833 messages |
2016-02-13 09:47:35 | vinay.sajip | create | |
|