I Would like to hear the opinions of others on that point, but yes, I think
that is an appropriate procedure.
Travis
--
Travis Oliphant
(on a mobile)
512-826-7480
On Feb 29, 2012, at 10:54 AM, Matthew Brett wrote:
> Hi,
>
> On Wed, Feb 29, 2012 at 1:46 AM, Travis Oliphant wrote:
>> We
On Wed, Feb 29, 2012 at 11:07 PM, Matt Miller wrote:
> More reading of the thread linked solved the issue. To reiterate, add
> numpy/ and change .c to .h in line 590 of ieee754.c.src.
>
> Ex:
>
> elif defined(__CYGWIN__)
>include "numpy/fenv/fenv.h"
> endif
>
Thanks for confirming. Fixed i
28.02.2012 22:11, Ralf Gommers kirjoitti:
[clip]
> How about just putting it in a new github repo so everyone can see/review
> the mapping between Trac and YouTrack fields?
>
> We should probably create a basic export from YouTrack script at the
> same time, to make sure there's no lock-in.
Keepi
More reading of the thread linked solved the issue. To reiterate, add
numpy/ and change .c to .h in line 590 of ieee754.c.src.
Ex:
elif defined(__CYGWIN__)
include "numpy/fenv/fenv.h"
endif
Thanks,
On Wed, Feb 29, 2012 at 1:41 PM, Matt Miller wrote:
> That fixed changed my error message
That fixed changed my error message to this:
numpy/core/src/private/lowlevel_strided_loops.h:404:1: warning:
‘PyArray_PrepareThreeRawArrayIter’ declared ‘static’ but never defined
numpy/core/src/private/lowlevel_strided_loops.h:430:1: warning:
‘PyArray_PrepareFourRawArrayIter’ declared ‘static’ bu
On Wed, Feb 29, 2012 at 9:10 PM, Matt Miller wrote:
> Hi all,
>
> I am getting the following error when running `python setup.py install`
> for Numpy in Cygwin. This error happens on the latest as well as
> the maintenance branched for 1.5 and 1.6.
>
This should fix it: http://projects.scipy.org
On Wed, Feb 29, 2012 at 1:09 PM, Francesc Alted wrote:
> On Feb 29, 2012, at 11:52 AM, Pierre Haessig wrote:
>
> > Hi,
> >
> > Le 29/02/2012 16:22, Paweł Biernat a écrit :
> >> Is there any way to interact with Fortran's real(16) (supported by gcc
> >> and Intel's ifort) data type from numpy? By r
Pierre Haessig crans.org> writes:
>
> Hi,
>
> Le 29/02/2012 16:22, Paweł Biernat a écrit :
> > Is there any way to interact with Fortran's real(16) (supported by gcc
> > and Intel's ifort) data type from numpy? By real(16) I mean the
> > binary128 type as in IEEE 754. (In C this data type is expe
Hi all,
I am getting the following error when running `python setup.py install` for
Numpy in Cygwin. This error happens on the latest as well as
the maintenance branched for 1.5 and 1.6.
...
creating build/temp.cygwin-1.7.11-i686-2.6
creating build/temp.cygwin-1.7.11-i686-2.6/build
creating build
On Feb 29, 2012, at 11:52 AM, Pierre Haessig wrote:
> Hi,
>
> Le 29/02/2012 16:22, Paweł Biernat a écrit :
>> Is there any way to interact with Fortran's real(16) (supported by gcc
>> and Intel's ifort) data type from numpy? By real(16) I mean the
>> binary128 type as in IEEE 754. (In C this data
Hi,
Le 29/02/2012 16:22, Paweł Biernat a écrit :
> Is there any way to interact with Fortran's real(16) (supported by gcc
> and Intel's ifort) data type from numpy? By real(16) I mean the
> binary128 type as in IEEE 754. (In C this data type is experimentally
> supported as __float128 (gcc) and _Q
On Wed, Feb 29, 2012 at 10:22 AM, Paweł Biernat wrote:
> I am completely new to Numpy and I know only the basics of Python, to
> this point I was using Fortran 03/08 to write numerical code. However,
> I am starting a new large project of mine and I am looking forward to
> using Python to call som
On Wed, Feb 29, 2012 at 7:57 PM, Erin Sheldon wrote:
> Excerpts from Nathaniel Smith's message of Wed Feb 29 13:17:53 -0500 2012:
> > On Wed, Feb 29, 2012 at 3:11 PM, Erin Sheldon
> wrote:
> > > Excerpts from Nathaniel Smith's message of Tue Feb 28 17:22:16 -0500
> 2012:
> > >> > Even for binary,
On Wed, Feb 29, 2012 at 1:20 PM, Neal Becker wrote:
>
> Much of Linus's complaints have to do with the use of c++ in the _kernel_.
> These objections are quite different for an _application_. For example,
> there
> are issues with the need for support libraries for exception handling.
> Not an
Charles R Harris wrote:
> On Tue, Feb 28, 2012 at 12:05 PM, John Hunter wrote:
>
>> On Sat, Feb 18, 2012 at 5:09 PM, David Cournapeau wrote:
>>
>>>
>>> There are better languages than C++ that has most of the technical
>>>
>>> benefits stated in this discussion (rust and D being the most
>>> "ob
Excerpts from Nathaniel Smith's message of Wed Feb 29 13:17:53 -0500 2012:
> On Wed, Feb 29, 2012 at 3:11 PM, Erin Sheldon wrote:
> > Excerpts from Nathaniel Smith's message of Tue Feb 28 17:22:16 -0500 2012:
> >> > Even for binary, there are pathological cases, e.g. 1) reading a random
> >> > sub
Hi,
On Wed, Feb 29, 2012 at 1:46 AM, Travis Oliphant wrote:
> We already use the NEP process for such decisions. This discussion came
> from simply from the *idea* of writing such a NEP.
>
> Nothing has been decided. Only opinions have been shared that might
> influence the NEP. This is all
On Wed, Feb 29, 2012 at 3:11 PM, Erin Sheldon wrote:
> Excerpts from Nathaniel Smith's message of Tue Feb 28 17:22:16 -0500 2012:
>> > Even for binary, there are pathological cases, e.g. 1) reading a random
>> > subset of nearly all rows. 2) reading a single column when rows are
>> > small. In c
Hi,
On Wed, Feb 29, 2012 at 12:13 PM, Jonathan Rocher wrote:
> Thanks to your question, I discovered that there is a float128 dtype in
> numpy
>
> In[5]: np.__version__
> Out[5]: '1.6.1'
>
> In[6]: np.float128?
> Type: type
> Base Class:
> String Form:
> Namespace: Interactive
> File:
> /
Thanks to your question, I discovered that there is a float128 dtype in
numpy
In[5]: np.__version__
Out[5]: '1.6.1'
In[6]: np.float128?
Type: type
Base Class:
String Form:
Namespace: Interactive
File:
/Library/Frameworks/Python.framework/Versions/7.2/lib/python2.7/site-packages/numpy/__in
On Tue, Feb 28, 2012 at 11:28 PM, Mark Wiebe wrote:
> The development approach I really like is to start with a relatively rough
> NEP, then cycle through feedback, updating the NEP, and implementation.
> Organizing ones thoughts to describe them in a design document can often
> clarify things tha
On Wed, Feb 29, 2012 at 15:11, Erin Sheldon wrote:
> Excerpts from Nathaniel Smith's message of Tue Feb 28 17:22:16 -0500 2012:
>> > Even for binary, there are pathological cases, e.g. 1) reading a random
>> > subset of nearly all rows. 2) reading a single column when rows are
>> > small. In cas
I am completely new to Numpy and I know only the basics of Python, to
this point I was using Fortran 03/08 to write numerical code. However,
I am starting a new large project of mine and I am looking forward to
using Python to call some low level Fortran code responsible for most
of the intensive n
Excerpts from Erin Sheldon's message of Wed Feb 29 10:11:51 -0500 2012:
> Actually, for numpy.memmap you will read the whole file if you try to
> grab a single column and read a large fraction of the rows. Here is an
That should have been: "...read *all* the rows".
-e
--
Erin Scott Sheldon
Broo
Excerpts from Nathaniel Smith's message of Tue Feb 28 17:22:16 -0500 2012:
> > Even for binary, there are pathological cases, e.g. 1) reading a random
> > subset of nearly all rows. 2) reading a single column when rows are
> > small. In case 2 you will only go this route in the first place if you
25 matches
Mail list logo
