Sorry, I copy and pasted the wrong example r result - it should be as you say:
r = array([ 1, 1, 1, 48, 68, 1, 75, 1, 1, 115, 1, 95, 1,
1, 1, 1, 1, 1, 1, 28, 1, 68, 1, 1, 28])
The reason for looking for an alternative solution is performance as the sizes
o
On Sat, Feb 11, 2012 at 2:57 PM, mark florisson
wrote:
> On 11 February 2012 21:45, Mark Wiebe wrote:
> > On Sat, Feb 11, 2012 at 3:27 PM, mark florisson <
> markflorisso...@gmail.com>
> > wrote:
> >>
> >> On 11 February 2012 20:31, Charles R Harris
> >> wrote:
> >> > Hi Dag,
> >> >
> >> > This
Hi,
On Sat, Feb 11, 2012 at 10:56 PM, Dinesh B Vadhia wrote:
> **
> Could the following be written without the direct for-loop?
>
> import numpy
> # numpy vector r of any data type and length, eg.
> r = numpy.ones(25, dtype='int')
> # s is a list of values (of any data type), eg.
> s = [47, 27,
On Sat, Feb 11, 2012 at 7:51 PM, Travis Oliphant wrote:
> NumPy 1.7 is due out in the next few weeks.
This depends on whether all the issues regarding the move to gcc 4.x on
Windows will be solved. Right now numpy is not releasable. Either those
issues get solved, or we have to do something abou
On Sat, Feb 11, 2012 at 11:06 PM, Fernando Perez wrote:
> On Sat, Feb 11, 2012 at 11:11 AM, Travis Oliphant
> wrote:
> > I propose to give Francesc Alted commit rights to the NumPy project.
>
> +1.
> I'm only surprised he didn't have them already, given how much he has
> contributed over the ye
On Sat, Feb 11, 2012 at 11:11 AM, Travis Oliphant wrote:
> I propose to give Francesc Alted commit rights to the NumPy project.
I'm only surprised he didn't have them already, given how much he has
contributed over the years! I remember when numpy was reaching 1.0
stage, the insane amount of car
On Sat, Feb 11, 2012 at 9:49 PM, Mark Wiebe wrote:
> On Sat, Feb 11, 2012 at 3:12 PM, Eric Firing wrote:
>>
>> On 02/11/2012 10:44 AM, Travis Oliphant wrote:
>
>
>>
>> > 2) You must be an admin to label an issue (i.e. set it as a bug,
>> > enhancement, or so forth).
>>
>> A third problem is that
On Sat, Feb 11, 2012 at 2:13 PM, Charles R Harris wrote:
>
> On Sat, Feb 11, 2012 at 12:11 PM, Travis Oliphant wrote:
>
>> I propose to give Francesc Alted commit rights to the NumPy project.
>> Francesc will be working full time on NumPy for several months and it will
>> enable him to participat
On 11 February 2012 21:45, Mark Wiebe wrote:
> On Sat, Feb 11, 2012 at 3:27 PM, mark florisson
> wrote:
>>
>> On 11 February 2012 20:31, Charles R Harris
>> wrote:
>> > Hi Dag,
>> >
>> > This probably needs to be on the cython mailing list at some point, but
>> > I
>> > thought I'd start the dis
On Sat, Feb 11, 2012 at 3:12 PM, Eric Firing wrote:
> On 02/11/2012 10:44 AM, Travis Oliphant wrote:
>
> > 2) You must be an admin to label an issue (i.e. set it as a bug,
> > enhancement, or so forth).
>
> A third problem is that the entire style of presentation is poorly
> designed from a use
On Sat, Feb 11, 2012 at 3:27 PM, mark florisson
wrote:
> On 11 February 2012 20:31, Charles R Harris
> wrote:
> > Hi Dag,
> >
> > This probably needs to be on the cython mailing list at some point, but I
> > thought I'd start the discussion here. Numpy is going to begin
> deprecating
> > direct a
On 2/11/12 3:12 PM, Eric Firing wrote:
> A third problem is that the entire style of presentation is poorly
> designed from a use standpoint, in comparison to the sourceforge tracker
> which mpl used previously. The github tracker appears to have been
> designed by a graphics person, not a softwar
On 11 February 2012 20:31, Charles R Harris wrote:
> Hi Dag,
>
> This probably needs to be on the cython mailing list at some point, but I
> thought I'd start the discussion here. Numpy is going to begin deprecating
> direct access to ndarray/dtype internals, ala arr->data etc. There are
> current
On 02/11/2012 10:44 AM, Travis Oliphant wrote:
> This is good feedback.
>
> It looks like there are 2 concerns:
>
> 1) no way to add attachments --- it would seem that gists and indeed
> other github repos solves that problem.
Not really, in practice. Yes one can use these mechanisms, but they ar
11.02.2012 22:02, Jason Grout kirjoitti:
[clip]
> Are there any good github trac plugins? For example:
>
> http://davglass.lighthouseapp.com/projects/21212/home
>
> http://trac-hacks.org/wiki/GitPlugin (git, not github, but still maybe
> useful)
The Numpy & Scipy Trac is currently running on t
I think that migration will require some amount of manual intervention, and
that this is a perfect opportunity to review the issues which can be part of
the NumPy 1.8 work-load.
There is an intern I am working with who is looking for something more
substantial to do, and this would also be a
On 2/11/12 1:44 PM, Travis Oliphant wrote:
> How to people feel about moving the issue tracking for NumPy to Github?
> It looks like they have improved their issue tracking quite a bit and
> the workflow and integration with commits looks quite good from what I
> can see.
>
> Here is one tool I saw
Could the following be written without the direct for-loop?
import numpy
# numpy vector r of any data type and length, eg.
r = numpy.ones(25, dtype='int')
# s is a list of values (of any data type), eg.
s = [47, 27, 67]
# c is a list of (variable length) lists where the sub-list elements are inde
On Sat, Feb 11, 2012 at 12:36 PM, Pauli Virtanen wrote:
> The lack of attachments is the main problem with this transition. It's
> not so seldom that numerical input data or scripts demonstrating an
> issue come useful. This is probably less of an issue for Numpy than for
> Scipy, though.
We've t
On Sat, Feb 11, 2012 at 1:44 PM, Travis Oliphant wrote:
> This is good feedback.
>
> It looks like there are 2 concerns:
>
> 1) no way to add attachments --- it would seem that gists and indeed other
> github repos solves that problem.
> 2) You must be an admin to label an issue (i.e. set it as a
This is good feedback.
It looks like there are 2 concerns:
1) no way to add attachments --- it would seem that gists and indeed
other github repos solves that problem.
2) You must be an admin to label an issue (i.e. set it as a bug,
enhancement, or so forth).
This second co
11.02.2012 20:44, Travis Oliphant kirjoitti:
> How to people feel about moving the issue tracking for NumPy to Github?
>It looks like they have improved their issue tracking quite a bit and
> the workflow and integration with commits looks quite good from what I
> can see.
The lack of attachm
Hi Dag,
This probably needs to be on the cython mailing list at some point, but I
thought I'd start the discussion here. Numpy is going to begin deprecating
direct access to ndarray/dtype internals, ala arr->data etc. There are
currently macros/functions for many of these operations in the numpy
d
On Sat, Feb 11, 2012 at 12:11 PM, Travis Oliphant wrote:
> I propose to give Francesc Alted commit rights to the NumPy project.
> Francesc will be working full time on NumPy for several months and it will
> enable him to participate in pull requests.
>
> Francesc Alted has been very active in the
On Saturday, February 11, 2012, Travis Oliphant wrote:
> How to people feel about moving the issue tracking for NumPy to Github?
It looks like they have improved their issue tracking quite a bit and the
workflow and integration with commits looks quite good from what I can see.
> Here is one tool
How to people feel about moving the issue tracking for NumPy to Github?It
looks like they have improved their issue tracking quite a bit and the workflow
and integration with commits looks quite good from what I can see.
Here is one tool I saw that might help in the migration:
https://g
I propose to give Francesc Alted commit rights to the NumPy project. Francesc
will be working full time on NumPy for several months and it will enable him to
participate in pull requests.
Francesc Alted has been very active in the larger Python for Science community
and has written PyTable
NumPy 1.7 is due out in the next few weeks. This will obviously support 2.4.
It can be used for as long as people want.
Right now, there is a plan for NumPy 1.8 to be released in the summer which
will have much attention paid to it in order to improve the documentation, add
bug-fixes, as w
On Sat, Feb 11, 2012 at 4:08 PM, David Cournapeau wrote:
> On Sat, Feb 11, 2012 at 1:30 PM, Ralf Gommers
> wrote:
> >
> >
> > As Bruce said, 29 Feb 2012 and not 2014:
> > https://access.redhat.com/support/policy/updates/errata/
>
> I think Bruce and me were not talking about the same RHEL version
On Sat, Feb 11, 2012 at 1:30 PM, Ralf Gommers
wrote:
>
>
> As Bruce said, 29 Feb 2012 and not 2014:
> https://access.redhat.com/support/policy/updates/errata/
I think Bruce and me were not talking about the same RHEL version (4 vs 5).
Let me see if I can set up a buildbot for 2.4.
David
___
On 2/10/2012 8:53 AM, Francesc Alted wrote:
> On Feb 10, 2012, at 4:50 PM, Francesc Alted wrote:
>
>> https://github.com/FrancescAlted/carry
>
> Hmm, this should be:
>
> https://github.com/FrancescAlted/carray
>
> Blame my (too) smart spell corrector.
>
> -- Francesc Alted
Thank you, Frances
On Sat, Feb 11, 2012 at 12:05 PM, David Cournapeau wrote:
> On Sat, Feb 11, 2012 at 9:08 AM, Ralf Gommers
> wrote:
> >
> >
> > On Fri, Feb 10, 2012 at 8:51 PM, Ralf Gommers <
> ralf.gomm...@googlemail.com>
> > wrote:
> >>
> >>
> >>
> >> On Fri, Feb 10, 2012 at 10:25 AM, David Cournapeau
> >> wro
On Sat, Feb 11, 2012 at 9:08 AM, Ralf Gommers
wrote:
>
>
> On Fri, Feb 10, 2012 at 8:51 PM, Ralf Gommers
> wrote:
>>
>>
>>
>> On Fri, Feb 10, 2012 at 10:25 AM, David Cournapeau
>> wrote:
>>>
>>> On Sun, Feb 5, 2012 at 7:19 AM, Ralf Gommers
>>> wrote:
>>> >
>>> >
>>> > On Sun, Feb 5, 2012 at 7:3
On Fri, Feb 10, 2012 at 8:51 PM, Ralf Gommers
wrote:
>
>
> On Fri, Feb 10, 2012 at 10:25 AM, David Cournapeau wrote:
>
>> On Sun, Feb 5, 2012 at 7:19 AM, Ralf Gommers
>> wrote:
>> >
>> >
>> > On Sun, Feb 5, 2012 at 7:33 AM, Travis Oliphant
>> wrote:
>> >>
>> >> I think supporting Python 2.5 and
34 matches
Mail list logo
