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

[<sab...@gm...>]

Hi Andrew,

2006/7/6, Andrew McNamara <an...@ob...>:
> ...
> As to whether it make it into a future release, I can certainly apply
> it to the repository, but neither Dave nor I have a Sybase installation
> to test it against at the moment (and neither of us can really spare
> the time).
>
> That raises the question - should the project be moved to Sourceforge? I'=
m
> not convinced the move would solve anything: it would still require at
> least one developer with C skills and the time to review and test patches=
,
> cut releases, and reply to queries - is there anyone on the list willing
> to commit to that?

I would like to volunteer to do that. We are using python-sybase in a
few tools at the company where I work and so we would like to
contribute to this project and ensure it is properly tested.

Actually I have already done most of the work:
* I merged most of the patches provided on this list
* I added some corrections of my own
* I added a unit test suite based on the DB API 2.0 driver compliance
unit test suite + extra
* this unit test suite has been added to our automated testing
framework so that it runs frequently on the following platforms and
sybase clients:
   i686-pc-linux-gnu - Sybase ASE 12.5.1 and 15.0 (32bits)
   sparc-sun-solaris2.10 - Sybase ASE 12.5.1 and 15.0 (32bits and 64bits)
   sparc-sun-solaris2.8 - Sybase ASE 12.5.1 and 15.0 (32bits)
   powerpc-ibm-aix5.3.0.0 - Sybase ASE 12.5.1 and 15.0 (32bits)
   powerpc-ibm-aix5.2.0.0 - Sybase ASE 12.5.1 and 15.0 (32bits)
   alphaev68-dec-osf5.1 - Sybase ASE 12.5.1 and 15.0 (32bits)

I join a patch which includes the modifications and the unit test
suite. If that is OK with you and Dave, I would be happy to help you
"review and test patches, cut releases, and reply to queries" for
coming versions of python-sybase.

regards

--
S=E9bastien Sabl=E9
SunGard GP3 - Runtime