<br />>The pg8000 / bpgsql seem to be toy projects, and anyway you dont<br />>want to use pure-Python drivers in
high-performanceenvironments.<br /><br />I agree that there are some performance-challenges with pure-Python
drivers.<br/><br />And we should not forget to look for the reasons for the incubation of that many pure-Python
drivers:<br/><br />a) Python is no longer one-language, one-implementation. There are (at least) cPython (the
original),Jython (on JVM), IronPython (from Microsoft on CLR), PyPy (Python on Python), Unladen Swallow (from Google on
LLVM).In addition the nearly-Pythons as in Cython, RPython and ShedSkin<br /><br />Everything apart from cPython (and
possibleUnladenSwallow) has its challenges dealing with non-Python extension modules. From a developer standpoint it
canbe tempting to be able to rely on the same database adapter across more then one implementation<br /><br />b) the
stabilizationof an Python Application Binary Interface is in early discussion stage; meaning: it will take some time
untilla non-Python extension can be usable across Python versions. c-Extensions are allways a major stumbling block on
Python-nto Python-(n+1) versions<br /><br />c) Stability. Python code is same-on-same more robust then C-Code, as some
ofthe crash-friendly-problems are eliminated (you cannot allocate memory wrongly within Python, you cannot errorly
accessmemory cross array boundaries...)<br /><br />especially a) is a point to consider when standardizing on a
PostgreSQLblessed Python-Postgresql-driver. How will the blessing extend to Jython / Ironpython / PyPy?<br /><br
/>Harald<br/>-- <br />GHUM Harald Massa<br />persuadere et programmare<br /> Harald Armin Massa<br />Spielberger Straße
49<br/>70435 Stuttgart<br />0173/9409607<br />no fx, no carrier pigeon <br />-<br />%s is too gigantic of an industry
tobend to the whims of reality<br />
