Re: [Numpy-discussion] numpy-1.4.0 no longer available for download?
Ahhh I see this is due to the ABI change, sorry for the noise. Cheers Adam On Mon, Feb 15, 2010 at 21:00, Adam Mercer ramer...@gmail.com wrote: Hi According to the NumPy download page http://sourceforge.net/projects/numpy/files/ the latest available version is 1.3.0, what happened to 1.4.0? Apologies if I've missed some announcement. Cheers Adam ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] F2PY error with G95 on Mac OS 10.5
On Wed, Jun 10, 2009 at 12:44, Samir Unnisru...@gmail.com wrote: I'm trying to use F2PY on Mac OS 10.5 with G95, but I'm getting the error g95: unrecognized option '-shared'. I tried modifying the NumPy code to use the correct -dynamic flag, rather than the -shared flag. While that does allow for F2PY to successfully execute, I get the error Traceback (most recent call last): File stdin, line 1, in module ImportError: dlopen(/Users/srunni/src/pdb2pqr/pdb2pqr/tinker/src/tinker/source/ese.so, 2): no suitable image found. Did find: /Users/srunni/src/pdb2pqr/pdb2pqr/tinker/src/tinker/source/ese.so: unknown file type, first eight bytes: 0x80 0xC0 0x4F 0x00 0xEB 0x57 0xE0 0x8F when I attempt to import the generated module. Any ideas on how to fix this? AFAIK g95 is not supported by numpy distutils on Mac OS X. Cheers Adam ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] F2PY error with G95 on Mac OS 10.5
On Wed, Jun 10, 2009 at 15:04, Samir Unnisru...@gmail.com wrote: Are you sure? When I run f2py -c --help-fcompiler, I get: List of available Fortran compilers: --fcompiler=g95 G95 Fortran Compiler (0.91) G95 is the only compiler listed as available. If it can't be used, then what can? I would actually prefer to use GFortran, but that is not listed as available. I get the following with numpy-1.3.0: $ f2py -c --help-fcompiler Fortran compilers found: Compilers available for this platform, but not found: --fcompiler=absoft Absoft Corp Fortran Compiler --fcompiler=g95 G95 Fortran Compiler --fcompiler=gnu GNU Fortran 77 compiler --fcompiler=gnu95 GNU Fortran 95 compiler --fcompiler=ibm IBM XL Fortran Compiler --fcompiler=intel Intel Fortran Compiler for 32-bit apps --fcompiler=nag NAGWare Fortran 95 Compiler Compilers not available on this platform: --fcompiler=compaq Compaq Fortran Compiler --fcompiler=hpux HP Fortran 90 Compiler --fcompiler=intele Intel Fortran Compiler for Itanium apps --fcompiler=intelem Intel Fortran Compiler for EM64T-based apps --fcompiler=intelev Intel Visual Fortran Compiler for Itanium apps --fcompiler=intelv Intel Visual Fortran Compiler for 32-bit apps --fcompiler=laheyLahey/Fujitsu Fortran 95 Compiler --fcompiler=mips MIPSpro Fortran Compiler --fcompiler=none Fake Fortran compiler --fcompiler=pg Portland Group Fortran Compiler --fcompiler=sun Sun or Forte Fortran 95 Compiler --fcompiler=vast Pacific-Sierra Research Fortran 90 Compiler For compiler details, run 'config_fc --verbose' setup command. $ Cheers Adam ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] F2PY error with G95 on Mac OS 10.5
On Wed, Jun 10, 2009 at 15:19, Samir Unnisru...@gmail.com wrote: That's odd. You're running Mac OS 10.5.7? Did you install NumPy manually or via Fink? Yep Intel 10.5.7, installed from MacPorts. Cheers Adam ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] scipy 0.7.1rc2 released
On Fri, Jun 5, 2009 at 06:09, David Cournapeaucourn...@gmail.com wrote: Please test it ! I am particularly interested in results for scipy binaries on mac os x (do they work on ppc). Test suite passes on Intel Mac OS X (10.5.7) built from source: OK (KNOWNFAIL=6, SKIP=21) nose.result.TextTestResult run=3486 errors=0 failures=0 Cheers Adam ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Python2.4 support
On Sun, Dec 7, 2008 at 23:42, David Cournapeau [EMAIL PROTECTED] wrote: I am strongly against dropping 2.4 support anytime soon. I haven't seen a strong rationale for using = 2.5 features in numpy, supporting 2.4 is not so hard, and 2.4 is still the default python version on many OS (mac os X 10.4 I believe, RHEL for sure, open solaris). Mac OS X 10.4 uses python-2.3, 10.5 uses python-2.5. Cheers Adam ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] Specifying a fortran compiler on numpy build.
Hi If I specify a fortran compiler when building numpy, does that have any effect on what is installed? In other words, must I build numpy against a fortran compiler in order to successfully build and use extension written in fortran - such as scipy? Cheers Adam ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Specifying a fortran compiler on numpy build.
On Fri, Jun 20, 2008 at 4:38 PM, Robert Kern [EMAIL PROTECTED] wrote: No. It just affects the Fortran compiler (if any) used to build numpy. The only place this might affect you is if you use a LAPACK or BLAS that needs to be linked with a Fortran compiler. Generally, you don't have to specify anything. Thanks for the clarification. Cheers Adam ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] planet.scipy.org
On Dec 31, 2007 10:43 PM, Jarrod Millman [EMAIL PROTECTED] wrote: Hey, I just wanted to announce that we now have a NumPy/SciPy blog aggregator thanks to Gaël Varoquaux: http://planet.scipy.org/ When I try to load http://planet.scipy.org I get an error saying that the page doesn't exist, however the scipy home page, i.e. http://www.scipy.org, now appears to be the planet aggregator is this just a temporary DNS issue? Cheers Adam ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] appending extra items to arrays
On 11/10/2007, Robert Kern [EMAIL PROTECTED] wrote: Appending to a list then converting the list to an array is the most straightforward way to do it. If the performance of this isn't a problem, I recommend leaving it alone. Thanks, I'll leave it as is - I was just wondering if there was a better way to do it. Cheers Adam ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] appending extra items to arrays
On 11/10/2007, Mark Janikas [EMAIL PROTECTED] wrote: If you do not know the size of your array before you finalize it, then you should use lists whenever you can. I just cooked up a short example: snip # Result # Total Time with array: 2.12951189331 Total Time with list: 0.0469707035741 Hope this helps, That is helpful, I thought that using arrays would be much faster but its clearly not in this case. Thanks Adam ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] appending extra items to arrays
Hi In some code I have, I need to append some extra data to a given array. At the moment I construct the data in a list, append the extra information I need and then convert the final list to an array. Is there a way that I can append extra information to an existing array thereby negating the need for the list, as the array object doesn't seem to have an append() method? Cheers Adam ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Convert array type
On 08/10/2007, Ryan May [EMAIL PROTECTED] wrote: Why not use numpy.fromstring? because that results in the array being filled with gibberish values = numpy.fromstring(wavearray, dtype=float, count=-1, sep='') print values gives: [ 1.39804329e-076 1.30354290e-076 1.18295070e-076 ..., 5.45168074e-067 2.11101912e-052 6.58519056e-260] where using values = array(wavearray.split()).astype(float) print values results in the correct [ 0.e+00 0.e+00 0.e+00 ..., 4.22233200e-23 3.86799900e-23 3.48452000e-23] Cheers Adam ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Convert array type
On 08/10/2007, Robert Kern [EMAIL PROTECTED] wrote: Use sep=' '. As the docstring says, if sep is empty, then the string is interpreted as binary data. If it is not empty, then the string is interpreted as ASCII. Thanks, got it the wrong way round. That works now. Cheers Adam ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] Convert array type
Hi I am fairly new to using numpy and am running into a problem regarding the type of an array. The array in question is created using the following code: values = array(wavearray.split()) where wavearray is a string containing a series of floats separated by white space, it appears that the individual elements of the values array are strings, where I need them to be floats. How can I ensure that the individual elements of the values array are floats, not strings? I have tried using values = array(wavearray.split(), dtype=float) but that results in the error: ValueError: setting an array element with a sequence. Cheers Adam ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Convert array type
On 07/10/2007, Gary Ruben [EMAIL PROTECTED] wrote: Try using astype. This works: values = array(wavearray.split()).astype(float) Thanks Gary, that does the trick. Cheers Adam ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
