Re: [python-win32] win32com.server failure: Is debugging possible?

Have you tried using PTVS and attaching to process with the Python debug engine enabled? Then you can set a breakpoint in managed code and look for calls to sys.exit On Sat, Aug 27, 2016 at 7:23 AM Bob Hood wrote: > On 8/25/2016 9:36 PM, eryk sun wrote: > > On Fri, Aug 26,

Re: [python-win32] Python in Visual Studio

The debugger is good too. I don't know of any other tool that lets you seamlessly step between Python and native code when debugging a program which embeds Python On Sat, Apr 16, 2016 at 5:23 PM Alexander Walters wrote: > As a total aside, PTVS (part of the base VS 2015

Re: [python-win32] Figuring out why a window is losing focus

It's included as part of Visual Studio. Download community edition, it should be there. On Mon, Feb 8, 2016 at 7:33 PM reckoner wrote: > > Where can I safely download this Spy program you are all talking about? > > Thanks! > > > > On 2/8/2016 9:00 AM,

Re: [python-win32] Building my own C extension

Two questions: 1) Are you embedding this extension in your own application or do you only need to be able to load it into a stock Python distribution? 2) Is Python 3.5 out of the question? On Wed, Nov 4, 2015 at 5:10 PM Ken Brooks wrote: > I have joined this list because I

Re: [python-win32] Windows 10

It's not that "many programmers still refer to Windows API as Win32", it's that the Windows API itself has decided that that is what it is called. When you #define _WIN32 in a C or C++ program using the Windows API, it does not mean "this is a 32-bit app", it means "I'm using the Windows API".