On 9/20/06, John DeRosa <[EMAIL PROTECTED]> wrote: [snip] > > It seems a little screwy for a file in a directory called "sqlite3" to > do an import from "pysqlite2". But that's what it does. >
What you need to realize is that "sqlite" refers to the database, while "pysqlite" are the python bindings to that database. SQLite is currently up to version 3.x. The python bindings required to use SQLite3 are up to version 2.x - thus "pysqlite2". It would seem that in Python2.5 they tried to avoid this confusion by naming the python bindings the same as the version of SQLite they are a wrapper for. While this certainly makes sense, it is not backward compatable as any existing projects would be importing from pysqlite2 as you found out. It looks this this is being addressed in ticket 2772 [1]. For more info on the new sqlite3 wrapper, see [2]. [1]: http://code.djangoproject.com/ticket/2772 [2]: http://docs.python.org/dev/whatsnew/modules.html#SECTION0001440000000000000000 -- ---- Waylan Limberg [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
