On Wed, Jul 23, 2008 at 8:59 PM, David Cournapeau
<[EMAIL PROTECTED]> wrote:
> Fernando Perez wrote:
>>
>> Very, very useful. Many thanks for this tip, Andrew!
>>
>
> Hi Fernando,
>
>I am still catching up things (have been on holidays for 2 weeks),
> but have you started the INSTALL.txt docum
Fernando Perez wrote:
>
> Very, very useful. Many thanks for this tip, Andrew!
>
Hi Fernando,
I am still catching up things (have been on holidays for 2 weeks),
but have you started the INSTALL.txt document ?
cheers,
David
___
Numpy-discussion
2008/7/24 Neil Crighton <[EMAIL PROTECTED]>:
> Ok, thanks.
>
> I meant the amount of vertical space between lines of text - for
> example, the gaps between parameter values and their description, or
> the large spacing between both lines of text and and the text boxes in
> the examples section. If
On Wed, Jul 23, 2008 at 3:13 PM, Andrew Straw <[EMAIL PROTECTED]> wrote:
> And on a Debian (derivative) system, you can stall those with "apt-get
> build-dep python-numpy". This will only install the build dependencies
> for the version of python-numpy which is listed in your apt
> sources.list, b
On Wed, Jul 23, 2008 at 3:02 PM, Robert Kern <[EMAIL PROTECTED]> wrote:
> On Wed, Jul 23, 2008 at 16:56, Fernando Perez <[EMAIL PROTECTED]> wrote:
>> (which can be a useful guide on other distros). Should we have a
>> stripped-down copy of this doc somewhere in the top-level directory of
>> numpy
Howdy,
On Wed, Jul 23, 2008 at 3:18 PM, Stéfan van der Walt <[EMAIL PROTECTED]> wrote:
> 2008/7/23 Fernando Perez <[EMAIL PROTECTED]>:
> I agree (with your previous e-mail) that it would be good to have some
> documentation, so if you could give me some pointers on *what* to
> document (I haven't
On Wed, Jul 23, 2008 at 17:18, Stéfan van der Walt <[EMAIL PROTECTED]> wrote:
> 2008/7/23 Fernando Perez <[EMAIL PROTECTED]>:
>> I'm just reposting here to see if anyone with a stake in f2py has an
>> opinion/advice on the points below. F2py feels very much in
>> autopilot/drifting into the iceber
2008/7/23 Fernando Perez <[EMAIL PROTECTED]>:
> I'm just reposting here to see if anyone with a stake in f2py has an
> opinion/advice on the points below. F2py feels very much in
> autopilot/drifting into the icebergs mode right now. Is that correct
> assessment?
>
> If there's any guidance on wh
Ok, thanks.
I meant the amount of vertical space between lines of text - for
example, the gaps between parameter values and their description, or
the large spacing between both lines of text and and the text boxes in
the examples section. If other people agree it's a problem, I thought
the spacing
Robert Kern wrote:
> On Wed, Jul 23, 2008 at 16:56, Fernando Perez <[EMAIL PROTECTED]> wrote:
>> Howdy,
>>
>> I was just trying to explain to a new user how to build numpy from
>> source on ubuntu and I realized that there's not much info on this
>> front in the source tree. Scipy has a nice INSTA
On Wed, Jul 23, 2008 at 16:56, Fernando Perez <[EMAIL PROTECTED]> wrote:
> Howdy,
>
> I was just trying to explain to a new user how to build numpy from
> source on ubuntu and I realized that there's not much info on this
> front in the source tree. Scipy has a nice INSTALL.txt that even
> lists t
Howdy,
I was just trying to explain to a new user how to build numpy from
source on ubuntu and I realized that there's not much info on this
front in the source tree. Scipy has a nice INSTALL.txt that even
lists the names of the debian/ubuntu packages needed for the build
(which can be a useful g
Hi all,
I'm just reposting here to see if anyone with a stake in f2py has an
opinion/advice on the points below. F2py feels very much in
autopilot/drifting into the icebergs mode right now. Is that correct
assessment?
If there's any guidance on where to go, I can at least file tickets on
these
On Wed, Jul 23, 2008 at 6:46 AM, David Huard <[EMAIL PROTECTED]> wrote:
> I think we should stick to what has been agreed and announced months ago.
> It's called honouring our commitments and the project's image depends on it.
>
> If the inconvenience of these API changes is worth the trouble, a 1.
Thanks Everyone.
On Mon, Jul 21, 2008 at 6:25 PM, Charles R Harris <[EMAIL PROTECTED]>
wrote:
>
>
> On Mon, Jul 21, 2008 at 3:37 PM, Stéfan van der Walt <[EMAIL PROTECTED]>
> wrote:
>
>> 2008/7/21 Suchindra Sandhu <[EMAIL PROTECTED]>:
>> > Is that the recommended way of checking the type of the a
Stéfan van der Walt wrote:
> Hi all,
>
> Should we document character arrays? Does anybody still use them?
>
> I think their behaviour can largely be duplicated by object arrays.
> They also seem to be broken:
>
x = np.array(['1', '2', '3', '4']).view(np.chararray)
>
x*3
> chararray(
On Wed, Jul 23, 2008 at 9:57 AM, Stéfan van der Walt <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> Should we document character arrays? Does anybody still use them?
>
> I think their behaviour can largely be duplicated by object arrays.
> They also seem to be broken:
FWIW, I've got issues and patches
Hi all,
Should we document character arrays? Does anybody still use them?
I think their behaviour can largely be duplicated by object arrays.
They also seem to be broken:
>>> x = np.array(['1', '2', '3', '4']).view(np.chararray)
>>> x*3
chararray(['111', '222', '333', '444'],
dtype='|S4'
On Wed, Jul 23, 2008 at 9:40 AM, Stéfan van der Walt <[EMAIL PROTECTED]> wrote:
> 2008/7/23 Alan McIntyre <[EMAIL PROTECTED]>:
>> There's a function (_test_unique1d_speed) in numpy/lib/arraysetops.py
>> that looks to me like it should be in a benchmark suite instead of in
>> the library module. Wo
I think we should stick to what has been agreed and announced months ago.
It's called honouring our commitments and the project's image depends on it.
If the inconvenience of these API changes is worth the trouble, a 1.1.2 release
could be considered.
My two cents.
David
2008/7/22 Joe Harringto
2008/7/23 Alan McIntyre <[EMAIL PROTECTED]>:
> There's a function (_test_unique1d_speed) in numpy/lib/arraysetops.py
> that looks to me like it should be in a benchmark suite instead of in
> the library module. Would anyone mind if I moved it to
> numpy/lib/benchmarks?
No, please go ahead.
Cheer
Hi all,
I noticed that subclasses are not represented correctly:
In [8]: np.chararray([1, 2, 3])
Out[8]:
chararray([[['\x03', '', ''],
['\xc0', '\x03', '']]],
dtype='|S1')
Notice how the indentation of the second row is completely wrong.
I tried to fix this in array_repr_builtin (
There's a function (_test_unique1d_speed) in numpy/lib/arraysetops.py
that looks to me like it should be in a benchmark suite instead of in
the library module. Would anyone mind if I moved it to
numpy/lib/benchmarks?
___
Numpy-discussion mailing list
Num
23 matches
Mail list logo
