In article <[EMAIL PROTECTED]>,
John Salerno <[EMAIL PROTECTED]> wrote:
>
>I was just thinking, since Python 3.0 is supposed to clean up a lot of
>the unnecessary or redundant features of Python and make other things
>more streamlined, does it seem to anyone that including SQLite goes
>against
John Salerno wrote:
> I was just thinking, since Python 3.0 is supposed to clean up a lot of
> the unnecessary or redundant features of Python and make other things
> more streamlined, does it seem to anyone that including SQLite goes
> against this goal?
Not to me. I don't see the redundancy.
John Salerno wrote:
> I was just thinking, since Python 3.0 is supposed to clean up a lot of
> the unnecessary or redundant features of Python and make other things
> more streamlined, does it seem to anyone that including SQLite goes
> against this goal?
>
> This is just me thinking out loud, min
John> I guess I am just trying to figure out why I'm a little surprised
John> sqlite was included, but at the same time I'm excited to use it
John> and the fact that it will now be standard has caused me to look
John> into more than otherwise. :)
You might find some of the discuss
Dan Sommers wrote:
> It's difficult to imagine
> any one developer (or development shop) using the entire library, so at
> least one module must be extraneous.
That's a good point. I guess I am just trying to figure out why I'm a
little surprised sqlite was included, but at the same time I'm exc
John Salerno <[EMAIL PROTECTED]> writes:
> I was just thinking, since Python 3.0 is supposed to clean up a lot
> of the unnecessary or redundant features of Python and make other
> things more streamlined, does it seem to anyone that including
> SQLite goes against this goal?
To my mind, "unneces
John Salerno wrote:
> This is just me thinking out loud, mind you, but it seems like including
> a database module (especially one that many people won't use in favor
> of MySQL or PostgreSQL, etc.) is weighing down the standard library.
Weighing down the standard library? The latest version of
I was just thinking, since Python 3.0 is supposed to clean up a lot of
the unnecessary or redundant features of Python and make other things
more streamlined, does it seem to anyone that including SQLite goes
against this goal?
This is just me thinking out loud, mind you, but it seems like incl
