Hi Roger, I agree with you that either
1) sqlite should not be required to run nose on your own projects 2) sqlite should be required, but eggs should be available and there should be install instructions for it Requiring sqlite to run the tests on the trunk is one thing, but it's something else entirely for TG projects. This issue did actually come up before, and we talked about just recommending use of sqlite. But, I'd prefer to see that configurable. By the way, in reference to the below: On 3/16/06, Roger Rohrbach <[EMAIL PROTECTED]> wrote: > > Hm. I installed SQLite 3.1.2 from a Fedora Core 4 source RPM, and > installed pysqlite 2.1.3. I still get "No module named sqlite"; it > seems like TurboGears doesn't know I've got the module. I think your problem can be identified here: http://initd.org/pub/software/pysqlite/doc/install-source.html pysqlite 2.1.x requires SQLite 3.2.2+. I think you'll find that pysqlite 2.0.x will work for you with that version of sqlite. (This is one reason that I'm ultimately inclined to get some statically linked eggs of pysqlite with sqlite together.) Kevin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears -~----------~----~----~----~------~----~------~--~---
