On Tue, Nov 25, 2008 at 12:48 AM, Malcolm Tredinnick
wrote:
>> > On Mon, 2008-11-17 at 16:19 -0800, Matthew D. Hancher wrote:
>> > > Options include:
>> >
>> > > A. Leave sqlite3 as the default, and add a configuration setting that
>> > > forces use of pysqlite2 if desired.
>> >
>> > > B. Always
> Since so far only you and I have made real input here, I'd like to hear
> what any of the other maintainers (or anybody else who uses this stuff)
> thinks. Realistically, any of the options are survivable, so barring any
> great arguments one way or the other, we should just pick one and commit
On Mon, 2008-11-24 at 18:20 -0800, Matt Hancher wrote:
> On Nov 18, 5:15 pm, Malcolm Tredinnick <[EMAIL PROTECTED]>
> wrote:
> > On Mon, 2008-11-17 at 16:19 -0800, Matthew D. Hancher wrote:
> >
> > [...]
> >
> > > Options include:
> >
> > > A. Leave sqlite3 as the default, and add a configuration
On Nov 18, 5:15 pm, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> On Mon, 2008-11-17 at 16:19 -0800, Matthew D. Hancher wrote:
>
> [...]
>
> > Options include:
>
> > A. Leave sqlite3 as the default, and add a configuration setting that
> > forces use of pysqlite2 if desired.
>
> > B. Always tr
On Mon, 2008-11-17 at 16:19 -0800, Matthew D. Hancher wrote:
[...]
> Options include:
>
> A. Leave sqlite3 as the default, and add a configuration setting that
> forces use of pysqlite2 if desired.
>
> B. Always try both sqlite3 and pysqlite2, and use whichever has the
> greater version num
Hi again, time for my next GeoDjango-on-SQLite question.
In order to load the SpatiaLite extensions for SQLite, you first need
to enable SQLite extensions in the first place. Unfortunately,
pysqlite did not expose this functionality until pysqlite 2.5.0, which
means it didn't make it into
