On Thursday 27 November 2008, Oleg Broytmann wrote: > On Thu, Nov 27, 2008 at 04:35:43PM +0100, Markus Gritsch wrote: > > currently the sqlite3 module is, if present, preferred over a > > manually installed pysqlite2 module. Therefore it is not possible to > > use a newer version of pysqlite than the one that ships with Python > > 2.5 and 2.6. Is this really the desired behavior? > > No, and a request to fix this is already in my TODO. > > > The attached patch reverses the order in which the importing of the > > respective SQLite modules is performed. > > Thank you very much! > > I think, though, that such a change should be applied to the trunk, > not to the bugfix-only branches.
I think that such a change should not be applied at all. This change will make some users happy, but will alienate others, who what to use the old default while they may have both installed for reasons of their own. There shouldn't be a hardcoded choice of one version over the other if everybody is to be happy (the assumption that all people having both sqlite3 from python2.5+ and pysqlite2 installed prefer pysqlite2 doesn't hold water; same for the other way around) A better solution would be to somehow (maybe using a module parameter) indicate which is preferred (having a default that points to the most common/used one in case nothing is indicated by the user). Or maybe some parameter to the dburi (like backend) would be simpler and cleaner. -- Dan ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ sqlobject-discuss mailing list sqlobject-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
