On 14 March 2016 at 17:15, Arie van Wingerden <xapw...@gmail.com> wrote: > I've fixed the quoting below. Can you not top-post please Arie? > On 14 March 2016 at 16:59, Arie van Wingerden < xapw...@gmail.com > wrote: >> 2016-03-14 15:59 GMT+01:00 Oscar Benjamin < oscar.j.benja...@gmail.com >: >>> >>> On 14 March 2016 at 12:07, Arie van Wingerden < xapw...@gmail.com > >>> wrote: >>> > that is weird. I am using Windows 10 and get exactly the same >>> > "warnings" >>> > when I run PyInstaller. >>> > But the update you mention is only available for up to Windows 8.1. >>> > >>> > What about Windows 10 then?? >>> >>> I'm not sure what you mean. Windows 10 should already have the UCRT so >>> it shouldn't need the update. Is it possibly a bug in pyinstaller? >>> What exactly are you doing to see this error message? >> Hi Oscar, >> >> no. By default W10 appears to have them NOT installed (at least that is >> what >> I experienced). >> You really need the SDK to be installed. >> Also the path must point to the libs installed by the SDK. >> Now it works without all those warnings. > What works? Python or pyinstaller or what? If pyinstaller do you see > the error when creating an executable or when running it? > -- > Oscar > > Creating standalone exe with pyinstaller gave all the warnings about missing > libs.
Okay well then that's a separate issue. The OP was unable to run Python because these libs were missing. You are trying to compile C code using pyinstaller which means that you need these libs available on PATH I guess. -- Oscar -- https://mail.python.org/mailman/listinfo/python-list
