Re: [python-sybase] Re: This routine cannot be called because another command structure has results pending

[Greg W. <gwa...@py...>]

On 05 July 2006, I said:
> However, I suspect a more appropriate fix would be to factor out a
> _close_fetcher() method of Cursor:
>
>   def _close_fetcher(self):
>       if self._fetcher:
>           self._fetcher._close()
>       self._fetcher = None
>
> and replace every occurence of "self._fetcher = None" with
> "self._close_fetcher()".

I have done this and it seems to work.  I'm certainly not getting any
more mysterious "this routine cannot be called" errors from my
Python/sybase scripts, which makes me very happy indeed.

I'll attach my patch.  Does this look correct?  Is it likely to be
included in a future release of python-sybase?  Do you think I'll get
burned if I deploy a version of python-sybase with this patch applied?

        Greg