Take advantage of python features (itertools, generators), write 'portable'/standard code and reduce overhead seem good reasons to me :-) BTW, the list thing saves/converts a snapshot of the collection (frozen their members), it comes handy when working with the selection or unwanted mutable collections.
Cheers! On Thu, Nov 7, 2013 at 6:27 PM, Eric Thivierge <[email protected]>wrote: > Converting from an iterable object to another while losing capabilities > (collections have some handy functions, can be added to other collections, > etc) doesn't seem too helpful other than getting something that will print > something other than "None". In which case since you know .Bones is a > property of the chain root you can just print the .Count of the collection > to see if it is empty. > > Any benefits to converting to a list? > > Eric T. > >
