[python-win32] Instructions for building and installing Python 2.7 on Windows with VS 2013 or newer

2015-02-20 Thread Reid Kleckner
Hi, I've successfully used the solution in the PCBuild directory to build CPython. However, now I have a binary and collection of .pyd files that aren't really a coherent installation. How do I do the equivalent of a "make install" step on Windows? My ultimate goal is to get a directory that looks

Re: [python-win32] Using pip to install pywin32

2015-02-20 Thread Thomas Heller
Am 20.02.2015 um 17:58 schrieb Preston Landers: Actually that gist wouldn't help much since it uses pywin32, the thing we're trying to install. (derp!) There may be another way though. Sure, you could port the gist to ctypes instead of pywin32. However, the problem is that pip doesn't run post

Re: [python-win32] extension modules and msvc version

2015-02-20 Thread Thomas Heller
Am 20.02.2015 um 17:41 schrieb Zachary Turner: Does anyone understand the technical reasons why an extension module must be compiled with the same version of msvc as python itself? Are there any workarounds? It's really quite an inconvenience. If the reason is because python27.dll and the extens

Re: [python-win32] extension modules and msvc version

2015-02-20 Thread Chris Angelico
On Sat, Feb 21, 2015 at 4:18 AM, Zachary Turner wrote: > Is it completely out of the question to change the way extension modules and > python talk to each other? > > I don't know anything about Python implementation internals, but is > something like this possible? I've no idea, my previous post

Re: [python-win32] Using pip to install pywin32

2015-02-20 Thread Kevin Horn
On Fri, Feb 20, 2015 at 8:07 AM, Vernon D. Cole wrote: > Pywin32 is mostly written in C, and has lots of dependencies and weird > build requirements. In order to compile it, you must have the same C > compiler that your release of Python was built with. For older Python > versions (like 2.7) tha

Re: [python-win32] extension modules and msvc version

2015-02-20 Thread Chris Angelico
On Sat, Feb 21, 2015 at 3:41 AM, Zachary Turner wrote: > Is the situation better in python 3 than it is in 2.7? And is anyone aware > of any ways to get around this restriction so that i can write an extension > module that will work with a binary release of python? It's going to be better, start

Re: [python-win32] Using pip to install pywin32

2015-02-20 Thread Preston Landers
Actually that gist wouldn't help much since it uses pywin32, the thing we're trying to install. (derp!) There may be another way though. Possibly related: http://bugs.python.org/issue20641 On Fri, Feb 20, 2015 at 10:31 AM, Preston Landers wrote: > > I don't think pip can run this script (it

Re: [python-win32] Using pip to install pywin32

2015-02-20 Thread Preston Landers
> I don't think pip can run this script (it even needs admin privs!). Is there a reason it couldn't run a script that presents a UAC prompt to elevate the process? Something like this: https://gist.github.com/Preston-Landers/267391562bc96959eb41 I guess for unattended installs you could just el

Re: [python-win32] Using pip to install pywin32

2015-02-20 Thread Thomas Heller
Am 20.02.2015 um 15:07 schrieb Vernon D. Cole: Pywin32 is mostly written in C, and has lots of dependencies and weird build requirements. In order to compile it, you must have the same C compiler that your release of Python was built with. For older Python versions (like 2.7) that compiler is ob

Re: [python-win32] Using pip to install pywin32

2015-02-20 Thread Vernon D. Cole
Pywin32 is mostly written in C, and has lots of dependencies and weird build requirements. In order to compile it, you must have the same C compiler that your release of Python was built with. For older Python versions (like 2.7) that compiler is obsolete and hard to find, so installs from source