From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27036 invoked by alias); 9 Sep 2002 16:21:49 -0000 Mailing-List: contact gsl-discuss-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gsl-discuss-owner@sources.redhat.com Received: (qmail 27026 invoked from network); 9 Sep 2002 16:21:47 -0000 Received: from unknown (HELO mail.tepkom.ru) (195.9.10.14) by sources.redhat.com with SMTP; 9 Sep 2002 16:21:47 -0000 Received: from mojo.tepkom.ru (mojo.tepkom.ru [195.9.10.30]) by mail.tepkom.ru (8.11.6/8.11.6) with ESMTP id g89GLaq96402 for ; Mon, 9 Sep 2002 20:21:36 +0400 (MSD) (envelope-from wart@mojo.tepkom.ru) Received: from wart by mojo.tepkom.ru with local (Exim 3.35 #1 (Debian)) id 17oRHY-0005pw-00 for ; Mon, 09 Sep 2002 20:21:00 +0400 Date: Mon, 09 Sep 2002 09:26:00 -0000 From: Wartan Hachaturow To: gsl-discuss@sources.redhat.com Subject: Python GSL wrappers using SWIG. Message-ID: <20020909162100.GA22402@mojo.tepkom.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i X-SW-Source: 2002-q3/txt/msg00199.txt.bz2 Hello. I've hacked swig files by Arno Peters to get python wrappers. But I must say they're not that usable, because of C nature of gsl -- all those malloc's, etc. So now I do understand why pygsl is being written by hands :) Anyway, if somebody wants to play with swig files, the archive is available at http://mojo.tepkom.ru/pygsl-swig.tar.gz -- Regards, Wartan. "Computers are not intelligent. They only think they are."