On Fri, Jan 30, 2009 at 9:41 AM, Michael Colonno wrote:
>This is the first failure in the build log:
>
> _configtest.c
> _configtest.c(1): catastrophic error: could not open source file
> "inttypes.h"
> #include
>^
>
> compilation aborted for _configtest.c (code 4)
>
Hi Tim
Thank you for your interest! To answer your various questions order
of approximately increasing complexity:
Most importantly: the currently available version of Resolver One
does not have numpy support built in, and for various reasons I
wouldn't advise trying to integrate Ironclad w
This is the first failure in the build log:
_configtest.c
_configtest.c(1): catastrophic error: could not open source file
"inttypes.h"
#include
^
compilation aborted for _configtest.c (code 4)
failure.
I don't have this file anywhere on my system; it appears to b
Hello William,
once again.
I just noticed that Resolver One can only import data from Excel.
In science, the common low level data exchange format is ASCII text
like: CSV or tab separated.
You may consider adding this.
I did not find any installation instructions contained in the docs for
the
OK, I'm on the cusp of success now. I updated to the most recent code and
get to a sequence of errors surround math functions. This must be due to
linking the MKL libs. I tried various combinations (including those
recommended by the MKL docs) but could not get around the errors. Looks like
a mi
Hello William,
> * A few performance improvements.
> * Over 900 NumPy tests now pass: in fact, almost all the tests from the
> core, fft, lib, linalg, ma, oldnumeric and random subpackages.
I have some questions here for the science interested. I hope that they
are not too specific:
* Can you a
On Fri, Jan 30, 2009 at 2:43 AM, Michael Colonno wrote:
>Not sure if it's a VS thing since I get different compile errors with
> either the MS or Intel C compiler under the same environment (Visual Studio
> for x64 console). Let me start with a more basic question: I'm using the
> package avai
Not sure if it's a VS thing since I get different compile errors with
either the MS or Intel C compiler under the same environment (Visual Studio
for x64 console). Let me start with a more basic question: I'm using the
package available on SourceForge (1.2.1, 2008-10-29 14:36). If it can be
conf
> numpy\core\src\umathmodule.c.src(64): error: expected an identifier
> static float frexpf(float x, int * i)
>^
>
> numpy\core\src\umathmodule.c.src(64): error: expected a ")"
> static float frexpf(float x, int * i)
>^
>
> numpy\core\src\umathmodule.c.src(65): e
OK, I think I have a much better understanding of how this all gets
assembled now. I've got the build environment using both Intel compilers
(C++ and Fortran) and linked to the Intel MKL. Using the Intel C compiler
(icl.exe, more "gcc-like") as a replacement cl.exe (it supports the same
options,
The first option doesn't accept complex data.
-gideon
On Jan 29, 2009, at 1:18 AM, Nadav Horesh wrote:
> There are at least two options:
> 1. use convolve1d from numpy.numarray.nd_image (or scipy.ndimage)
> 2. use scipy.signal.convolve and adjust the dimensions of the
> convolution kenel to ali
Michael Colonno wrote:
>OK, some progress here. I have two questions: 1) Let's forget about
> the Intel compiler(s) for the moment and focus on a standard Windows
> build. Python 2.6 comes with two classes in distutils: msvccompiler.py
> and msvc9compiler.py. In reading through these, it appear
OK, some progress here. I have two questions: 1) Let's forget about the
Intel compiler(s) for the moment and focus on a standard Windows build.
Python 2.6 comes with two classes in distutils: msvccompiler.py and
msvc9compiler.py. In reading through these, it appears msvc9compiler.py is
ideally s
David Cournapeau wrote:
> It is said in the email that this is reserved to the python project, and
> prominent python projects like Twisted and Django. Would it be ok to try
> to be qualified as a prominent python project as well ?
Give it some time. Nobody - not even the Python core devs - have a
Hi all
I'm delighted to announce the release of Ironclad v0.8 -- the
all-singing, all-dancing CPython API compatibility layer for IronPython
-- available now from http://code.google.com/p/ironclad/ . Notable
improvements over the last release include:
* Ironclad is now a neatly self-contained
Hi,
I am interested in contributing to the port of NumPy to Python 3. Who
I should coordinate effort with?
I have started at the Python end of the problem (as opposed to
http://www.scipy.org/Python3k), e.g. I have several patches to get
2to3 to work on NumPy's Python source code.
James.
___
> 2009/1/29 Pierre GM :
> Pauli, how often is the documentation on docs.scipy.org updated from
> SVN ?
My understanding is the following:
SVN -> doc-wiki - updated once daily at around 10:00 (UTC?).
doc-wiki -> SVN - infrequently, when someone applies one or more doc
patches produced from the doc
On Jan 29, 2009, at 3:17 AM, Pauli Virtanen wrote:
> Thu, 29 Jan 2009 00:28:46 -0500, Pierre GM wrote:
>> Is there an objects.inv lying around for the numpy reference guide,
>> or
>> should I start one from scratch ?
>
> It's automatically generated by Sphinx, and can be found at
>
> http
Thu, 29 Jan 2009 00:28:46 -0500, Pierre GM wrote:
> Is there an objects.inv lying around for the numpy reference guide, or
> should I start one from scratch ?
It's automatically generated by Sphinx, and can be found at
http://docs.scipy.org/doc/numpy/objects.inv
Let's make the promise th
19 matches
Mail list logo
