headers
Matthew Brett | 1 Feb 2006 01:02
Picon
Gravatar

Re: gfortran, numpy build

> numpy.distutils has already support for both g95 and gfortran compilers.
> Run
>    python setup.py config_fc --help-fcompiler
> to see a list of supported Fortran compilers.

Oops - sorry, I completely missed that - and thanks a lot for the
pointer.  For those as slow as I am, the build command seemed to be:

python setup.py config --fcompiler=gnu95 build

I am afraid this is a sign that I am lost in the build system.  Is
there a good place to start to get to grips with options like the
above?

And, is there a simple way to pass my favorite compiler optimization
flags into the build?

Thanks a lot,

Matthew

-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642
Permalink | Reply | 0 comments |
headers
Colin J. Williams | 1 Feb 2006 04:53
Picon
Favicon

Re: RE: [Numpy-user] possible error with isarrtype

Fernando Perez wrote:
> O'Keefe, Michael wrote:
>>> Now, the data-type object itself is the preferred way.  I need to 
>>> figure
>>>  out what to do with these functions now and see if they even have 
>>> any use anymore.
>>
>>
>> Thanks Travis.
>>
>> With regard to what to do with the functions, I only ended up trying 
>> them
>> because they were there. From my point of view, I'd love to learn how to
>> code the "right" way. To that end, any means of informing the user of
>> "deprecated" functions (or just taking them out) would be fine with me.
>> However, I realize some may have legacy code and so I would defer to 
>> their
>> opinions.
>
>
> Python has a proper framework for deprecation warnings.  I'd say we 
> use that, and Travis can ruthlessly deprecate anything that's just 
> compatibility noise.
>
> Perhaps 1.0 can keep old but deprecated things around (numpy will see 
> a LOT of use once 1.0 comes out, far more than the current svn testing 
> crowd).  Then, as of 1.1 or 1.2 or whatever, those can be removed.
>
> Cheers,
>
(Continue reading)

Permalink | Reply | 5 comments |
headers
Travis Oliphant | 1 Feb 2006 05:04
Picon

Re: RE: [Numpy-user] possible error with isarrtype

Colin J. Williams wrote:

> One of the deprecated names is ArrayType.  This seems to be closer to 
> the Python style than ndarray.

Not really. 

Rather than test:
type(var) == types.IntType 

you should be testing
isinstance(var, int)

just like rather than testing
type(somearray) == ArrayType

you should be testing
isinstance(somearray, ndarray)

Python style has changed a bit since 2.2 allowed sub-typing builtings

-Travis

-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
Permalink | Reply | 4 comments |
headers
Zdeněk Hurák | 1 Feb 2006 15:19
Picon
Picon

Re: Numerical Mathematics Consortium vs. scipy and numpy

Christopher Barker wrote:

> In general,
> unfortunately, it looks to be quite commercially-focused: how does one
> get the open source community to be represented in this kind of thing?

