Pysqlite bindings on RHE5

[ladhami@…]

Hello, There does not seem to be a way to get TRAC and python to agree on using the same sqlite version. This is a brand new RHE5 machine, with only subversion upgraded on it. TRAC creates everything using sqlite3, while the python bindings will always use pysqlite1.x with TRAC, even after pysqlite2 is installed. (I confirmed all this following the troubleshouting instructions to give the exact version: sqlite3.3.6, sqlite.version-1.1.7, sqlite._sqlite.sqlite_version()=3.3.6, and for the backend test.sqlite.version=2.2.3).

Should there not be a way of forcing either TRAC of the bindings (not sure if this is mod_python or what) to sync on the same version of pysqlite?

Thanks

[anonymous]

Replying to ladhami@…:

There does not seem to be a way to get TRAC and python to agree on using the same sqlite version.

Trac only uses pysqlite module to access the SQLite database, so it cannot be otherwise. However, several versions of pysqlite may be installed on the same machine.
Trac does not use sqlite nor sqlite3 command line tool.

This is a brand new RHE5 machine, with only subversion upgraded on it.

RedHat is/has been known to provide a version of the sqlite command line tool which is not compatible with the provided pysqlite Python module ;-)
You may want to search the Trac DB or the MailingList archive to find the relevant thread.

TRAC creates everything using sqlite3,

Not actually true. Trac creates everything using pysqlite bindings. It should be pysqlite2 with a recent version of Trac, that is using a SQLite DB format which is compatible with sqlite3 but not with sqlite command line tool.

while the python bindings will always use pysqlite1.x with TRAC, even after pysqlite2 is installed.

It depends on how/where the modules are installed, and the current PYTHONPATH variable, among others settings. Maybe the default Trac package that comes with Red Hat is buggy, though?

This is an InstallationIssue. You may want to post to the MailingList to find help with Red Hat