[Twisted-Python] [ANN] pglib 0.1
I'm pleasant to announce the first public release of pglib. pglib is an implementation of the PostgreSQL protocol, version 3.0. It is written in Twisted, and aims to be a complete replacement for libpq. In the current version the extended query sub protocol is not supported. The project can be found at: http://developer.berlios.de/projects/pglib/ Subversion access coming soon. Unfortunately, I still have to write some documentation/examples. However there is a (hopefully) detailed README and a complete test case. Its just the "twisted way" ;-). Note that running the test suite requires to setup a PostgreSQL database. And note that pglib offer (at least with the default IRowConsumer implementation) only a raw and low level access to the database (no conversion from SQL types and Python objects, like in pgasync). This is the responsibility of an higher lever layer. I would like to see pglib included in Twisted Core (in twisted.enterprise.protocols.twisted) I'm planning to write a support for MySQL (if I have time, it has a really ugly protocol design) and an asynchronous "wrapper" for SQLite. Regards Manlio Perillo
On Tue, 2006-05-23 at 14:58 -0200, Manlio Perillo wrote:
Manlio Perillo ha scritto:
[...]
I would like to see pglib included in Twisted Core (in twisted.enterprise.protocols.twisted)
Well, just to know. What is the procedure for require the inclusion of a new module/package?
1. Make sure you follow the Twisted coding standards, and have good test coverage. 2. Open issue in issue tracker, explaining motivation for not keeping this is as separate project.
Itamar Shtull-Trauring ha scritto:
On Tue, 2006-05-23 at 14:58 -0200, Manlio Perillo wrote:
Manlio Perillo ha scritto:
[...] I would like to see pglib included in Twisted Core (in twisted.enterprise.protocols.twisted)
Well, just to know. What is the procedure for require the inclusion of a new module/package?
1. Make sure you follow the Twisted coding standards, and have good test coverage.
In the current version, the docstrings do not use the format of epydocs/pydoctor. The test coverage should be good, but it requires an "external" PostgreSQL database. Is this a problem?
2. Open issue in issue tracker, explaining motivation for not keeping this is as separate project.
Ok, thanks. I will open an issue when I clean up the code. However I would like to see pglib in Twisted because: 1) I don't like that adbapi have to use dbapi2 compiant modules 2) I don't have the time to fully support pglib Thanks and regards Manlio Perillo
On 5/23/06, Manlio Perillo <manlio_perillo@libero.it> wrote:
However I would like to see pglib in Twisted because: 1) I don't like that adbapi have to use dbapi2 compiant modules 2) I don't have the time to fully support pglib
#2 is a point *against* inclusion of pglib in Twisted, as far as the Twisted project is concerned. We already have way too much unmaintained code whose only users are the author and (sometimes) a few third parties who don't contribute enough. -- Christopher Armstrong International Man of Twistery http://radix.twistedmatrix.com/ http://twistedmatrix.com/ http://canonical.com/
Christopher Armstrong ha scritto:
On 5/23/06, Manlio Perillo <manlio_perillo@libero.it> wrote:
However I would like to see pglib in Twisted because: 1) I don't like that adbapi have to use dbapi2 compiant modules 2) I don't have the time to fully support pglib
#2 is a point *against* inclusion of pglib in Twisted, as far as the Twisted project is concerned. We already have way too much unmaintained code whose only users are the author and (sometimes) a few third parties who don't contribute enough.
Support the *code* is not a problem. The problem is support a bug tracker, mailing list, and all stuff for user contributions. Regards Manlio Perillo
participants (3)
-
Christopher Armstrong
-
Itamar Shtull-Trauring
-
Manlio Perillo