Joss Gray wrote: > I managed to build it minus lots of modules, that luckily i'm not using.
Don't ignore Zach's comment. Unless you have also built Python itself with VS2013 (which is unlikely), you are just asking for trouble. You are mixing two different versions of the C runtime library. You will be allocating objects in one version of the CRT and freeing them in another. In might work some of the time, but you are going to have inexplicable errors. > On Thu, Jul 24, 2014 at 5:10 PM, Zachary Ware > <zachary.ware+py...@gmail.com <mailto:zachary.ware+py...@gmail.com>> > wrote: > > On Thu, Jul 24, 2014 at 10:06 AM, Joss Gray <j...@jossgray.net > <mailto:j...@jossgray.net>> wrote: > > Has anybody successfully built pywin32 with Visual Studio 2013 ( > v120 > > toolkit ) and using the windows 8.1 sdk? > > I haven't tried, but I wouldn't expect useful results unless you're > also compiling Python yourself (which does not yet officially support > anything newer than VS 2010). > > -- > Zach > > -- Tim Roberts, t...@probo.com Providenza & Boekelheide, Inc.
_______________________________________________ python-win32 mailing list python-win32@python.org https://mail.python.org/mailman/listinfo/python-win32