Quick note to self, hopefully useful to others too:
If you compile Python 2.6 (or 2.5) from source, and you want to enable sqlite3 support (which is included in the stdlib for 2.5 and above), then you need to pass a special USE flag to the configuration command line, like this:
./configure USE="sqlite"
(note "sqlite" and not "sqlite3")
Subscribe to:
Post Comments (Atom)
Modifying EC2 security groups via AWS Lambda functions
One task that comes up again and again is adding, removing or updating source CIDR blocks in various security groups in an EC2 infrastructur...
-
This post is a continuation of my previous one on " Running Gatling tests in Docker containers via Jenkins ". As I continued to se...
-
For the last month or so I've been experimenting with Rancher as the orchestration layer for Docker-based deployments. I've been pr...
-
Here's a good interview question for a tester: how do you define performance/load/stress testing? Many times people use these terms inte...
3 comments:
Hm. That's strange. I've built Python 2.5 and 2.6 from source and I didn't do this either time, but I got the "sqlite3" module. I wonder what the difference is.
Same doubt here: I just compiled Python 2.6 in Centos 5 64 bits: only thing I needed -of course- was the dev files for sqlite.
It may be some peculiarity of my environment....I am compiling Python 2.6 from source on an Ubuntu 8.04 box, which has Python 2.5 as the default.
Post a Comment