[issue35644] venv doesn't work on Windows when no venvlauncher executable present

Steve Dower added the comment: Doesn't seem to be anything to fix upstream here. -- resolution: -> not a bug status: open -> closed ___ Python tracker ___ ___

[issue35644] venv doesn't work on Windows when no venvlauncher executable present

Steve Dower added the comment: It should just build directly from venv[w]launcher.vcxproj, though you'll need to rename venv[w]launcher.exe to python[w].exe (otherwise they'd conflict in the build directory). -- ___ Python tracker

[issue35644] venv doesn't work on Windows when no venvlauncher executable present

Ray Donnelly added the comment: Thanks Steve, the sys.path value from the first comment can be discarded, it was running the wrong Python! The 'old' mechanism (which my patch reverts to) does copy all the necessary DLLs already. I released builds with this patch now and venv works fine (test

[issue35644] venv doesn't work on Windows when no venvlauncher executable present

Steve Dower added the comment: The installed venv seems to be okay, so I'm going to assume it's something about your own build. Now I realise I haven't ever tried virtualenv against 3.6 or later... no idea what state that's in. -- ___ Python trac

[issue35644] venv doesn't work on Windows when no venvlauncher executable present

Steve Dower added the comment: That patch will break the case where the launcher *is* present, which is why it was changed. If you're sure the launcher won't be present under Scripts/nt, then that patch is okay. You'll probably need to add code to also copy python37.dll and vcruntime140.dll,

[issue35644] venv doesn't work on Windows when no venvlauncher executable present

Change by Ray Donnelly : -- title: venv doesn't do what it claims to do (apears not to work at all?) -> venv doesn't work on Windows when no venvlauncher executable present ___ Python tracker ___