Author jt
Recipients jeremy.kloth, jkloth, jt, ncoghlan, paul.moore, steve.dower, tim.golden, zach.ware
Date 2019-02-16.18:24:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Okay, I just tested switching to the NuGet package and appear to have hit some sort of issue:

C:\myproject\tools\windows\.python-win\python\tools\python.exe: No module named venv
Traceback (most recent call last):
  File "C:\myproject\tools\windows\\", line 129, in <module>
  File "C:\myproject\tools\windows\\", line 60, in do_build
    ".python-win", "spen-venv")
  File "C:\myproject\tools\windows\.python-win\python\tools\Lib\", line 395, in check_output
  File "C:\myproject\tools\windows\.python-win\python\tools\Lib\", line 487, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['C:\\myproject\\tools\\windows\\.python-win\\python\\tools\\python.exe', '-m', 'venv', 'C:\\myproject\\tools\\windows\\.python-win\\spen-venv']' returned non-zero exit status 1.

Is this expected with the NuGet variant? Can I somehow install 'venv' on top? I didn't have this issue with the install obtained by running the Windows Installer with /Q
Date User Action Args
2019-02-16 18:24:46jtsetrecipients: + jt, paul.moore, ncoghlan, tim.golden, jkloth, jeremy.kloth, zach.ware, steve.dower
2019-02-16 18:24:46jtsetmessageid: <>
2019-02-16 18:24:46jtlinkissue36010 messages
2019-02-16 18:24:46jtcreate