Sorry, I don't know what specifically will force the clean up of those points.
Typically you shouldn't have to care and the garbage collector will do it's job
when the memory pressure is high enough.
> On Dec 21, 2015, at 4:18 PM, Djordje Spasic wrote:
>
> Thank you Steve.
> What about the po
Thank you Steve.
What about the points from which the mesh is made (a regular python lists with
Point3d objects in it).
Should I use the "del" statement to delete them, and then call gc.collect()
afterwards?:
import gcdel meshPts # meshPts is a python list containing Point3d objects
from which
In this case, the class that you are referring to is IDisposable. Call the
Dispose function on the Mesh instance when you are done with it.
-Steve
Steve Baer
Robert McNeel & Associates
www.rhino3d.com
On Sun, Dec 20, 2015 at 4:00 AM, Djordje Spasic via Ironpython-users <
ironpython-users@python.
I am a creating a huge mesh object (some 900 megabytes in size) in Rhino3d
application by using its ironpython 2.7 interpreter.Once I am done with
analysing this mesh, I would like to somehow delete it from the memory.
I did a bit of search on stackoverflow.com, and I found out that "del"
state
Hello,
when you create public ironpython apis for your applications written in C#,
would you prefer to create the API using c# with using the PythonModule
attribute,
or would you wrap every thing in IronPython written modules and call the in c#
written application core from there?
Currently I'm
