(Addendum -- Mark Hammond suggests this may be a threading issue -- OpenDatabase() apparently causes Python threads to be initialized. Does NumPy or lapack lite use threads for anything?)
No.
The problem is that the statement 'print linear_...' never completes. I step through in the debugger under pythonwin, & the lapack routine called by linear_least_squares() never returns.
If I remove the statement 'db = engine...' it completes normally.
If I make a call to linear_least_squares() *before* the database stuff, the later call to linear_least_squares() works properly.
I don't know how dynamic libraries work under Windows, but I could imagine that your database modules uses a symbol which is also used in Linpack or the Linpack/Python interface. There ought to be tools to verify this. Konrad. -- ------------------------------------------------------------------------------- Konrad Hinsen | E-Mail: hinsen@cnrs-orleans.fr Centre de Biophysique Moleculaire (CNRS) | Tel.: +33-2.38.25.56.24 Rue Charles Sadron | Fax: +33-2.38.63.15.17 45071 Orleans Cedex 2 | Deutsch/Esperanto/English/ France | Nederlands/Francais -------------------------------------------------------------------------------