On 10/13/05, Vernon Cole <
[EMAIL PROTECTED]> wrote:
I am among those who have submitted patches. I get the idea (perhaps
unfounded) that the guys who made ADODBAPI now work for Micro$oft and
that their employer does not WANT them to maintain it. A pity, if so.
All I really know is that they have been silent for a very long time.
Sourceforge seems have a policy for other volunteers taking over an
inactive project. I think it would be better to try that than to make a
new effort. I am trying to contact the existing project administrator
by sending him a copy of this message. If there is continued silence, we
should try taking over this project, I would think.
Comments or volunteers, anyone?
---
Vernon Cole
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On
Behalf Of Erik Rose
Sent: Thursday, October 13, 2005 10:21 AM
To: [email protected]
Subject: [DB-SIG] Forking ADODBAPI
Aha, so I'm not the only one to consider forking ADODBAPI! :-) I,
too, submitted some fixes to the mailing list long ago and never got
a reply, and it's increasingly cumbersome to say "Requires ADODBAPI
v2.0.1 with this patch and that patch and...."
Has anyone forked it already? If I don't hear anything within a week,
I'm going to set up a Trac environment myself. I won't replace the
mailing list immediately, since Sourceforge's works fine and I don't
especially want to become a mail admin. I do look forward, though, to
rolling the accumulated patches into an up-to-date release and having
a central place to ticket what remains.
Any objectors?
Regards,
Erik Rose
P.S. In response to the long-ago bottom poster, I think there are
more preferable ways to talk to MS SQL from Python than through ADO:
FreeTDS, for instance, which is cross-platform and less flakey than
ADO. However, for applications like mine which absolutely need ADO-
driven access, ADODBAPI seems the most mature solution.
> I think a re-do may be going a little far, but the source is there,
> and
> it is easy to modify. A fork may be called for, and people to help
> maintain the fork would be needed.
>
> What issues have you had with MSSQL and adodbapi?
>
> ~Jon Franz
> NeuroKode Labs, LLC
>
> Chris Curvey wrote:
> > I think I had posted something several years ago and never heard
> > anything back. Since Python-to-MSSQL has been a pain in the neck
> for
> > years now, I'd be willing to help in an effort to re-do adodbapi.
> >
> > On 4/25/05, *Jonathan Franz* <jfranz at neurokode.com
> > <mailto: jfranz at neurokode.com>> wrote:
> >
> > Does anyone know how I can reach the maintainer of adodbapi? I
> > submitted a fix for a bug with transaction handling two weeks
> ago, and
> > heard nothing back.
> >
> > Looking closer at the project on SF, it looks like there
> are open bugs
> > dating back almost 2 years... is adodbapi now an orphaned
> project?
> >
> > ~Jon Franz
> > NeuroKode Labs, LLC
> > _______________________________________________
> > DB-SIG maillist - DB-SIG at python.org <mailto:DB-SIG at
> python.org>
> > http://mail.python.org/mailman/listinfo/db-sig
_______________________________________________
DB-SIG maillist - [email protected]
http://mail.python.org/mailman/listinfo/db-sig
_______________________________________________
DB-SIG maillist - [email protected]
http://mail.python.org/mailman/listinfo/db-sig
--
Nervous passengers are advised to wear a blindfold.
_______________________________________________ DB-SIG maillist - [email protected] http://mail.python.org/mailman/listinfo/db-sig
