Path: csiph.com!usenet.pasdenom.info!aioe.org!news.stack.nl!newsfeed.xs4all.nl!newsfeed4.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
MIME-Version: 1.0
In-Reply-To: <CAMw+j7L+M8-qWL4yyihfqGcqzNA7_=BMQx3ExrH9zds8apg=bg@mail.gmail.com>
References: <l2pois$359$1@dont-email.me> <l2ppnh$9fc$1@dont-email.me> <l2puok$5i8$1@dont-email.me> <l2qvju$hoi$1@dont-email.me> <CAMw+j7L+M8-qWL4yyihfqGcqzNA7_=BMQx3ExrH9zds8apg=bg@mail.gmail.com>
Date: Mon, 7 Oct 2013 00:37:55 +1100
Subject: Re: Database engine bindings for Python (was: Database statements via python but database left intact)
From: Chris Angelico <rosuav@gmail.com>
To: python-list@python.org
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.781.1381066683.18130.python-list@python.org>
Lines: 42
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:56256

On Sun, Oct 6, 2013 at 8:10 PM, Chris =93Kwpolska=94 Warrick
<kwpolska@gmail.com> wrote:
> It would require Postgres around people=92s (or at least packagers=92)
> systems, and it often gets messy when we have such requirements.

I would hope that an absence of libpq could simply result in a
courteous exception when the module's imported, but maybe that'd be
hard to implement.

> Also, Postgres is much harder to configure than MySQL,
> especially if you have no experience or an asshole OS.

You can get a ready-to-go Postgres under Debian by simply apt-getting
it. The default config might not give you optimum performance, but
it'll work just fine. Most people shouldn't need to dig into the
configs of _any_ database before getting the app going -
out-of-the-box settings should be fine for early development, even
deployment if you're not doing a lot of traffic.

> Moreover, the stdlib is where packages come to die.

Fair point. That is an issue.

> We should also educate people on how PostgreSQL works with a nice,
> human-friendly tutorial.  Especially in some non-standard things and
> things that differ between PostgreSQL and MySQL =97 like how to make an
> auto-incrementing ID field (use sequences), or how PostgreSQL arrays
> work, among others.  The wiki (that nobody reads anyways) could also
> use some marketing fixes.

Maybe! Possibly go a bit further and say "How-to: Python and
Databasing", which could mention SQLite (great for something tiny),
PostgreSQL (great for concurrency / multi-user), and "Other databases
can also be used, with similar or identical APIs - check out PyPI for
a module for your favorite database engine".

I guess the above paragraph is sentencing [1] me to write the article, now.=
..

ChrisA

[1] if you'll pardon a terrible pun