In Spyce, we use a convention where we tuck away the connection details in a module,

<%\
import MySQLdb
con=MySQLdb.Connect( host="foobar.com",
                     port=3306,
                     user="loginname",
                     passwd="loginpassword",
                     db="foobar")
%>

dbfoobar.py above, which is in a directory that is outside the locations served by the web server, (e.g. /usr/spyce-2.1/modules/dbfoobar.py). This is to avoid inadvertently leaking login details to the outside world.

However, because MySQLdb.Connect() cannot get called each time a Spyce script is run this way, you will get an Error 2006 ('Server has gone away') exception if you have not called the script for a while and its connection times out. The way to deal with this is to use the mysql ping() function:

<%\
from dbfoobar import con

con.ping(True)
cur=con.cursor()
%>

The method above ensures an automatic reconnection if the server ever goes away and should no longer display the error 2006 message. The pydoc documentation for ping() has full details:

>>> import MySQLdb

>>> help(MySQLdb._mysql.connection.ping)
Help on method_descriptor:

ping(...)
    Checks whether or not the connection to the server is
    working. If it has gone down, an automatic reconnection is
    attempted.

    This function can be used by clients that remain idle for a
    long while, to check whether or not the server has closed the
    connection and reconnect if necessary.

    New in 1.2.2: Accepts an optional reconnect parameter. If True,
    then the client will attempt reconnection. Note that this setting
    is persistent. By default, this is on in MySQL<5.0.3, and off
    thereafter.

    Non-standard. You should assume that ping() performs an
    implicit rollback; use only when starting a new transaction.
    You have been warned.