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

[Andrew M. <an...@ob...>]

>    Greg> Agreed.  In my experience, checking in patches is the least
>    Greg> time-consuming part of maintaining a stable project.  Merely
>    Greg> opening checkins to more developers won't help much.
>
>OTOH, if the Object Craft folks don't have Sybase available to test against,
>perhaps moving to SF would prompt someone with Sybase access to take over
>much of the vetting process.

If someone is offering to put pre-release code through it's paces,
we can do that without SF (yeah, it's a pretty clunky way of doing it,
but we all did somehow get by before the SF, and even IP connectivity 8-)

Obviously Greg's patch should go in - are there any other patches vs
0.37 that should be applied? I'll put together a devel snapshot for you
to download and test, and if all goes well, we'll call that 0.38.

In some ways, this situation is no worse than the linux kernel -
multiple repositories, patches being mailed around and being applied
without testing (since Andrew Morton and Linus can only ever have a
small subset of the hardware available). But if I can find time, I'll
have another go at installing Sybase.

-- 
Andrew McNamara, Senior Developer, Object Craft
http://www.object-craft.com.au/