When I said "as of now" I was referring to current snapshots.
Phil
On Thursday 16 October 2003 11:49 am, Patrick Stinson wrote:
> Is that the -r option on build.py? Doesn't that set the dir containing qt
> lib files?
>
> bash-2.05b$ python build.py --help
> ...
> -r dir the directory
Is that the -r option on build.py? Doesn't that set the dir containing qt lib
files?
bash-2.05b$ python build.py --help
...
-r dir the directory containing the Qt library [default
$QTDIR/lib]
...
bash-2.05b$
On Wednesday 15 October 2003 19:47, Phil Thompson wrote:
> On Thursday 16
On Thursday 16 October 2003 11:47, Phil Thompson wrote:
> # The SIP v4 module is called sip.
> import libsip as sip
>
> sip.settracemask(0xff)
>
> ...you can change the mask at any time. See the SIP_TRACE_* values in sip.h
> to see the detail of which trace messages correspond to which bit of the
>
On Thursday 16 October 2003 4:21 am, Derek Fountain wrote:
> When getting a segv from a PyQt script, is there a way of getting and using
> a core dump such that it might provide a clue as to what I've done wrong?
> What steps do developers take when faced with a segv?
Getting a core dump depends o
When getting a segv from a PyQt script, is there a way of getting and using a
core dump such that it might provide a clue as to what I've done wrong? What
steps do developers take when faced with a segv?
--
> eatapple
core dump
___
PyKDE mailing list
I'm running a self compiled PyQT-GPL-3.8 against Python-2.2.1 and Qt-3.1.1 on
a SuSE-8.1 box. I'm getting a SegV. The code is this:
---
from qt import *
class Model(QObject):
def __init__( self, *args ):
apply( QObject.__init__, (self,) + args )
self.currentImageList = []
