Path: csiph.com!usenet.pasdenom.info!aioe.org!news.stack.nl!newsfeed.xs4all.nl!newsfeed3.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
To: python-list@python.org
From: Ned Deily <nad@acm.org>
Subject: Re: python-noob - which container is appropriate for later exporting into mySql + matplotlib ?
Date: Sun, 14 Apr 2013 09:40:53 -0700
References: <kk4nkd$ain$1@dont-email.me> <kk6tk2$inl$1@dont-email.me> <kk9433$l9s$1@dont-email.me> <kk9ef7$9ll$1@dont-email.me> <kk9s22$i7n$1@dont-email.me> <kka56d$beu$1@dont-email.me> <5168b87f$0$29977$c3e8da3$5496439d@news.astraweb.com> <kkbe5r$isk$1@dont-email.me> <mailman.550.1365853145.3114.python-list@python.org> <kkbmfq$7ed$1@dont-email.me> <mailman.551.1365861813.3114.python-list@python.org> <kkbqhd$29r$1@dont-email.me> <mailman.555.1365869763.3114.python-list@python.org> <2d737309-6608-4e2e-8ff1-2b8b020a418c@qc10g2000pbb.googlegroups.com> <516a6125$0$29977$c3e8da3$5496439d@news.astraweb.com> <8555d9af-e52e-47d6-b2bd-ef7fe5dd61d9@pl9g2000pbb.googlegroups.com> <CAPTjJmrP_9saiG89DKse-P6D0kPBjXMfe1731dfFAguKvaSO+Q@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
User-Agent: MT-NewsWatcher/3.5.3b3 (Intel Mac OS X)
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.588.1365957665.3114.python-list@python.org>
Lines: 37
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:43572

In article 
<CAPTjJmrP_9saiG89DKse-P6D0kPBjXMfe1731dfFAguKvaSO+Q@mail.gmail.com>,
 Chris Angelico <rosuav@gmail.com> wrote:
 > Actually, this is one place where I disagree with the current decision
> of the Python core devs: I think bindings for other popular databases
> (most notably PostgreSQL, and probably MySQL since it's so widely
> used) ought to be included in core, rather than being shoved off to
> PyPI. Databasing is so important to today's world that it would really
> help if people had all the options right there in core, if only so
> they're more findable (if you're browsing docs.python.org, you won't
> know that psycopg is available). Currently the policy seems to be "we
> don't include the server so why should we include the client"; I
> disagree, I think the client would stand nicely on its own. (Does
> Python have a DNS server module? DNS client? I haven't dug deep, but
> I'm pretty sure I can do name lookups in Python, yet running a DNS
> server is sufficiently arcane that it can, quite rightly, be pushed
> off to PyPI.) But this is minor, and tangential to this discussion.

For the bindings to be useful, Python batteries-included distributions 
(like python.org installers) would either need to also ship the various 
DB client libraries for all supported platforms (including Windows), 
which adds complexity and potentially intractable license issues, or 
there would need to be reverse-engineered implementations of the client 
libs or wire protocols, either option adding fragility and complex 
testing issues.  DNS client lookups use published, well-understood 
Internet-standard protocols, not at all like talking to a third-party 
database, be it open-source or not.  Sqlite3 is certainly an anomaly in 
that it is not-only open source but designed to be a lightweight, 
compatible library that runs on just about everything, and with a 
fanatical devotion to compatibility and documentation.  These days just 
about every major product or operating system platform ships with or 
uses a copy of sqllite3 for something.

-- 
 Ned Deily,
 nad@acm.org