On Feb 15, 2008, at 3:23 PM, Jonathon Anderson wrote:
> > I think I understand the relationship between pysqlite2 and sqlite3 > (the second being a stdlib snapshot of the first) and have found the > code in sqlalchemy that will use pysqlite2, if present, over sqlite3, > so having installed the latest version of pysqlite2, I should be fine. > > Any idea why the library name changed? I think that's confusing me > more than anything. > probably so you can have a separate pysqlite2 installed without conflicts over the built-in sqlite3. > I assume the stdlib sqlite module will be upgraded at Python 2.6? hopefully. apparently theres unit tests in python 2.5 which are hardwired against an older version of sqlite (fail with newer versions). --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
