| Subject | Re: [firebird-python] What is the current status of kinterbasdb? |
|---|---|
| Author | Helen Borrie |
| Post date | 2008-03-16T13:12:14Z |
Hello again Uwe,
At 11:37 PM 16/03/2008, Uwe Grauer wrote:
The Firebird Project needs Python too, as all of our QA tests and the QMtest system itself are written in Python. For this reason, Pavel Cisar is in the process of setting up an official Firebird sub-project for developing a new, fully implemented native Python driver for Firebird (but not InterBase). Help will be needed.
No doubt Pavel will catch up with this thread next week but I'll add a little more information. Pavel has devoted a lot of thought and energy in the past week or two preparing an application for the Google Summer of Code. By this means, if we are successful, we hope to attract some students to help with the new implementation. It looks like a good opportunity to get some enthusiastic new talent into this project.
We are all overstressed for time (another of Pavel's roles is as chairman of the Technical Task Group that's currently discussing the feature sets for this year's Firebird releases), but you can expect the Python driver area to get its own subweb under Development on the main website soon, when Pavel has sorted out some parameters. Have a little patience, though, as Pavel is our QA director and we're doing releases for 3 versions of Firebird currently.
The possibility of some grant funding from the Foundation shouldn't be overlooked either, if the new project throws up some good talent that has signs of staying aboard.
That's all I know so far, but Pavel shouldn't be far away. :-) I suggest in the meantime anyone at all interested should at least wave your hats and whistle a tune so we know you're here.
Helen
At 11:37 PM 16/03/2008, Uwe Grauer wrote:
>There were no news on kinterbasdb for a long time now.First, for the benefit of others, I'll repeat the answer I gave you on firebird-support. As you may or may not be aware, the lead developer of kinterbasedb (David Rushby) was killed last summer in a boating accident. Nobody has taken over from him.
>Can someone please give some information on the current status?
>Did someone take over kinterbasdb development?
>
>Since kinterbasdb isn't ready for firebird 2.1 and i have to use a
>testrelease of kinterbasbd 3.2 to be able to use it with Dabo
>(http://www.dabodev.com) i really would like to have some infos on the
>future of kinterbasdb support.
>
>I hope someone is reading this mailing list as there was almost no
>activity during the last year.
The Firebird Project needs Python too, as all of our QA tests and the QMtest system itself are written in Python. For this reason, Pavel Cisar is in the process of setting up an official Firebird sub-project for developing a new, fully implemented native Python driver for Firebird (but not InterBase). Help will be needed.
No doubt Pavel will catch up with this thread next week but I'll add a little more information. Pavel has devoted a lot of thought and energy in the past week or two preparing an application for the Google Summer of Code. By this means, if we are successful, we hope to attract some students to help with the new implementation. It looks like a good opportunity to get some enthusiastic new talent into this project.
We are all overstressed for time (another of Pavel's roles is as chairman of the Technical Task Group that's currently discussing the feature sets for this year's Firebird releases), but you can expect the Python driver area to get its own subweb under Development on the main website soon, when Pavel has sorted out some parameters. Have a little patience, though, as Pavel is our QA director and we're doing releases for 3 versions of Firebird currently.
The possibility of some grant funding from the Foundation shouldn't be overlooked either, if the new project throws up some good talent that has signs of staying aboard.
That's all I know so far, but Pavel shouldn't be far away. :-) I suggest in the meantime anyone at all interested should at least wave your hats and whistle a tune so we know you're here.
Helen