New submission from wolfgang kuehn <wolfgang-ku...@decatur.de>:
I just installed Python3.10.1 from the Windows 10 App Store. Most workflows depend on creating virtual environments, but (1) python -m venv venv # -> Error 1260: Windows cannot open this program because it has been prevented by a software restriction policy However, a (2) python -m venv --without-pip venv completes, only to not allow execution of (3) .\venv\Scripts\python.exe # -> Error 1260: Windows cannot open this program because it has been prevented by a software restriction policy Reason for this probably are the (not so unreasonable) cooperate Software Restriction Policy (in our case enforced by Applocker): You are not allowed to execute from where you are allowed to write. So basically Python is broken in many MS Windows cooperate settings. Cooperate meaning (Software Restriction Policies) + (Usage of Virtual Environments). And my feeling is that it does not need to be, the virtual environment implementation with those *.exe copies being a kludge, IMHO. Note: (2) is reminiscent of bpo-45337, which was fixed with 3.9. ---------- components: Installation messages: 408380 nosy: wolfgang-kuehn priority: normal severity: normal status: open title: Cannot use virtual environment on Windows 10 in cooperate security settingss versions: Python 3.10, Python 3.6, Python 3.7, Python 3.8, Python 3.9 _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue46056> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com