On Sun, 14 Oct 2012 16:17:10 +0300, Patrick Vrijlandt
wrote:
I'm trying to install pywin32 build 217 for python 3.3 on my Vista machine.
...
The postinstall script shows a traceback:
...
File "C:\Python33\lib\imp.py", line 158, in load_module
raise ValueError(msg)
ValueError: file
From: Stefan George
I am using the PyWin32 package and I am wondering if there is any way to
get visibility information of a button (I only know the handle).
Is that possible and is there any code snippet, you could pass to me?
I am looking for something like isVisible(hwnd) returns True or Fa
I've made some modifications to PythonWin's Grep functionality. At first I
just wanted to add highlighting for the regex matches, but I guess I got
carried away. :b I'll eventually submit it to SourceForge, so that Mark may
include it in the official release if he wants. In the meantime, here's
From: "Antoine Martin"
Hah, that's easier than I thought!
Sure is. The hard part is terminating a bunch of processes as group (either
manually with PIDs or using job objects).
I had forgotten about the pipes (doh), I guess I should start the child
with stdin=stdout=stderr=None then?
Yes,
From: "Antoine Martin"
What is the best way to ensure that a child started with
subprocess.Popen does not get killed when its parent terminates on win32?
On Linux I can daemonize the child with fork()s and dup2()s
But what about windows?
You don't have to do anything. The lifetime of a child pr
Running Vista x64, PythonWin 2.6.1 x64, pywin32 214 x64.
win32api.FindWindow sometimes returns 0 instead of raising an exception. I
suppose that's a bug and will submit it if so. Can anyone verify? I tried
peeking into the code, but I have no clue about SWIG. :o)
Example code:
import win3
First, check if the file
("\Lib\site-packages\win32\win32file.pyd") really exists. Then
check the Python module search path. Put a "print sys.path" before the
"import win32file" and check whether it contains the
"...site-packages\win32" dir.
Either pywin32 didn't install properly or some modu
From: "Mark Hammond"
Thanks for the note - can someone with build 213 for Python 3.0 installed
check if they have the same problem or not (ie, if it is a regression or
just the first report of a problem existing for a few months)?
I just tried 213 for 3.0.1 and it works OK, so it looks like a
From: "Mark Hammond"
I'm happy to announce the release of pywin32 build 214.
Thanks, Mark.
Last night I wanted to try Python 3.1 and was wondering when PythonWin will
come out. Nice timing!
By the way, there's a bug (causing a triple exception) in the display of
syntax errors in the int
--- On Fri, 1/30/09, Mark Tolonen wrote:
> Two days ago I changed Control
> Panel, Regional and Language Options, Advanced tab,
> "Select a language to match the language version of the
> non-Unicode programs you want to use:" from
> "English (United States)" to "Chinese
> (PRC)" to work with Pyth
--- wowberk wrote:
> I need to list the advanced properties of a file such as
> organization, dll
> version, etc..
You can use win32api.GetFileVersionInfo.
___
python-win32 mailing list
python-win32@python.org
http://mail.python.org/mailman/list
Starting from pywin 211, typing non-ascii chars in any Scintilla control in
PythonWin is broken. These characters are truncated to the lower 8 bits of
their Unicode values. The changelog of Scintilla 1.75 (the version used in 211
and 212) mentions some Unicode enhancements, which might be the re
12 matches
Mail list logo
