[issue39656] shebanged scripts can escape from `venv` depending on how it was created

Change by Vinay Sajip : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___ P

[issue39656] shebanged scripts can escape from `venv` depending on how it was created

Vinay Sajip added the comment: New changeset 58ec58a42bece5b2804b178c7a6a7e67328465db by Anthony Sottile in branch 'master': bpo-39656: Ensure `bin/python3.#` is always present in virtual environments on POSIX (GH-19030) https://github.com/python/cpython/commit/58ec58a42bece5b2804b178c7a6a7e

[issue39656] shebanged scripts can escape from `venv` depending on how it was created

Change by Anthony Sottile : -- keywords: +patch pull_requests: +18379 stage: -> patch review pull_request: https://github.com/python/cpython/pull/19030 ___ Python tracker ___

[issue39656] shebanged scripts can escape from `venv` depending on how it was created

New submission from Anthony Sottile : This is distilled from a larger example to be small/silly, however this caused real problems A script which was intended for python3.6 exactly was written as follows: ``` #!/usr/bin/env python3.6 ... ``` when creating a virtualenv with `python3.6 -m venv