On Thu, Aug 27, 2015 at 11:06 AM, Matthew Brett
wrote:
> Hi,
>
> On Thu, Aug 27, 2015 at 6:23 PM, wrote:
> >
> >
> > On Thu, Aug 27, 2015 at 12:22 PM, Matthew Brett >
> > wrote:
> >>
> >> Hi
> >>
> >> On Thu, Aug 27, 2015 at 5:11 PM, wrote:
> >> >
> >> >
> >> > On Thu, Aug 27, 2015 at 11:04
Hi Sebastian
On 2015-08-27 14:45:50, Sebastian Berg
wrote:
> Agreed. Are not PEP's/NEP's just that (and could possibly be
> formalized more, not sure how much they are in the current
> proposal) in some sense? Since they have a sponsor/author who
> can be said to be assigned to it/responsibl
On Do, 2015-08-27 at 12:34 -0700, Stefan van der Walt wrote:
> On 2015-08-27 11:06:10, Matthew Brett
> wrote:
> > So, in the spirit of fruitful discussion, can I ask what y'all
> > consider to be the current problems with working on numpy (other
> > than the technical ones). What is numpy doi
On Thu, Aug 27, 2015 at 2:06 PM, Matthew Brett
wrote:
> Hi,
>
> On Thu, Aug 27, 2015 at 6:23 PM, wrote:
> >
> >
> > On Thu, Aug 27, 2015 at 12:22 PM, Matthew Brett >
> > wrote:
> >>
> >> Hi
> >>
> >> On Thu, Aug 27, 2015 at 5:11 PM, wrote:
> >> >
> >> >
> >> > On Thu, Aug 27, 2015 at 11:04 A
On 2015-08-27 11:06:10, Matthew Brett
wrote:
> So, in the spirit of fruitful discussion, can I ask what y'all
> consider to be the current problems with working on numpy (other
> than the technical ones). What is numpy doing well, and what
> is it doing badly? What risks do we have to plan f
Hi,
On Thu, Aug 27, 2015 at 6:23 PM, wrote:
>
>
> On Thu, Aug 27, 2015 at 12:22 PM, Matthew Brett
> wrote:
>>
>> Hi
>>
>> On Thu, Aug 27, 2015 at 5:11 PM, wrote:
>> >
>> >
>> > On Thu, Aug 27, 2015 at 11:04 AM, Matthew Brett
>> >
>> > wrote:
>> >>
>> >> Hi,
>> >>
>> >> On Thu, Aug 27, 2015 a
On Do, 2015-08-27 at 17:22 +0100, Matthew Brett wrote:
> Hi
>
> On Thu, Aug 27, 2015 at 5:11 PM, wrote:
> >
> >
> > On Thu, Aug 27, 2015 at 11:04 AM, Matthew Brett
> > wrote:
> >>
> >> Hi,
> >>
> >> On Thu, Aug 27, 2015 at 3:34 PM, wrote:
> >> [snip]
> >> > I don't really see a problem with "
On Thu, Aug 27, 2015 at 12:22 PM, Matthew Brett
wrote:
> Hi
>
> On Thu, Aug 27, 2015 at 5:11 PM, wrote:
> >
> >
> > On Thu, Aug 27, 2015 at 11:04 AM, Matthew Brett >
> > wrote:
> >>
> >> Hi,
> >>
> >> On Thu, Aug 27, 2015 at 3:34 PM, wrote:
> >> [snip]
> >> > I don't really see a problem wit
On Thu, Aug 27, 2015 at 11:04 AM, Matthew Brett
wrote:
> Hi,
>
> On Thu, Aug 27, 2015 at 3:34 PM, wrote:
> [snip]
> > I don't really see a problem with "codifying" the status quo.
>
> That's an excellent point.If we believe that the current situation
> is the best possible, both now and in
Hi
On Thu, Aug 27, 2015 at 5:11 PM, wrote:
>
>
> On Thu, Aug 27, 2015 at 11:04 AM, Matthew Brett
> wrote:
>>
>> Hi,
>>
>> On Thu, Aug 27, 2015 at 3:34 PM, wrote:
>> [snip]
>> > I don't really see a problem with "codifying" the status quo.
>>
>> That's an excellent point.If we believe that
The reason why we don't have that extra slice is because we may not know
ahead of time that we are dealing with a 2D array. It could be a 1D array.
I guess we could use ellipses, but I wanted to make sure that the numpy
devs consider the above to be perfectly valid semantics because it is
entrenche
On Do, 2015-08-27 at 11:15 -0400, Benjamin Root wrote:
> Ok, I just wanted to make sure I understood the issue before going bug
> hunting. Chances are, it has been a bug on our end for a while now.
> Just to make sure, is the following valid?
>
>
> arr = np.zeros((5, 3))
>
> ind = np.array([True
Ok, I just wanted to make sure I understood the issue before going bug
hunting. Chances are, it has been a bug on our end for a while now. Just to
make sure, is the following valid?
arr = np.zeros((5, 3))
ind = np.array([True, True, True, False, True])
arr[ind] # gives a 4x3 result
Running that
Hi,
On Thu, Aug 27, 2015 at 3:43 PM, Bryan Van de Ven wrote:
>
>> On Aug 27, 2015, at 1:57 PM, Matthew Brett wrote:
>>
>> The 'president' idea
>
> ...seems to be predicated on a steady stream of people who: actually want
> job, don't mind campaigning, are willing to accept any and all blame, an
Hi,
On Thu, Aug 27, 2015 at 3:34 PM, wrote:
[snip]
> I don't really see a problem with "codifying" the status quo.
That's an excellent point.If we believe that the current situation
is the best possible, both now and in the future, then codifying the
status quo is an excellent idea.
So, we
On Wed, Aug 26, 2015 at 10:06 AM, Travis Oliphant
wrote:
>
>
> On Wed, Aug 26, 2015 at 1:41 AM, Nathaniel Smith wrote:
>
>> Hi Travis,
>>
>> Thanks for taking the time to write up your thoughts!
>>
>> I have many thoughts in return, but I will try to restrict myself to two
>> main ones :-).
>>
>
On Do, 2015-08-27 at 08:04 -0600, Charles R Harris wrote:
>
>
> On Thu, Aug 27, 2015 at 7:52 AM, Benjamin Root
> wrote:
>
>
> Ok, I tested matplotlib master against numpy master, and there
> were no errors. I did get a bunch of new deprecation warnings
>
> On Aug 27, 2015, at 1:57 PM, Matthew Brett wrote:
>
> The 'president' idea
...seems to be predicated on a steady stream of people who: actually want job,
don't mind campaigning, are willing to accept any and all blame, and have the
technical experience to make "final decisions". As others
On Thu, Aug 27, 2015 at 8:57 AM, Matthew Brett
wrote:
> Hi,
>
> On Thu, Aug 27, 2015 at 12:11 PM, Sebastian Berg
> wrote:
> > On Do, 2015-08-27 at 10:45 +0100, Matthew Brett wrote:
> >> Hi,
> >>
> >> On Thu, Aug 27, 2015 at 10:35 AM, Bryan Van de Ven
> wrote:
> >> >
> >> >> On Aug 27, 2015, at
On Thu, Aug 27, 2015 at 7:52 AM, Benjamin Root wrote:
>
> Ok, I tested matplotlib master against numpy master, and there were no
> errors. I did get a bunch of new deprecation warnings though such as:
>
> "/nas/home/broot/centos6/lib/python2.7/site-packages/matplotlib-1.5.dev1-py2.7-linux-x86_64.
Ok, I tested matplotlib master against numpy master, and there were no
errors. I did get a bunch of new deprecation warnings though such as:
"/nas/home/broot/centos6/lib/python2.7/site-packages/matplotlib-1.5.dev1-py2.7-linux-x86_64.egg/matplotlib/colorbar.py:539:
VisibleDeprecationWarning: boolea
Hi,
On Thu, Aug 27, 2015 at 12:11 PM, Sebastian Berg
wrote:
> On Do, 2015-08-27 at 10:45 +0100, Matthew Brett wrote:
>> Hi,
>>
>> On Thu, Aug 27, 2015 at 10:35 AM, Bryan Van de Ven
>> wrote:
>> >
>> >> On Aug 27, 2015, at 10:22 AM, Matthew Brett
>> >> wrote:
>> >>
>> >> In the case of the 'co
The change also seems to have made datetime64 computations stricter:
>>> np.datetime64('2010') - np.datetime64('2000-01-01')
numpy.timedelta64(3653,'D')
>>> np.datetime64('2010') - np.datetime64('2000-01-01T00:00:00Z')
Traceback (most recent call last):
File "", line 1, in
TypeError: Cannot c
On Thu, Aug 27, 2015 at 12:51 AM Daniel Bliss
wrote:
Can anyone give me some advice for translating this equation into code
> using numpy?
>
> eta(t) = lim(dt -> 0) N(0, 1/sqrt(dt)),
>
> where N(a, b) is a Gaussian random variable of mean a and variance b**2.
>
> This is a heuristic definition of
Daniel Bliss wrote:
> Hi all,
>
> Can anyone give me some advice for translating this equation into code
> using numpy?
>
> eta(t) = lim(dt -> 0) N(0, 1/sqrt(dt)),
>
> where N(a, b) is a Gaussian random variable of mean a and variance b**2.
>
> This is a heuristic definition of a white noise p
On Do, 2015-08-27 at 10:45 +0100, Matthew Brett wrote:
> Hi,
>
> On Thu, Aug 27, 2015 at 10:35 AM, Bryan Van de Ven
> wrote:
> >
> >> On Aug 27, 2015, at 10:22 AM, Matthew Brett
> >> wrote:
> >>
> >> In the case of the 'core' model, we have some compelling testimony
> >> from someone with a gr
Hi again,
The change seems to have possibly unforeseen consequences because some
ufuncs don't declare all possible types, e.g.:
>>> a = np.arange(10, dtype=np.int32)
>>> out = np.zeros_like(a)
>>> np.fabs(a, out=out)
Traceback (most recent call last):
File "", line 1, in
TypeError: ufunc 'fab
Hi,
On Thu, Aug 27, 2015 at 11:05 AM, Nathaniel Smith wrote:
> On Thu, Aug 27, 2015 at 2:16 AM, Matthew Brett
> wrote:
>> So, I speculate, that a good governance model would have:
>>
>> * one 'president' who has to take final responsibility for all decisions;
>> * this president might well have
Hi,
On Thu, Aug 27, 2015 at 11:10 AM, Nathaniel Smith wrote:
> On Thu, Aug 27, 2015 at 1:44 AM, Matthew Brett
> wrote:
>> Hi,
>>
>> On Thu, Aug 27, 2015 at 7:33 AM, Nathaniel Smith wrote:
>>> Hi all,
>>>
>>> Here's a first draft of a governance document for NumPy.
>>
>> Thanks for this.
>>
>>
On Thu, Aug 27, 2015 at 1:44 AM, Matthew Brett wrote:
> Hi,
>
> On Thu, Aug 27, 2015 at 7:33 AM, Nathaniel Smith wrote:
>> Hi all,
>>
>> Here's a first draft of a governance document for NumPy.
>
> Thanks for this.
>
> I wasn't sure from your email whether you were asking for feedback as
> to whe
On Thu, Aug 27, 2015 at 2:16 AM, Matthew Brett wrote:
> So, I speculate, that a good governance model would have:
>
> * one 'president' who has to take final responsibility for all decisions;
> * this president might well have a fixed term, maybe with limits on
> the number of terms they can serve
Hi,
On Thu, Aug 27, 2015 at 10:35 AM, Bryan Van de Ven wrote:
>
>> On Aug 27, 2015, at 10:22 AM, Matthew Brett wrote:
>>
>> In the case of the 'core' model, we have some compelling testimony
>> from someone with a great deal of experience:
>>
>> """
>> Much of this early structure (CVS, web site
> On Aug 27, 2015, at 10:22 AM, Matthew Brett wrote:
>
> In the case of the 'core' model, we have some compelling testimony
> from someone with a great deal of experience:
>
> """
> Much of this early structure (CVS, web site, cabal ["core" group],
> etc.) was copied verbatim by other open sour
Hi,
On Thu, Aug 27, 2015 at 10:15 AM, Bryan Van de Ven wrote:
>
>> On Aug 27, 2015, at 9:36 AM, Matthew Brett wrote:
>>
>>
>> So, in answer to your question, it's difficult to know if a particular
>> governance model is successful. It isn't enough that a project has
>> lasted, or is still acti
On Thu, Aug 27, 2015 at 9:36 AM, Matthew Brett wrote:
> Hi,
>
> On Wed, Aug 26, 2015 at 11:46 PM, Stefan van der Walt
> wrote:
>> Hi Matthew
>>
>> On 2015-08-26 10:50:47, Matthew Brett
>> wrote:
>>> In short, the core structure seems to be characteristically
>>> associated with a conservatism an
> On Aug 27, 2015, at 9:36 AM, Matthew Brett wrote:
>
>
> So, in answer to your question, it's difficult to know if a particular
> governance model is successful. It isn't enough that a project has
> lasted, or is still active, because there are so many factors in play.
> On the other hand,
Hi,
On Thu, Aug 27, 2015 at 7:33 AM, Nathaniel Smith wrote:
> Hi all,
>
> Here's a first draft of a governance document for NumPy.
Thanks for this.
I wasn't sure from your email whether you were asking for feedback as
to whether this was the right governance model?
I mean that - for code - I t
Hi,
On Wed, Aug 26, 2015 at 11:46 PM, Stefan van der Walt
wrote:
> Hi Matthew
>
> On 2015-08-26 10:50:47, Matthew Brett
> wrote:
>> In short, the core structure seems to be characteristically
>> associated with a conservatism and lack of vision that causes
>> the project to stagnate.
>
> Can you
38 matches
Mail list logo
