Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #77718 > unrolled thread

Re: weakref, memory management and execution slow down in PyQt4

Started byMark Lawrence <breamoreboy@yahoo.co.uk>
First post2014-09-09 08:43 +0100
Last post2014-09-09 08:43 +0100
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: weakref, memory management and execution slow down in PyQt4 Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-09-09 08:43 +0100

#77718 — Re: weakref, memory management and execution slow down in PyQt4

FromMark Lawrence <breamoreboy@yahoo.co.uk>
Date2014-09-09 08:43 +0100
SubjectRe: weakref, memory management and execution slow down in PyQt4
Message-ID<mailman.13891.1410249864.18130.python-list@python.org>
On 09/09/2014 03:45, kjs wrote:
>
> You're right, a dictionary can do everything I need and more. This
> happened to be the first thing I thought of, and I didn't imagine it
> would be very expensive. I figured it was simply a different way of
> defining and retrieving a class variable. IE setattr(self, foo, True) ==
> self.foo = True.
>

My rule of thumb for making a judgement on Python performance is never 
assume anything, ever.  In using Python for well over 10 years my gut 
instinct has never been correct on this matter.  The only thing to do is 
profile your code and then seek the answers online, as you can guarantee 
someone else has already been there, seen it, done it and got the t-shirt :)

-- 
My fellow Pythonistas, ask not what our language can do for you, ask
what you can do for our language.

Mark Lawrence

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web