Mail Archives: cygwin/2008/11/20/13:53:45
Tim Hoel wrote:
> But when I did "import sqlite3", I
> got the following error:
>
> ImportError: No module named _sqlite3
I thought this was fixed 2 months ago:
http://cygwin.com/ml/cygwin/2008-08/msg00156.html
Cygwin's Python currently links to SQLite statically, but from that
thread, this doesn't seem to be a problem.
If it turns out that you really do need a dynamic library to make
pysqlite happy, that's probably something the Cygwin Python maintainer,
Jason Tishler, needs to take care of. My SQLite packages for Cygwin
include both static and dynamic libraries, it's just that Cygwin's
Python doesn't know how to build against the dynamic ones yet.
It'd be best if Python and SQLite can remain separate, with Python
modules building against the standard SQLite package files. I'd hate to
see a separate distribution of SQLite included with Python. There's not
enough maintainer bandwidth to go around even without wasting it on
duplicate packaging like that.
> Using cygwin setup again, I installed sqlite3 src (3.6.2-1-src), and
> tried to build pysqlite. I did run into one build problem because this
> version of sqlite3 does not have an entry for
> sqlite3_enable_load_extension().
I'll see about enabling that in the next build of the SQLite packages.
It might not be possible, as it might use dlopen(), rather than
LoadLibrary().
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -