[Numpy-discussion] 64bit infrastructure

[Chris Barker]

On Mon, Aug 20, 2012 at 3:51 PM, Travis Oliphant <travis at 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?

-Chris




> But, I would rather have official builds of NumPy for all platforms with a compiler paid for by a NumPy-sponsor than not have them.
>
> -Travis
>
>
>
> On Aug 20, 2012, at 5:28 PM, Chris Barker wrote:
>
>> On Sun, Aug 19, 2012 at 11:39 AM, Ralf Gommers > The problem is that,
>> unlike 32-bit builds, they can't be made with open
>>> source compilers on Windows. So unless we're okay with that,
>>
>> Why does it have to be built with open-source compilers? we're
>> building against the python.org python, yes? Which is built with the
>> MS compiler -- so why the insistance on open-source?
>>
>> -Chris
>>
>>
>>
>> --
>>
>> Christopher Barker, Ph.D.
>> Oceanographer
>>
>> Emergency Response Division
>> NOAA/NOS/OR&R            (206) 526-6959   voice
>> 7600 Sand Point Way NE   (206) 526-6329   fax
>> Seattle, WA  98115       (206) 526-6317   main reception
>>
>> Chris.Barker at noaa.gov
>> _______________________________________________
>> NumPy-Discussion mailing list
>> NumPy-Discussion at scipy.org
>> http://mail.scipy.org/mailman/listinfo/numpy-discussion
>
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion at scipy.org
> http://mail.scipy.org/mailman/listinfo/numpy-discussion



-- 

Christopher Barker, Ph.D.
Oceanographer

Emergency Response Division
NOAA/NOS/OR&R            (206) 526-6959   voice
7600 Sand Point Way NE   (206) 526-6329   fax
Seattle, WA  98115       (206) 526-6317   main reception

Chris.Barker at noaa.gov