Thanks On Thu, Apr 26, 2012 at 3:57 PM, Steven Caron <car...@gmail.com> wrote:
> there was a 'memory leak'. i logged an issue about this mentioning they > should have provided a way to avoid the leak but maintain compatibility > with client code. i suggest you do the same so it will get some more > attention. > > i wouldn't change siutils.py but instead put a try catch in your code > until its resolved. > > s > > > On Thu, Apr 26, 2012 at 12:53 PM, Hans Payer <hanspa...@gmail.com> wrote: > >> Hello, >> >> The si shortcut in siutils return a method object in 2013 instead of the >> XSI.application object in 2012. So to get the same result as in 2012 you >> have to add parentheses() when calling si in 2013 in order my old plugins >> to work. Seems like no big deal, I will change siutils.py so it behaves as >> in 2012. But why change it? Is there a good reason? It's a bit annoying. >> Now I'm afraid others will start writing code with si() and I'll have to >> find a clever way to support both at the same time. >> >> Thanks >> >> Hans >> > >
