PSARC/2008/117 - PySQLite

[Darren Kenny]

Hi Danek,

Hmm - this is my mistake - I happened to have both PySQLite 0.x/1.x and
PySQLite2 installed - and the name is meant to be pysqlite2, but saying that
most test programs import the module as sqlite - which is what confused me.

#!/usr/bin/python
import pysqlite2.dbapi2 as sqlite

print sqlite.apilevel


So it should have read

Exported Interface
---------------------------------------------------------------------------
         Interface Name		Stability	Comments
---------------------------------------------------------------------------
         pysqlite2              Uncommitted     Python module [PEP-2249]

Thanks for catching that!

Darren.

Danek Duvall wrote:
> Sorry for the late question, but ...
> 
> On Fri, Feb 15, 2008 at 10:17:18AM -0800, John Fischer wrote:
> 
>>         sqlite                      Uncommitted     Python module [PEP-2249]
> 
> I was browsing the Python 2.5 What's New document, and discovered that
> pysqlite is bundled with 2.5.  A little more reading, and I'm concerned
> about your proposed module name.
> 
> The history appears to be this:
> 
>   - pysqlite 0.x/1.x used the module name "sqlite".
> 
>   - pysqlite 2.x uses the module name "pysqlite2", where the "2" refers to
>     the major version of pysqlite.
> 
>   - It appears that pysqlite 3.x will use "pysqlite2" as well.
> 
>   - Python-bundled pysqlite uses the module name "sqlite3", where the "3"
>     refers to the SQLite version number.
> 
> I think that shipping pysqlite 2.x as "sqlite" is a bad idea -- it will
> confuse developers who have written Python code to recognize that as the
> 1.x API.  I'd recommend using "pysqlite2", as it appears that the
> difference between the Python-bundled name and the leaf-development name is
> at the request of the pysqlite author, and it makes sense to me to maintain
> that distinction.
> 
> Thanks,
> Danek