Phil Thompson [EMAIL PROTECTED] wrote:
Except that this is not totally equivalent:
- In the C++ version, dlg is a local variable: so it gets deleted
when we get out of function().
- In the Python version, dlg is owned by self: when we get out of
function(), it is still referenced and won't
Le Lundi 27 Février 2006 11:20, Phil Thompson a écrit :
You don't say what versions you are using. I think this was fixed in v3.15
- at least I don't see any leak in current snapshots.
Oups, my bad. I'm using 3.13. Good to know it has been fixed.
--
Aurélien Gâteau - [EMAIL PROTECTED]
So I have been playing with Qprocess and have again run into a problem.
I have:
from qt import *
## snipped away most of the code ##
upgradeProcess = QProcess(apt-get)
upgradeProcess = addArgument(upgrade)
upgradeProcess.start()
while upgradeProcess.canReadLineStdout():
Hi *,
Danny Pansters wrote:
[...] well I've seen quite a few people
lately asking for working real-life examples of pyqt/pykde [...]
and http://www.kde-files.org/content/show.php?content=35251 is another one
written in just 3-4 days (with pure C++ Qt I am pretty sure at least double
of the
Phil Thompson wrote:
upgradeProcess = addArgument(upgrade)
...has the effect of rebinding the name upgradeProcess to the object
returned by the (non-existant) function addArgument(). The object previously
bound to upgradeProcess is garbage collected (assuming it has no other
names bound
Hi.
Are there any plans for supporting kde ioslaves in eric?
I do a lot of server side development in python and has become really fond the
way xemacs/tramp and kate/fish works to enable remote editing from local
editor sessions.
Of course, I would like eric to understand where the file is
Am Dienstag, 28. Februar 2006 13:23 schrieb Roy Dragseth:
Hi.
Are there any plans for supporting kde ioslaves in eric?
I do a lot of server side development in python and has become really fond
the way xemacs/tramp and kate/fish works to enable remote editing from
local editor sessions.
Hi,
What is the procedure to propose modification to sip ? I need a feature
that I am ready to program. I would like sip to have an option to
generate a C++ file only if it does not exists or if it is different
from the existing one. This would greatly improve compilation time
(using make
I would like sip to have an option to generate a C++
file only if it does not exists or if it is different from the existing one.
This would greatly improve compilation time ...
That would be very good indeed. Does it need to be
optional?
We would see some immediate benefits to
On Tuesday 28 February 2006 3:10 pm, Yann Cointepas wrote:
Hi,
What is the procedure to propose modification to sip ?
You've just followed it. :)
I need a feature
that I am ready to program. I would like sip to have an option to generate
a C++ file only if it does not exists or if it is
I wouldn't accept this change as it doesn't really have anything to do with
what SIP does (although I readily admit that some of SIP's existing
functionality also falls into that category).
Phil,
It could be argued that SIP is part of a broader toolchain (in our case,
gmake and qmake) that
Nigel Stewart [EMAIL PROTECTED] wrote:
I wouldn't accept this change as it doesn't really have anything to do
with
what SIP does (although I readily admit that some of SIP's existing
functionality also falls into that category).
Phil,
It could be argued that SIP is part of a broader
It could be argued that SIP is part of a broader toolchain
What does this have to do with SIP again? I don't remember GCC not
generating the object files if the source code is not changed.
A compiler takes one input file and creates one output file.
The granularity of SIP is
On Tuesday 28 February 2006 3:50 pm, Nigel Stewart wrote:
I wouldn't accept this change as it doesn't really have anything to do
with what SIP does (although I readily admit that some of SIP's existing
functionality also falls into that category).
Phil,
It could be argued that SIP is
Nigel Stewart [EMAIL PROTECTED] wrote:
What does this have to do with SIP again? I don't remember GCC not
generating the object files if the source code is not changed.
A compiler takes one input file and creates one output file.
Actually not really, since the input can also contain an
On Tue, 28 Feb 2006 10:18:31 -0600
Nigel Stewart [EMAIL PROTECTED] wrote:
It could be argued that SIP is part of a broader toolchain
What does this have to do with SIP again? I don't remember GCC not
generating the object files if the source code is not changed.
A compiler
uic and moc avoid touching files unnecessarily, and so could SIP.
I wasn't aware of uic and mock behaving like that.
True, it's qmake that is uic and moc dependency aware...
A wrapper that generated the .sip files into a temporary directory, compared
them against previously generated
On Monday 27 February 2006 16:44, Tom Brown wrote:
On Monday 27 February 2006 16:39, Andreas Pakulat wrote:
Are you using PyQt3 or PyQt4? And also a minimal compilable example is
very helpful when reproducing this.
I can't reproduce this with PyQt4 and a small example that fills the
On Tuesday 28 February 2006 4:30 pm, Giovanni Bajo wrote:
Nigel Stewart [EMAIL PROTECTED] wrote:
What does this have to do with SIP again? I don't remember GCC not
generating the object files if the source code is not changed.
A compiler takes one input file and creates one output
On Tuesday 28 February 2006 08:48, Tom Brown wrote:
On Monday 27 February 2006 16:44, Tom Brown wrote:
On Monday 27 February 2006 16:39, Andreas Pakulat wrote:
Are you using PyQt3 or PyQt4? And also a minimal compilable example is
very helpful when reproducing this.
I can't
Phil Thompson [EMAIL PROTECTED] wrote:
With one source file (plus lots of header files) the whole of PyQt4 takes
2
minutes 50 seconds on my 2GHz Opteron. Microsoft compilers struggle with
such large source files.
My experience is that GCC cannot handle PyQt3 single-file version and takes
like
A wrapper that generated the .sip files into a temporary directory, compared
them against previously generated files and replaced them if they were
different isn't very difficult to write.
Phil,
Experimenting here with diff and patch...
diff -ruN out tmp | patch -d out
However, there is one
On 28.02.06 08:48:04, Tom Brown wrote:
On Monday 27 February 2006 16:44, Tom Brown wrote:
On Monday 27 February 2006 16:39, Andreas Pakulat wrote:
Are you using PyQt3 or PyQt4? And also a minimal compilable example is
very helpful when reproducing this.
I can't reproduce this with
On Tuesday 28 February 2006 5:25 pm, Nigel Stewart wrote:
A wrapper that generated the .sip files into a temporary directory,
compared them against previously generated files and replaced them if
they were different isn't very difficult to write.
Phil,
Experimenting here with diff and
On Tuesday 28 February 2006 5:18 pm, Giovanni Bajo wrote:
Phil Thompson [EMAIL PROTECTED] wrote:
With one source file (plus lots of header files) the whole of PyQt4 takes
2
minutes 50 seconds on my 2GHz Opteron. Microsoft compilers struggle with
such large source files.
My experience
On 28.02.06 18:18:42, Giovanni Bajo wrote:
Phil Thompson [EMAIL PROTECTED] wrote:
With one source file (plus lots of header files) the whole of PyQt4 takes
2
minutes 50 seconds on my 2GHz Opteron. Microsoft compilers struggle with
such large source files.
My experience is that GCC
On Tuesday 28 February 2006 09:18, Giovanni Bajo wrote:
Phil Thompson [EMAIL PROTECTED] wrote:
With one source file (plus lots of header files) the whole of PyQt4 takes
2 minutes 50 seconds on my 2GHz Opteron. Microsoft compilers struggle with
such large source files.
My experience is that
27 matches
Mail list logo
