Scusami, Enrico, hai ragione.<br>Cercherņ di spiegarmi meglio dicendo cosa voglio ottenere.<br>Scrivo dei programmi in wx.Python basati su una frame principale e su numerose frame secondarie destinate a operazioni usate raramente.<br>
Se la memoria usata da queste finestre secondarie NON viene restituita all'OS alla distruzione dell'oggetto, ma č trattenuta a disposizione del programma, tanto vale nascondere e mostrare le frame senza ripetere ogni volta il lavoro di inizializzazione.<br>
<br><div><span class="gmail_quote">2008/4/11, enrico franchi <<a href="mailto:enrico.franchi@gmail.com">enrico.franchi@gmail.com</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Fri, Apr 11, 2008 at 4:38 PM, raffaello <<a href="mailto:barbarossa.platz@gmail.com">barbarossa.platz@gmail.com</a>> wrote:<br> <br> > Is it true that when an object is destroyed in a Python application<br> > the garbage collector does NOT give back the occupied memory to the<br>
> Operating System as long as the application is running, but keeps it at the<br> > disposal of the same application?<br> <br> <br>1. Since this is an italian mailing list, Italian or Python should be<br> preferred (writing prose in Python is quite hard, though).<br>
2. It is not true that the behaviour you described is part of<br> *Python*. However, as far as I know this was (and may be as well) the<br> behaviour of the interpreter. This is a reasonable behaviour.<br> <br><br> <br> --<br>
-enrico<br> _______________________________________________<br> Python mailing list<br> <a href="mailto:Python@lists.python.it">Python@lists.python.it</a><br> <a href="http://lists.python.it/mailman/listinfo/python">http://lists.python.it/mailman/listinfo/python</a><br>
</blockquote></div><br>