>
> On Wed, Nov 4, 2009 at 5:29 PM, Pierre Raybaut wrote:
>
>> > A simpler fix would be:
>> >
>> > ? ? ? ?class FigureWindow(QtGui.QMainWindow):
>> > ? ? ? ? ? ?def __init__(self):
>> > ? ? ? ? ? ? ? ?super(FigureWindow, self).__init__()
>> >
>> > ? ? ? ? ? ?def closeEvent(self, event):
>> > ?
Hello,
The latest check-out gives an error while trying to build the documentation.
Hitting "q" in pdb prompt resumes the execution and finishes the creation
successfully.
[gse...@ccn doc]$ python make.py all
Running Sphinx v0.6.2
loading pickled environment... done
animation, api, axes_grid, ev
On Sat, Nov 7, 2009 at 9:53 AM, Pierre Raybaut wrote:
>>
>> On Wed, Nov 4, 2009 at 5:29 PM, Pierre Raybaut
>> wrote:
>>
>>>
>>> > A simpler fix would be:
>>> >
>>> > ? ? ? ?class FigureWindow(QtGui.QMainWindow):
>>> > ? ? ? ? ? ?def __init__(self):
>>> > ? ? ? ? ? ? ? ?super(FigureWindow, self)._
Hey all,
2009/2/10 Andrew Straw :
> Gary Ruben wrote:
>> Hi Andrew,
>>
>> I don't have commit access. If you would check it in, that would be great.
>
> Committed to the trunk in r6899... Thanks!
>
> And, sheesh, SourceForge's SVN server is slooow today for me, although
> it seems to have finally
Currently imsave (implemented in the image.py file) only deals with
greyscale single-plane images, i.e. 2D arrays, and in my defence, it's
in the docstring, so I wouldn't call it a bug. However, it's a
reasonable expectation that it support rgb and rgba since it is
basically a thin wrapper arou
Hi everybody,
I was looking at this bug about a memory leak:
https://sourceforge.net/tracker/?func=detail&atid=560720&aid=2889570&group_id=80706
While this bug is now essentially fixed, I noticed that the Figure class
contains some circular references that prevent it from being cleaned up by th
Michiel de Hoon wrote:
> Hi everybody,
>
> I was looking at this bug about a memory leak:
>
> https://sourceforge.net/tracker/?func=detail&atid=560720&aid=2889570&group_id=80706
>
> While this bug is now essentially fixed, I noticed that the Figure class
> contains some circular references that
I guess you're right... I misunderstood the result of gc.collect() as the
number of objects that could not be freed. The good news is that after fixing
the bug I was looking at, there are no more objects that cannot be freed
(gc.garbage is empty).
Thanks!
--Michiel.
--- On Sun, 11/8/09, Eric
