rkdeli...@gmail.com wrote:
> An application package that I have requires Python 2.6 and NumPy.
>
> I've installed Python 2.6 in a parallel manner as follows:
>
> NO modification of the core Python2.4 in /usr/bin has been done.
> Rather, I installed Python 2.6 under /opt/Python_2.6.4 and modified my
An application package that I have requires Python 2.6 and NumPy.
I've installed Python 2.6 in a parallel manner as follows:
NO modification of the core Python2.4 in /usr/bin has been done. Rather, I
installed Python 2.6 under /opt/Python_2.6.4 and modified my user (not
root) environment var
Colin J. Williams wrote:
> Thanks for this. My aim is to extract a row of data from a line in a
> file and append it to an array. The number of columns is fixed but, at
> the start, the number of rows is unknown.
That is exactly the kind of use-case I had in mind.
In fact, you can use it now
On Tue, Nov 24, 2009 at 12:53 AM, wrote:
>
> Is this only related to the temporary (?) ABI breaking during the
> datetime merge, or do we now have to recompile all packages with
> c-extension each time we update numpy trunk?
Hopefully that's due to the temporary breakage.
There is unfortunatel
Christopher Barker wrote:
> Colin J. Williams wrote:
>> Access by the interpreter prevents array resizing.
>
> yup -- resize is really fragile for that reason. It really should be
> used quite sparingly.
>
> Personally, I think it should probably only be used when wrapped with
> a higher level l
On Nov 23, 2009, at 6:42 PM, Travis Oliphant wrote:
>
>
> I've made a few changes to datetime today and spent some time looking over
> what is there and what remains to be implemented.
As always, many thanks for your work !!
> Basically, the biggest thing left to do is to implement the low-l
On Mon, Nov 23, 2009 at 18:43, Dr. Phillip M. Feldman
wrote:
>
> I opened ticket #1302 to make the following enhancement request:
>
> I'd like to see hstack and vstack promote 1-D arguments to 2-D when this is
> necessary to make the dimensions match. In the following example, c_ works
> as expec
I opened ticket #1302 to make the following enhancement request:
I'd like to see hstack and vstack promote 1-D arguments to 2-D when this is
necessary to make the dimensions match. In the following example, c_ works
as expected while hstack does not:
[~]|8> x
<8>
array([[1, 2, 3],
[4,
I've made a few changes to datetime today and spent some time looking
over what is there and what remains to be implemented.
Basically, the biggest thing left to do is to implement the low-level
casting functions to and from datetime types and other numpy types.
In addition, the ufuncs n
Hi,
Having just written some cython code to iterate a neighborhood across
an array, I have some ideas about features that would be useful for a
general frame. Specifically, being able to pass in a "footprint"
boolean array to define the neighborhood is really useful in many
contexts. Also
Pauli Virtanen wrote:
> Mon, 23 Nov 2009 08:58:47 +0100, Sturla Molden wrote:
>
>> Pauli Virtanen skrev:
>>
>>> XXX: 3K: numpy.random is disabled for now, uses PyString_* XXX: 3K:
>>> numpy.ma is disabled for now -- some issues
>>>
>>>
>> I thought numpy.random uses Cython? Is it
I have several scikits with c extension compiled against an older
trunk version of 1.4 but didn't recompile them with the numpy trunk
version that I currently use.
scikits.timeseries just crashed on me taking several hours worth of
examples with it.
(scipy crashed during testing, so I rebuilt it im
Access by the interpreter prevents array resizing.
Yes, one can use the function, in place of the method but this appears
to require copying the whole array.
If one sets b= a, then that reference can be deleted with del b.
Is there any similar technique for the interpreter?
Colin W.
Python 2.
Thank you, this is a start. I seems that there are more issues to resolve. I am
trying to make a general frame that would enable one to write filters using
this iterator.
Nadav
-Original Message-
From: numpy-discussion-boun...@scipy.org on behalf of David Warde-Farley
Sent: Mon 23-
On Nov 23, 2009, at 4:36 AM, Pauli Virtanen wrote:
> Mon, 23 Nov 2009 01:40:00 -0500, Pierre GM wrote:
> [clip]
>>> XXX: 3K: numpy.ma is disabled for now -- some issues
>>
>> What are the issues ?
>
> Something resolving which would have taken more than 5 minutes :)
> Possibly because something
Mon, 23 Nov 2009 08:58:47 +0100, Sturla Molden wrote:
> Pauli Virtanen skrev:
>> XXX: 3K: numpy.random is disabled for now, uses PyString_* XXX: 3K:
>> numpy.ma is disabled for now -- some issues
>>
> I thought numpy.random uses Cython? Is it just a matter of recompiling
> the pyx-file?
The Cyt
Mon, 23 Nov 2009 01:40:00 -0500, Pierre GM wrote:
[clip]
>> XXX: 3K: numpy.ma is disabled for now -- some issues
>
> What are the issues ?
Something resolving which would have taken more than 5 minutes :)
Possibly because something that ma depends on is currently broken in
numpy.core.
I just w
Pauli Virtanen wrote:
> Setup.py runs 2to3 automatically for all changed files.
Yes, but I think it is more practical to have the build process to be 2
and 3-compatible.
> Of course, if it's possible to cater for24 and 3 at the same time,that's
> good. How do you work around the relative import
The issue with longs is that we wouldn't want array([1,2,3]) create object
arrays -- so we need to decide on casting rules for longs. Currently, I think
they're treated like python2 ints.
-- alkuper. viesti --
Aihe: Re: [Numpy-discussion] Numpy on Python3
Lähettäjä: Charles R Harris
Päivämäärä:
Setup.py runs 2to3 automatically for all changed files. Of course, if it's
possible to cater for24 and 3 at the same time,that's good. How do you work
around the relative imports andthe changed exception catching syntax?
-- alkuper. viesti --
Aihe: Re: [Numpy-discussion] Numpy on Python3
Lähettä
20 matches
Mail list logo
