Message176122
| Author | pitrou |
|---|---|
| Recipients | barry, brett.cannon, christian.heimes, eric.araujo, lemburg, pitrou, serhiy.storchaka |
| Date | 2012-11-22.19:29:43 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1353612526.3321.0.camel@localhost.localdomain> |
| In-reply-to | <1353611290.05.0.790265308245.issue16499@psf.upfronthosting.co.za> |
| Content | |
|---|---|
> How shall I handle venv? I'm reluctant to disable venv in site.py > although it allows a user to modify sys.path. However it's only an > issue under two circumstances: > > (1) The user either needs write permissions to the parent directory of > the python executable. > (2) The script doesn't hard code the path to the interpreter in its > shebang. > > Point 1 allows the user to mess with the system in more serious ways. > The second point can be avoided with a correctly written shebang line. I agree that venv shouldn't be a problem. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2012-11-22 19:29:43 | pitrou | set | recipients: + pitrou, lemburg, barry, brett.cannon, christian.heimes, eric.araujo, serhiy.storchaka |
| 2012-11-22 19:29:43 | pitrou | link | issue16499 messages |
| 2012-11-22 19:29:43 | pitrou | create | |