Hi,
I'm having trouble with creating np.string_ fields in recarrays. If I
create a recarray using
np.rec.fromrecords([(1,'hello'),(2,'world')],names=['a','b'])
the result looks fine:
rec.array([(1, 'hello'), (2, 'world')], dtype=[('a', 'http://mail.scipy.org/mailman/listinfo/numpy-discussion
thanks for the suggestion! I will look into it. The other thing is
that the numpy arrays in question are actually embedded in another
object. When I convert the numpy arrays into plain lists, and then
cPickle them, there is no problem with any of the larger objects. That
is the way we are currently
On Mon, Nov 2, 2009 at 2:42 PM, Reckoner wrote:
> Anybody have any ideas here?
>
> Otherwise, I'm thinking this should be posted to the numpy bugs list.
> What's the best way to report a bug of this kind?
>
> Thanks!
>
> On Fri, Oct 30, 2009 at 5:48 PM, Reckoner wrote:
>>> Robert Kern wrote:
>>>
On Mon, Nov 2, 2009 at 15:42, Reckoner wrote:
> Anybody have any ideas here?
Nope!
> Otherwise, I'm thinking this should be posted to the numpy bugs list.
> What's the best way to report a bug of this kind?
Create a new ticket on the Trac:
http://projects.scipy.org/numpy/
If you can attach th
Anybody have any ideas here?
Otherwise, I'm thinking this should be posted to the numpy bugs list.
What's the best way to report a bug of this kind?
Thanks!
On Fri, Oct 30, 2009 at 5:48 PM, Reckoner wrote:
>> Robert Kern wrote:
>> You can import numpy.core.multiarray on both machines?
>
> Yes.
On Nov 2, 2009, at 11:09 AM, numpy-discussion-requ...@scipy.org wrote:
From: David Cournapeau
Subject: [Numpy-discussion] 1.4.0: Setting a firm release date for 1st
december.
To: Discussion of Numerical Python
Message-ID:
<5b8d13220911020029q1d9f1bd7ia1770e3b93e6e...@mail.gmai
On Mon, Nov 2, 2009 at 9:38 PM, Pauli Virtanen wrote:
>
> Can we get the complex functions to npy_math for 1.4.0: could be useful
> for the next Scipy? This is pretty quick to do, I can just write up some
> more tests one evening and commit.
The idea was partially to set a date to force me putti
On Mon, Nov 2, 2009 at 1:29 AM, David Cournapeau wrote:
> Hi,
>
> I think it is about time to release 1.4.0. Instead of proposing a
> release date, I am setting a firm date for 1st December, and 16th
> november to freeze the trunk. If someone wants a different date, you
> have to speak now.
>
> T
2009/11/1 Thomas Robitaille :
> Hi,
>
> I'm trying to generate random 64-bit integer values for integers and
> floats using Numpy, within the entire range of valid values for that
> type. To generate random 32-bit floats, I can use:
Others have addressed why this is giving bogus results. But it's
Mon, 02 Nov 2009 17:29:18 +0900, David Cournapeau wrote:
> I think it is about time to release 1.4.0. Instead of proposing a
> release date, I am setting a firm date for 1st December, and 16th
> november to freeze the trunk. If someone wants a different date, you
> have to speak now.
>
> There are
On Mon, Nov 2, 2009 at 3:29 AM, David Cournapeau wrote:
> Hi,
>
> I think it is about time to release 1.4.0. Instead of proposing a
> release date, I am setting a firm date for 1st December, and 16th
> november to freeze the trunk. If someone wants a different date, you
> have to speak now.
>
> Th
Hi,
I think it is about time to release 1.4.0. Instead of proposing a
release date, I am setting a firm date for 1st December, and 16th
november to freeze the trunk. If someone wants a different date, you
have to speak now.
There are a few issues I would like to clear up:
- Documentation for dat
12 matches
Mail list logo