I do not know the details, but one of the members of the consortium - Scilab
consortium - is kind of open-source. Well, their license is not purely free
(http://www.scilab.org/legal/license.html,
http://www.scilab.org/legal/index_legal.php?page=faq.html#q6), but it is
definitely not a commercial project. Perhaps some Scilab people could
answer some open-source related questions.

Note that I am not related to the NMC in any way, it is really that I only
found this link and as a newcomer to Python computing community, I am
simply interested what are the attitudes towards these issues here.   

Zdenek

-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
Permalink | Reply | 0 comments |
headers
Christopher Hanley | 1 Feb 2006 15:46

numpy.dtype problem

The following seems to have stopped working:

In [6]: import numpy

In [7]: a = numpy.ones((3,3),dtype=numpy.int32)

In [8]: a.dtype.name
---------------------------------------------------------------------------
exceptions.MemoryError                               Traceback (most 
recent call last)

/data/sparty1/dev/devCode/≤console>

MemoryError:

Chris

-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
Permalink | Reply | 2 comments |
headers
Colin J. Williams | 1 Feb 2006 17:15
Picon
Favicon

Re: RE: [Numpy-user] possible error with isarrtype

Travis Oliphant wrote:
> Colin J. Williams wrote:
>
>> One of the deprecated names is ArrayType.  This seems to be closer to 
>> the Python style than ndarray.
>
>
> Not really.
I agree with what you say below, but doesn't ArrayType have a greater
similarity to the Python types than ndarray?

[Dbg]>>> import types
[Dbg]>>> dir(types)
['BooleanType', 'BufferType', 'BuiltinFunctionType',
'BuiltinMethodType', 'ClassType', 'CodeType', 'ComplexType',
'DictProxyType', 'DictType', 'DictionaryType', 'EllipsisType',
'FileType', 'FloatType', 'FrameType', 'FunctionType', 'GeneratorType',
'Instance
Type', 'IntType', 'LambdaType', 'ListType', 'LongType', 'MethodType',
'ModuleType', 'NoneType', 'NotImplementedType', 'ObjectType',
'SliceType', 'StringType', 'StringTypes', 'TracebackType', 'TupleType',
'TypeType', 'UnboundMethodType', 'UnicodeType', 'XRan
geType', '__builtins__', '__doc__', '__file__', '__name__']
[Dbg]>>>

I presume that the aim is still that numpy will become a part of the
Python offering.

Colin W.
> Rather than test:
(Continue reading)

Permalink | Reply | 3 comments |
headers
Francesc Altet | 1 Feb 2006 17:36

Re: numpy.dtype problem

A Dimecres 01 Febrer 2006 15:46, Christopher Hanley va escriure:
> The following seems to have stopped working:
>
>
> In [6]: import numpy
>
> In [7]: a = numpy.ones((3,3),dtype=numpy.int32)
>
> In [8]: a.dtype.name
> ---------------------------------------------------------------------------
> exceptions.MemoryError                               Traceback (most
> recent call last)
>
> /data/sparty1/dev/devCode/≤console>
>
> MemoryError:

Below is a patch for this. It seems to me that Travis is introducing
new *scalar data types. I'm not sure if they should appear in this
case, but perhaps he can throw some light on this.

Cheers,

--

-- 
>0,0<   Francesc Altet     http://www.carabos.com/
V   V   Cárabos Coop. V.   Enjoy Data
 "-"

Index: numpy/core/src/arrayobject.c
===================================================================
(Continue reading)

Permalink | Reply | 1 comment |
headers
Gerard Vermeulen | 1 Feb 2006 18:14
Picon
Favicon

Re: RE: [Numpy-user] possible error with isarrtype

On Wed, 01 Feb 2006 11:15:09 -0500
"Colin J. Williams" <cjw <at> sympatico.ca> wrote:

[ depration + style ]

> [Dbg]>>> import types
> [Dbg]>>> dir(types)
> ['BooleanType', 'BufferType', 'BuiltinFunctionType',
> 'BuiltinMethodType', 'ClassType', 'CodeType', 'ComplexType',
> 'DictProxyType', 'DictType', 'DictionaryType', 'EllipsisType',
> 'FileType', 'FloatType', 'FrameType', 'FunctionType', 'GeneratorType',
> 'Instance
> Type', 'IntType', 'LambdaType', 'ListType', 'LongType', 'MethodType',
> 'ModuleType', 'NoneType', 'NotImplementedType', 'ObjectType',
> 'SliceType', 'StringType', 'StringTypes', 'TracebackType', 'TupleType',
> 'TypeType', 'UnboundMethodType', 'UnicodeType', 'XRan
> geType', '__builtins__', '__doc__', '__file__', '__name__']
> [Dbg]>>>
> 

Isn't the types module becoming superfluous?

[packer <at> zombie ~]$ python -E
Python 2.4 (#2, Feb 12 2005, 00:29:46)
[GCC 3.4.3 (Mandrakelinux 10.2 3.4.3-3mdk)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> long
<type 'long'>
>>> int
<type 'int'>
(Continue reading)

Permalink | Reply | 2 comments |
headers
Travis Oliphant | 1 Feb 2006 18:30
Picon

Re: numpy.dtype problem

Francesc Altet wrote:

>A Dimecres 01 Febrer 2006 15:46, Christopher Hanley va escriure:
>  
>
>>The following seems to have stopped working:
>>
>>
>>In [6]: import numpy
>>
>>In [7]: a = numpy.ones((3,3),dtype=numpy.int32)
>>
>>In [8]: a.dtype.name
>>---------------------------------------------------------------------------
>>exceptions.MemoryError                               Traceback (most
>>recent call last)
>>
>>/data/sparty1/dev/devCode/≤console>
>>
>>MemoryError:
>>    
>>
>
>Below is a patch for this. It seems to me that Travis is introducing
>new *scalar data types. I'm not sure if they should appear in this
>case, but perhaps he can throw some light on this.
>  
>
No, I'm not introducing anything new.  I just changed the name of the 
scalar type objects.  They used to be conveying type information for the
(Continue reading)

Permalink | Reply | 0 comments |
headers
Travis Oliphant | 1 Feb 2006 20:36
Favicon

Re: NumPy Behavior

Jay Painter wrote:

>Travis,
>
>I updated to the latest svn code this morning and ran some mmlib tests.
>Your commit has fixed the segmentation fault/illegal instruction error,
>but the mmlib test suite fails.  I'll look into it tonight, it may just
>be intentional differences between Numeric and NumPy.  I'll let you know
>what I find.
>  
>
Be sure to look over the list of differences in the sample chapter of my 
book (available at numeric.scipy.org)

The numpy.lib.convertcode module can be used to make most of the changes 
(but there may be a few it misses). 

>As I've been working with Numeric, I have often desired some particular
>features which I'd be willing to work on with NumPy.  Maybe these have
>come up before?
>
>1) Alternative implementations of matrixmultiply() and
>eigenvalues()/eigenvalues() for symmetric matrices.  For example, there
>is a analytic expression for the eigenvalues of a 3x3 symmetric matrix.
>
>2) New C implemented vectorM and matrixMN classes which support the
>array interface.  This could allow for lower memory usage via pool
>allocations and the customized implementations in item #1.  The ones I
>wish were there are:
>
(Continue reading)

Permalink | Reply | 0 comments |

Gmane