On Tue, Nov 25, 2008 at 12:48 AM, Malcolm Tredinnick <malc...@pointy-stick.com> wrote: >> > On Mon, 2008-11-17 at 16:19 -0800, Matthew D. Hancher wrote: >> > > Options include: >> > >> > > A. Leave sqlite3 as the default, and add a configuration setting that >> > > forces use of pysqlite2 if desired. >> > >> > > B. Always try both sqlite3 and pysqlite2, and use whichever has the >> > > greater version number if both are present. >> > >> > > C. Same as B, but with an optional configuration option to force one >> > > or the other if desired. >> > >> > > D. Switch to making pysqlite2 the default, since that's the correct >> > > name for the module if the user has explicitly installed it, and treat >> > > the Python-bundled version as the fallback. >> > > Still, it is a minor inconvenience, so I could still sleep at night if > we went with option A. The need to use the pysqlite2 version apparently > affects Windows users of Python 2.5.1 (maybe 2.5.2 also, I don't know), > since there was some version skew there that Ramiro Morales identified > as a problem
Actually, it was Python 2.5.2, it includes SQLite 3.3.4 (and sqlite3 module version is 2.3.2) and since then we've [1]learned that official win32 binary installers of Python 2.5.4 bundles the same combination. Regards, -- Ramiro Morales 1. http://groups.google.com/group/django-developers/msg/1368697b43ea27ea?hl=en --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
