On Wednesday 02 June 2004 09:33, Kevin Schmidt wrote:
> Hmm.. so in an effort to check to ensure things were thread safe, I've
> put in a bunch of thread blocking stuff. Around all code that calls to
> python, I call Py_BLOCK_THREADS and Py_UNBLOCK_THREADS. The problem
> this yields is that when
Hmm.. so in an effort to check to ensure things were thread safe, I've
put in a bunch of thread blocking stuff. Around all code that calls to
python, I call Py_BLOCK_THREADS and Py_UNBLOCK_THREADS. The problem
this yields is that when it hits the PyQt stuff, it hangs, trying to get
the GIL.
Jim Bublitz wrote:
On Wednesday 02 June 2004 08:17, Rex Dieter wrote:
Rex Dieter wrote:
Additionally, you may try this:
for i in $(find sip -name \*-kde322.diff); do
cp $i $(echo $i | sed "s|kde322|kde323|g")
done
cp -a extra/kde322 extra/kde323
thanks, that appears to have done the trick
Spoke
On Wednesday 02 June 2004 08:17, Rex Dieter wrote:
> Rex Dieter wrote:
> >> Additionally, you may try this:
> >> for i in $(find sip -name \*-kde322.diff); do
> >> cp $i $(echo $i | sed "s|kde322|kde323|g")
> >> done
> >> cp -a extra/kde322 extra/kde323
> >
> > thanks, that appears to have done
Rex Dieter wrote:
Rex Dieter wrote:
Additionally, you may try this:
for i in $(find sip -name \*-kde322.diff); do
cp $i $(echo $i | sed "s|kde322|kde323|g")
done
cp -a extra/kde322 extra/kde323
thanks, that appears to have done the trick
Spoke too soon... build fails later now. (kdelibs-3.2.
Rex Dieter wrote:
Additionally, you may try this:
for i in $(find sip -name \*-kde322.diff); do
cp $i $(echo $i | sed "s|kde322|kde323|g")
done
cp -a extra/kde322 extra/kde323
thanks, that appears to have done the trick
Spoke too soon... build fails later now. (kdelibs-3.2.3, rh90, gcc-3.2.2)
Hans-Peter Jansen wrote:
On Wednesday 02 June 2004 05:40, Rex Dieter wrote:
With these changes, build still fails, but differently:
...
KDE base directory is /usr
KDE include directory is /usr/include/kde
KDE lib directory is /usr/lib
KDE version is 3.2.3 (0x30203)
PyKDE modules to be built:
dco
On Wed Jun 2 15:28:00 2004, Kevin Schmidt [EMAIL PROTECTED] wrote:
> However, if I try:
>
> from qt import *
> q=QObject()
> p=QObject(p)
> print p.parent()
>
> It crashes when I try to compile (via Py_CompileString(c_line, "",
> Py_single_input)) the "print p.parent()" line.
I would have thou
On Wednesday 02 June 2004 05:40, Rex Dieter wrote:
>
> With these changes, build still fails, but differently:
> ...
> KDE base directory is /usr
> KDE include directory is /usr/include/kde
> KDE lib directory is /usr/lib
> KDE version is 3.2.3 (0x30203)
>
> PyKDE modules to be built:
> dcop kd
Another small bit of information:
I can run the following code:
from qt import *
q=QObject()
print q.parent()
The result is None, of course. However, if I try:
from qt import *
q=QObject()
p=QObject(p)
print p.parent()
It crashes when I try to compile (via Py_CompileString(c_line, "",
Py_single_i
A few more details:
I have embedded python in a similar manner to how a few groups mention
to. I don't use the InteractiveLoop in a separate thread for various
reasons. Instead, I compile a bunch of code, and send it off in groups
of lines. This works as far as I can tell.
I link in python s
On Wednesday 02 June 2004 11:20 am, Sibylle Koczian wrote:
> Dear Mr. Lauer,
>
>
>
> Did you try reading "Python und GUI-Toolkits"? This one aims at giving
> you some background to how event driven programs work, what makes a
> GUI-Toolkit at all etc. It contains a presentation of a "full-fledged"
Dear Mr. Lauer,
Did you try reading "Python und GUI-Toolkits"? This one aims at giving
you some background to how event driven programs work, what makes a
GUI-Toolkit at all etc. It contains a presentation of a "full-fledged"
application which is layed out GUI-Toolkit independent in the core and
t
13 matches
Mail list logo
