On Wed, Aug 22, 2012 at 11:40 AM, David Cournapeau <courn...@gmail.com> wrote: > On Tue, Aug 21, 2012 at 12:15 AM, Chris Barker <chris.bar...@noaa.gov> wrote: >> On Mon, Aug 20, 2012 at 3:51 PM, Travis Oliphant <tra...@continuum.io> wrote: >>> I'm actually not sure, why. I think the issue is making sure that >>> the release manager can actually "build" NumPy without having >>> to buy a particular compiler. >> >> The MS Express editions, while not open source, are free-to-use, >> and work fine. >> >> Not sure what what do about Fortran, though, but that's a scipy, not a >> numpy issue, yes? > > fortran is the issue. Having one or two licenses of say Intel Fortran > compiler is not enough because it makes it difficult for people to > build on top of scipy. > > David
For those users/developers/packages using NumPy but not SciPy, does this matter? Having just official NumPy 64bit Windows packages would still be very welcome. Is the problem that whatever route NumPy goes down will have potential implications/restrictions for how SciPy could proceed? Peter _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
