Hi,
#!/usr/bin/python
# panels.py
import wx
class Panels(wx.Frame):
def __init__(self, parent, id, title):
wx.Frame.__init__(self, parent, id, title)
hbox = wx.BoxSizer(wx.HORIZONTAL)
splitter = wx.SplitterWindow(self, -1)
vbox1 = wx.BoxSizer(wx.VERTICA
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
kNish a écrit :
> Hi,
>
> #!/usr/bin/python
>
> # panels.py
>
> import wx
>
>
> class Panels(wx.Frame):
>def __init__(self, parent, id, title):
>wx.Frame.__init__(self, parent, id, title)
>
>hbox = wx.BoxSizer(wx.HORIZ
> [>>>Peck, Jon] Thanks for the pointer. It worked perfectly. But, in the
> spirit of self help, where could I have found DispatchEx documentation that
> would have explained this (other than the website above)?
One of those perennially unanswerable questions, I'm afraid. A lot
of the pywin32 st
Hi,
>
> Message: 1
> Date: Thu, 28 Feb 2008 14:34:12 +0530
> From: kNish <[EMAIL PROTECTED]>
> Subject: [python-win32] createtoolbar
> To: python-win32@python.org
> Message-ID:
> <[EMAIL PROTECTED]>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi,
>
> #!/usr/bin/python
>
Hi
I am wondering how could I delete an dispatched object? Do I just delete the
reference to that object? Does python garbage collector take care of
everything after I delete the reference? Is there any method which I could
use to delete a dispatched object?
--
CHEN HUANG
COMPUTER Engineering
Are there any known problems with the pywin32 installer when building
against Python 2.6? I am using the 32-bit build of Python 2.6.13936
installed using the pre-built daily snapshot installer. Everything
compiles fine, and running 'setup.py bdist_wininst' executes without
errors. However,
As soon as the last reference to the PyIDispatch object goes away, the COM
object is released. Unfortunately, neither Python nor COM offer a way to
actually destroy an object - they are both independently reference counted
so the only option available is to drop all references being held.
In P
Its likely that you snapshot of 2.5 is built with a different MSVC version
than pywin32 (python decided on VS2007 in the meantime). Its not
immediately obvious how that would cause the problem you see, but it may
well. Please let me know if
http://starship.python.net/crew/mhammond/pywin32-210.9.w
Oops - I should proof-read, especially before the first coffee is empty:
> Its likely that you snapshot of 2.5 is built with a different MSVC
I meant 2.6 there (and an extra 'r' :)
Mark
___
python-win32 mailing list
python-win32@python.org
http://mail
I am using Visual C++ 9.0 to build pywin32, and Dependency Walker
shows that the pyhon.exe from the 2.6 snapshot is linked against the
Visual C++ 9.0 runtime.
The installer that you provided crashes for me in the same way.
Perhaps it's a bug in Python or something wrong with my machine? Oth
> I am using Visual C++ 9.0 to build pywin32, and Dependency Walker shows
> that the pyhon.exe from the 2.6 snapshot is linked against the Visual
> C++ 9.0 runtime.
Ahh - sorry, I missed that you are building pywin32 yourself.
> The installer that you provided crashes for me in the same way.
> Pe
On Feb 28, 2008, at 5:54 PM, Mark Hammond wrote:
I am using Visual C++ 9.0 to build pywin32, and Dependency Walker
shows
that the pyhon.exe from the 2.6 snapshot is linked against the Visual
C++ 9.0 runtime.
Ahh - sorry, I missed that you are building pywin32 yourself.
The installer that y
12 matches
Mail list logo
