Re: [python-win32] Pywin32 without the interface
On 11/30/22 8:16 AM, QMUL_EECS DVS wrote: I hope you are well. I’m trying to use pywin32 on my local server, is it possible to run it without the Visio/ Word interface open? Since I can only see the command line The question doesn't make much sense. Are you saying that you want to automate Visio and Word through pythoncom, but you don't want the application window to be visible? That can be done. Please clarify. -- Tim Roberts, t...@probo.com Providenza & Boekelheide, Inc. ___ python-win32 mailing list python-win32@python.org https://mail.python.org/mailman/listinfo/python-win32
[python-win32] Pywin32 without the interface
Hi all, I hope you are well. I’m trying to use pywin32 on my local server, is it possible to run it without the Visio/ Word interface open? Since I can only see the command line Thanks Best regards ___ python-win32 mailing list python-win32@python.org https://mail.python.org/mailman/listinfo/python-win32
Re: [python-win32] Memory access violation using pywin32 as WSH
We have a glimmer of hope. Just got a fresh build of xmetal.exe from the vendor, and it's not failing in my initial tests. Much more testing to do, but this looks very promising. I've asked them to tell me about the fix, but they've dodged that question so far. So let me stop here and tell you how grateful I am for your patient assistance. And (of course) for creating this package in the first place. Many thanks, Bob ___ python-win32 mailing list python-win32@python.org https://mail.python.org/mailman/listinfo/python-win32
Re: [python-win32] Memory access violation using pywin32 as WSH
On Tue, Nov 29, 2022 at 6:19 PM Mark Hammond wrote: > > On 30/11/2022 3:06 am, Bob Kline wrote: > >> As a side note, imp.new_module() [3] was deprecated back in Python 3.4. > > Yep, you are looking at a very old version. True, but I checked HEAD for the main branch, and the code [1] is still calling the deprecated method. Cheers, Bob [1] https://github.com/mhammond/pywin32/blob/main/com/win32comext/axscript/client/pyscript.py#L217 ___ python-win32 mailing list python-win32@python.org https://mail.python.org/mailman/listinfo/python-win32
Re: [python-win32] Memory access violation using pywin32 as WSH
On Tue, Nov 29, 2022 at 6:23 PM Mark Hammond wrote: > The close method is Microsoft is not helping much here. The documentation to which you linked has no information about this method other than that it returns a 32-bit integer for which no semantics are given, and that it lives in the Microsoft.VisualStudio.Debugger.Interop namespace. I'm having a little difficulty figuring out how that namespace would be appropriate for their general scripting language interface. > It's worth pointing out that any "obvious" bug in pywin32 > here would probably be able to be reproduced in, and > reported by, the various other hosts, including cscript.exe > and wscript.exe (which themselves are just active script > hosts, just like your problematic host) I had that thought, too. But then I realized that cscript.exe and wscript.exe use a model of a separate process for each invocation of a single script. That script can be very complicated, but it's loaded, parsed, and executed once. I can run a pretty complicated Python macro once per XMetaL session (by which I mean separate process) without any problem. If I want to run a script twice using cscript.exe I have to launch two separate cscript.exe processes. It occurred to me that a better comparison might be using Internet Explorer, which can presumably run multiple scripts multiple times in a single process. So I grabbed form.htm from axscript/Demos/client/ie (I promise I'm looking at the correct repository now ), thinking I'd see if clicking the Submit button multiple times caused any problems. Unfortunately, the scripts didn't fire at all, and the browser's console window didn't provide any explanation as to why. (By the way, I had to fix the third INPUT element, which was malformed, as its tag was missing its right angle bracket delimiter. IE may have been tolerant of that broken syntax at some time in the past, but it doesn't accept it now.) Cheers, Bob ___ python-win32 mailing list python-win32@python.org https://mail.python.org/mailman/listinfo/python-win32
Re: [python-win32] Memory access violation using pywin32 as WSH
On Tue, Nov 29, 2022 at 6:19 PM Mark Hammond wrote: > ... the ax object isn't going to have a Reset - so whatever that's trying to > do isn't getting done. How would we go about finding out what that missing method was supposed to do, so that we can know whether the failure to do it is related to the problem? One of the frustrations here is that while the documentation for the host application says "You can use any scripting language that conforms to the Microsoft Scripting Language Interface" trying to find the specification for that interface on Microsoft's web site turns up nothing. Has Microsoft published the spec and then gone to the trouble of extirpating every trace of it? Do you have a copy? > ... Yep, you are looking at a very old version. Sorry for the old link. Don't have any idea how I ended up in that repository. Obviously the copy I was hacking to get my debug logging was the real thing, installed by pip. I'm suitably embarrassed that I didn't notice that they didn't match. > ... when I say I'm hoping to see a stack trace, I mean a native stack trace I'll see what I can do to produce one. Thanks, Bob ___ python-win32 mailing list python-win32@python.org https://mail.python.org/mailman/listinfo/python-win32
