Re: [Numpy-discussion] how to compile Fortran using setup.py

On Thu, Mar 10, 2011 at 8:25 PM, Robert Kern wrote: > On Thu, Mar 10, 2011 at 19:58, Ondrej Certik wrote: >> Hi, >> >> I spent about an hour googling and didn't figure this out. Here is my >> setup.py: >> >> setup( >>    name = "libqsnake", >>    cmdclass = {'build_ext': build_ext}, >>    versio

Re: [Numpy-discussion] C API freeze and review

On Thu, Mar 10, 2011 at 10:10 PM, Charles R Harris wrote: > > > On Thu, Mar 10, 2011 at 12:25 AM, Charles R Harris > wrote: >> >> >> On Thu, Mar 10, 2011 at 12:15 AM, Ralf Gommers >> wrote: >>> >>> Hi all, >>> >>> In preparation for making a 1.6.x branch, I just updated the C API >>> version. Pl

Re: [Numpy-discussion] how to compile Fortran using setup.py

On Thu, Mar 10, 2011 at 19:58, Ondrej Certik wrote: > Hi, > > I spent about an hour googling and didn't figure this out. Here is my > setup.py: > > setup( >    name = "libqsnake", >    cmdclass = {'build_ext': build_ext}, >    version = "0.1", >    packages = [ >        'qsnake', >        'qsnake

[Numpy-discussion] how to compile Fortran using setup.py

Hi, I spent about an hour googling and didn't figure this out. Here is my setup.py: setup( name = "libqsnake", cmdclass = {'build_ext': build_ext}, version = "0.1", packages = [ 'qsnake', 'qsnake.calculators', 'qsnake.calculators.tests', 'qsnake.dat

[Numpy-discussion] Intel C Compiler users: please test

Hi, In commit dede2691 I've committed a change to the 32-bit Intel C compiler (adding -fPIC) and added a 64-bit "intelem" compiler. Please test, if there's any issue the 32-bit flag change can be reverted. Thanks, Ralf ___ NumPy-Discussion mailing list

Re: [Numpy-discussion] Request for a bit more info on structured arrays in the "basics" page

In article , Skipper Seabold wrote: >> The page >> >> gives a good introduction to structured arrays. However, it says nothing >> about how to set a particular element (all fields at once) from a >> collection of data. > ... > I added a bi

Re: [Numpy-discussion] Anybody going to PyCon?

I will be there tonight through Sunday night. I posted on Convore about a Visualization BoF, which may be of interest to folks in the numpy/scipy crowd: https://convore.com/pycon-2011/python-visualization-bof/ See you all there! -Peter On Mon, Mar 7, 2011 at 3:53 AM, Gökhan Sever wrote: > Hell

Re: [Numpy-discussion] Anybody going to PyCon?

Yung-Yu, We are advertised on this blog http://pycon.blogspot.com/2011/03/pycon-2011-outside-talks-poster-session.html I will be in the conference venue by tomorrow morning. There are many interesting talks and posters that I look forward seeing plus meeting those presenters. See you in Atlanta.

Re: [Numpy-discussion] ragged array implimentation

A Thursday 10 March 2011 20:29:00 Christopher Barker escrigué: > I don't think so -- my approach is a lot simpler that I think carray > is: > > it acts much like a python list: > > 1) it pre-allocates extra space when an array is created. same for carray > 2) when you append, it uses that extra

Re: [Numpy-discussion] ragged array implimentation

On 3/10/11 11:29 AM, Christopher Barker wrote: > By the way, it would be great to have a growable array that could be > efficiently used in Cython code -- so you could accumulate a bunch of > native C datatype data easily. I just noticed that carray is written in Cython, so that part should be ea

Re: [Numpy-discussion] ragged array implimentation

On 3/10/11 9:51 AM, Francesc Alted wrote: > A Thursday 10 March 2011 18:05:11 Christopher Barker escrigué: >> NOTE: this looks like it could use a "growable" numpy array, much >> like one I've written before -- maybe it's time to revive that >> project and use it here, fixing some performance issue

Re: [Numpy-discussion] Crash with nested recarray on Python 3.x

On 3/9/2011 10:29 PM, Charles R Harris wrote: > > > On Wed, Mar 9, 2011 at 11:20 PM, Christoph Gohlke > wrote: > > Hello, > > the following code crashes in the last line when using numpy 1.5.1 on > Python 3.1 and 3.2, 32 and 64 bit, for Windows. It works with

Re: [Numpy-discussion] ragged array implimentation

A Thursday 10 March 2011 18:05:11 Christopher Barker escrigué: > NOTE: this looks like it could use a "growable" numpy array, much > like one I've written before -- maybe it's time to revive that > project and use it here, fixing some performance issues while I'm at > it. A growable array would be

Re: [Numpy-discussion] ragged array implimentation

On 3/7/11 5:51 PM, Sturla Molden wrote: > Den 07.03.2011 18:28, skrev Christopher Barker: >> 1, 2, 3, 4 >> 5, 6 >> 7, 8, 9, 10, 11, 12 >> 13, 14, 15 >> ... >> > A ragged array, as implemented in C++, Java or C# is just an array of > arrays (or 'a pointer to an array of pointers'). Sure, but as a

Re: [Numpy-discussion] Is this the optimal way to take index along a single axis?

I see. Should functionality like this be included in numpy? Jon. On Tue, Mar 8, 2011 at 3:39 PM, wrote: > On Tue, Mar 8, 2011 at 3:03 PM, Jonathan Taylor > wrote: >> I am wanting to use an array b to index into an array x with dimension >> bigger by 1 where the element of b indicates what va

Re: [Numpy-discussion] problem with array/ndarray/list parameter to function

On Thu, Mar 10, 2011 at 4:04 AM, Mic J wrote: > Hi i have a problem with passing a parameter to a function > > > xtickvals = np.arange(0, total_project_days+5, 5) > > its for setting ticks on an axis, the x-axis > > Ex1: This works > xticks = pylab.setp(ax2, > xticklabels=['0','10','20','30','40

Re: [Numpy-discussion] C API freeze and review

On Thu, Mar 10, 2011 at 12:25 AM, Charles R Harris < charlesr.har...@gmail.com> wrote: > > > On Thu, Mar 10, 2011 at 12:15 AM, Ralf Gommers < > ralf.gomm...@googlemail.com> wrote: > >> Hi all, >> >> In preparation for making a 1.6.x branch, I just updated the C API >> version. Please do not add an

[Numpy-discussion] problem with array/ndarray/list parameter to function

Hi i have a problem with passing a parameter to a function xtickvals = np.arange(0, total_project_days+5, 5) its for setting ticks on an axis, the x-axis Ex1: This works xticks = pylab.setp(ax2, xticklabels=['0','10','20','30','40','50','60','70','80','90','100']) Ex2: This doesnt work xtickl

Re: [Numpy-discussion] Request for a bit more info on structured arrays in the "basics" page

Thu, 10 Mar 2011 15:23:59 +0800, Ralf Gommers wrote: [clip] >> x = np.array([1.5]) >> x.view(int) >> array([4609434218613702656]) Yes, `view` is meant to do exactly that. Use `astype` if you want a type cast. Pauli ___ NumPy-Discussion mailin