Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@sources.redhat.com>
List-Help: <mailto:cygwin-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@sources.redhat.com
Delivered-To: mailing list cygwin@sources.redhat.com
Message-ID: <005201c0d1be$6ef6bfb0$d938a8c0@Hadfield>
From: "Mark Hadfield" <m.hadfield@niwa.cri.nz>
To: "Jason Tishler" <Jason.Tishler@dothill.com>
Cc: "Norman Vine" <nhv@cape.com>, "Robert Yodlowski" <RYodlowski@Pirus.com>,
        "Cygwin Mailing List" <cygwin@cygwin.com>
References: <007c01c0d0fd$ff878a30$d938a8c0@Hadfield> <20010430103616.D593@dothill.com>
Subject: Re: Cygwin Python 2.1, Numeric package, exporting init<module> methods
Date: Tue, 1 May 2001 09:42:19 +1200
Organization: NIWA
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400

From: "Jason Tishler" <Jason.Tishler@dothill.com>
> IMO, submitting a patch to the Numpy maintainers using the DL_EXPORT
> macro approach is the way to go.  This is the approach that I used
> successfully for numerous standard Python modules.  See the following
> for Tim Peters assessment of this approach:
>
>     http://mail.python.org/pipermail/python-dev/2001-February/013292.html

If this is to be the "standard" approach, then that's fine. I guess it
should be documented in "Extending Python"?

The alternative is changing the compilation & linking process to generate &
use .def files. Norman Vine reported to me yesterday that he could build
Numpy without the DL_EXPORT macros. When we compared notes it turned out
that he was using a modified version of distutils. Basically Norman's
approach is to build with the "cygwin" compiler option:

    python setup.py --compiler=cygwin

and the distutils patch is attached below my sig. I think it's fairly
self-explanatory.

> Why don't you try the Numpy maintainers and see what they have to say?
> Since they already support a Win32 port, I can't imagine much resistance
> on their part.

I'd be glad to do that but first I would like a ruling from the
Cygwin-Python gods about which of these approaches is the
one-true-Pythonic-way.

---
Mark Hadfield
m.hadfield@niwa.cri.nz  http://katipo.niwa.cri.nz/~hadfield
National Institute for Water and Atmospheric Research


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple