On Tue, Mar 15, 2011 at 12:25 PM, Sebastian Haase wrote:
>
> >
> > Log Message:
> > ---
> > ENH: Add 'subok' parameter to PyArray_NewLikeArray, np.empty_like,
> np.zeros_like, and np.ones_like
> >
> > This way, the sub-type can be avoided if necessary. This helps mitigate,
> > but doesn't
On Tue, Mar 15, 2011 at 3:25 PM, Sebastian Haase wrote:
> On Tue, Mar 15, 2011 at 7:22 PM, wrote:
>> Branch: refs/heads/master
>> Home: https://github.com/numpy/numpy
>>
>> Commit: aada93306acfb4e2eb816faf32652edf8825cf45
>>
>> https://github.com/numpy/numpy/commit/aada93306acfb4e2eb816faf
On Tue, Mar 15, 2011 at 7:22 PM, wrote:
> Branch: refs/heads/master
> Home: https://github.com/numpy/numpy
>
> Commit: aada93306acfb4e2eb816faf32652edf8825cf45
>
> https://github.com/numpy/numpy/commit/aada93306acfb4e2eb816faf32652edf8825cf45
> Author: Mark Wiebe
> Date: 2011-03-15 (Tue,
On Sat, Sep 18, 2010 at 4:02 AM, Fernando Perez wrote:
> On Thu, Sep 16, 2010 at 1:58 AM, Pauli Virtanen wrote:
> >
> >
> > Numpy SVN repository is now frozen, and does not accept new commits.
> > Future development should end up in the Git repository:
> >
> >http://github.com/numpy/numpy
>
>
On Thu, Sep 16, 2010 at 1:58 AM, Pauli Virtanen wrote:
>
>
> Numpy SVN repository is now frozen, and does not accept new commits.
> Future development should end up in the Git repository:
>
> http://github.com/numpy/numpy
Joining my voice to the collective thank you, I figured I'd pass along
s
On Fri, Sep 17, 2010 at 3:49 AM, Charles R Harris
wrote:
> IIRC, Stefan said that the newer version of the buildbot software works with
> GIT.
Looks like the only missing component is a Git Poller, and because
this machine is behind such a scary firewall I'll have to ask the
administrators to hel
On Thu, Sep 16, 2010 at 7:21 PM, David wrote:
> On 09/16/2010 10:30 PM, Pauli Virtanen wrote:
> > Thu, 16 Sep 2010 08:58:46 +, Pauli Virtanen wrote:
> >> The next things on the TODO list:
> >>
> >>- Update any links that point to http://svn.scipy.org/svn/numpy
> >> or talk about SVN.
On 09/16/2010 10:30 PM, Pauli Virtanen wrote:
> Thu, 16 Sep 2010 08:58:46 +, Pauli Virtanen wrote:
>> The next things on the TODO list:
>>
>>- Update any links that point to http://svn.scipy.org/svn/numpy
>> or talk about SVN.
>>
>> E.g. numpy.org needs updating.
>>
>>- Put up
Thu, 16 Sep 2010 08:58:46 +, Pauli Virtanen wrote:
> The next things on the TODO list:
>
> - Update any links that point to http://svn.scipy.org/svn/numpy
> or talk about SVN.
>
> E.g. numpy.org needs updating.
>
> - Put up documentation on how to contribute to Numpy via Git.
>
On Thu, Sep 16, 2010 at 10:58 AM, Pauli Virtanen wrote:
> Numpy SVN repository is now frozen, and does not accept new commits.
> Future development should end up in the Git repository:
>
> http://github.com/numpy/numpy
Beautiful! It now takes mere seconds to clone NumPy (compared to
several m
Dear all,
Numpy SVN repository is now frozen, and does not accept new commits.
Future development should end up in the Git repository:
http://github.com/numpy/numpy
The next things on the TODO list:
- Update any links that point to http://svn.scipy.org/svn/numpy
or talk about SVN.
On Sat, Jul 17, 2010 at 17:06, Charles R Harris
wrote:
> At the moment... Chuck
I can svn up at the moment.
--
Robert Kern
"I have come to believe that the whole world is an enigma, a harmless
enigma that is made terrible by our own mad attempt to interpret it as
though it had an underlying tr
Sat, 17 Jul 2010 16:06:40 -0600, Charles R Harris wrote:
> At the moment... Chuck
Worksforme at the moment.
Pauli
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
At the moment... Chuck
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
On Thu, Jul 8, 2010 at 12:27 PM, Sebastian Haase wrote:
> isn't this related to
> http://projects.scipy.org/numpy/ticket/626
> percentile() and clamp()
>
> which was set to invalid
>
> -Sebastian
The new percentile function has an axis input. I like that.
scipy.stats.scoreatpercentile always work
isn't this related to
http://projects.scipy.org/numpy/ticket/626
percentile() and clamp()
which was set to invalid
-Sebastian
On Sun, May 16, 2010 at 12:11 AM, wrote:
> Author: oliphant
> Date: 2010-05-15 17:11:10 -0500 (Sat, 15 May 2010)
> New Revision: 8413
>
> Modified:
> trunk/numpy/lib
2010/6/6 Stéfan van der Walt
> I guess this changeset is up for discussion, but I'd be very glad if
> we could track the .gitignore. This makes life a lot easier for
> everybody using git-svn.
>
>
Do you really want to see all the various files that I want to ignore? It
bothered me that when I e
On 6 June 2010 22:49, David wrote:
> On 06/07/2010 02:36 PM, Stéfan van der Walt wrote:
>> I guess this changeset is up for discussion, but I'd be very glad if
>> we could track the .gitignore.
>
> I don't think we should. It is easy to set it up by yourself, and it may
> hide things that some peo
On 06/07/2010 02:36 PM, Stéfan van der Walt wrote:
> I guess this changeset is up for discussion, but I'd be very glad if
> we could track the .gitignore.
I don't think we should. It is easy to set it up by yourself, and it may
hide things that some people may want to see - different people may w
I guess this changeset is up for discussion, but I'd be very glad if
we could track the .gitignore. This makes life a lot easier for
everybody using git-svn.
Cheers
Stéfan
On 6 June 2010 20:43, wrote:
> Author: charris
> Date: 2010-06-06 22:43:07 -0500 (Sun, 06 Jun 2010)
> New Revision: 8457
>
On Oct 8, 2009, at 10:01 AM, David Cournapeau wrote:
> On Thu, Oct 8, 2009 at 8:55 PM, Travis Oliphant > wrote:
>>
>> The problem I have with spending time on it though is that there is
>> still
>> more implementation work to finish on the datetime functionality to
>> complete
>> the NEP imp
On Thu, Oct 8, 2009 at 8:55 PM, Travis Oliphant wrote:
>
> The problem I have with spending time on it though is that there is still
> more implementation work to finish on the datetime functionality to complete
> the NEP implementation. Naturally, I'd like to see those improvements
> made fi
On Thu, Oct 8, 2009 at 8:55 PM, Travis Oliphant wrote:
>
> On Oct 7, 2009, at 9:51 PM, David Cournapeau wrote:
>
> On Thu, Oct 8, 2009 at 11:39 AM, Travis Oliphant
> wrote:
>
> I apologize for the mis communication that has occurred here.
>
> No problem
>
> I did not
>
> understand that there w
On Oct 7, 2009, at 9:51 PM, David Cournapeau wrote:
On Thu, Oct 8, 2009 at 11:39 AM, Travis Oliphant > wrote:
I apologize for the mis communication that has occurred here.
No problem
I did not
understand that there was a desire to keep ABI compatibility with
NumPy 1.3
when NumPy 1.4 wa
Stéfan van der Walt wrote:
> We can work on implementing that today.
>
I am working on it ATM - it is taking me longer than expected, though.
David
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/n
2009/10/8 Charles R Harris :
> code generator problem and doesn't call for a jump in major version. We hope
> ;) I think David's hack, which looks to have been committed by Stefan,
> should fix things up.
I accidentally committed some of David's patches, but I reverted them
back out. I think Davi
On Wed, Oct 7, 2009 at 8:39 PM, Travis Oliphant wrote:
>
> On Oct 7, 2009, at 3:06 AM, David Cournapeau wrote:
>
> On Wed, Oct 7, 2009 at 2:31 AM, Charles R Harris
> wrote:
>
>
>
> Looks like a clue ;)
>
>
> Ok, I fixed it here:
>
> http://github.com/cournape/numpy/tree/fix_abi
>
> But that's an
On 10/7/2009 10:57 PM, Robert Kern wrote:
> it's "pimpl"
OK: http://en.wikipedia.org/wiki/Opaque_pointer
Thanks,
Alan Isaac
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
On Wed, Oct 7, 2009 at 21:55, David Cournapeau wrote:
> On Thu, Oct 8, 2009 at 11:51 AM, David Cournapeau wrote:
>
>> I would prefer passing to "numpy 2.0" when we really need to break ABI
>> and API - at that point, I think we should also think hard about
>> changing our structures and all to ma
On Thu, Oct 8, 2009 at 11:51 AM, David Cournapeau wrote:
> I would prefer passing to "numpy 2.0" when we really need to break ABI
> and API - at that point, I think we should also think hard about
> changing our structures and all to make them more robust to those
> changes (using pimp-like strat
On Thu, Oct 8, 2009 at 11:39 AM, Travis Oliphant wrote:
>
> I apologize for the mis communication that has occurred here.
No problem
> I did not
> understand that there was a desire to keep ABI compatibility with NumPy 1.3
> when NumPy 1.4 was released. The datetime merge was made under that
On Oct 7, 2009, at 3:06 AM, David Cournapeau wrote:
On Wed, Oct 7, 2009 at 2:31 AM, Charles R Harris
wrote:
Looks like a clue ;)
Ok, I fixed it here:
http://github.com/cournape/numpy/tree/fix_abi
But that's an ugly hack. I think we should consider rewriting how we
generate the API: inst
On Wed, Oct 7, 2009 at 7:07 AM, Charles R Harris
wrote:
>
>
> On Wed, Oct 7, 2009 at 6:59 AM, Charles R Harris <
> charlesr.har...@gmail.com> wrote:
>
>>
>>
>> On Wed, Oct 7, 2009 at 6:37 AM, David Cournapeau wrote:
>>
>>> On Wed, Oct 7, 2009 at 9:31 PM, Charles R Harris
>>> wrote:
>>> >
>>> >
>>
On Wed, Oct 7, 2009 at 6:59 AM, Charles R Harris
wrote:
>
>
> On Wed, Oct 7, 2009 at 6:37 AM, David Cournapeau wrote:
>
>> On Wed, Oct 7, 2009 at 9:31 PM, Charles R Harris
>> wrote:
>> >
>> >
>> > On Wed, Oct 7, 2009 at 2:06 AM, David Cournapeau
>> wrote:
>> >>
>> >> On Wed, Oct 7, 2009 at 2:31
On Wed, Oct 7, 2009 at 6:37 AM, David Cournapeau wrote:
> On Wed, Oct 7, 2009 at 9:31 PM, Charles R Harris
> wrote:
> >
> >
> > On Wed, Oct 7, 2009 at 2:06 AM, David Cournapeau
> wrote:
> >>
> >> On Wed, Oct 7, 2009 at 2:31 AM, Charles R Harris
> >> wrote:
> >> >
> >> >
> >> > Looks like a clu
On Wed, Oct 7, 2009 at 9:31 PM, Charles R Harris
wrote:
>
>
> On Wed, Oct 7, 2009 at 2:06 AM, David Cournapeau wrote:
>>
>> On Wed, Oct 7, 2009 at 2:31 AM, Charles R Harris
>> wrote:
>> >
>> >
>> > Looks like a clue ;)
>>
>> Ok, I fixed it here:
>>
>> http://github.com/cournape/numpy/tree/fix_ab
On Wed, Oct 7, 2009 at 2:06 AM, David Cournapeau wrote:
> On Wed, Oct 7, 2009 at 2:31 AM, Charles R Harris
> wrote:
> >
> >
> > Looks like a clue ;)
>
> Ok, I fixed it here:
>
> http://github.com/cournape/numpy/tree/fix_abi
>
> But that's an ugly hack. I think we should consider rewriting how we
On Wed, Oct 7, 2009 at 2:31 AM, Charles R Harris
wrote:
>
>
> Looks like a clue ;)
Ok, I fixed it here:
http://github.com/cournape/numpy/tree/fix_abi
But that's an ugly hack. I think we should consider rewriting how we
generate the API: instead of automatically growing the API array of
fptr, we
On Tue, Oct 6, 2009 at 11:14 AM, David Cournapeau wrote:
> On Wed, Oct 7, 2009 at 2:04 AM, Charles R Harris
> wrote:
> >
> >
> > On Tue, Oct 6, 2009 at 10:50 AM, David Cournapeau
> > wrote:
> >>
> >> On Wed, Oct 7, 2009 at 1:36 AM, Charles R Harris
> >> wrote:
> >> >
> >> >
> >> > 2009/10/6 Sté
On 6-Oct-09, at 12:50 PM, David Cournapeau wrote:
> The version itself is fine, but the ABI has been changed in an
> incompatible way: if you have an extension built against say numpy
> 1.2.1, and then use a numpy built from sources after the datetime
> merge, it will segfault right away. It does
On Wed, Oct 7, 2009 at 2:04 AM, Charles R Harris
wrote:
>
>
> On Tue, Oct 6, 2009 at 10:50 AM, David Cournapeau
> wrote:
>>
>> On Wed, Oct 7, 2009 at 1:36 AM, Charles R Harris
>> wrote:
>> >
>> >
>> > 2009/10/6 Stéfan van der Walt
>> >>
>> >> Hi all,
>> >>
>> >> The current SVN HEAD of NumPy is
On Tue, Oct 6, 2009 at 10:50 AM, David Cournapeau wrote:
> On Wed, Oct 7, 2009 at 1:36 AM, Charles R Harris
> wrote:
> >
> >
> > 2009/10/6 Stéfan van der Walt
> >>
> >> Hi all,
> >>
> >> The current SVN HEAD of NumPy is broken and should not be used.
> >> Extensions compiled against this version
On Wed, Oct 7, 2009 at 1:36 AM, Charles R Harris
wrote:
>
>
> 2009/10/6 Stéfan van der Walt
>>
>> Hi all,
>>
>> The current SVN HEAD of NumPy is broken and should not be used.
>> Extensions compiled against this version may (will) segfault.
>>
>
> Can you be more specific? I haven't had any probl
2009/10/6 Charles R Harris :
> 2009/10/6 Stéfan van der Walt
>>
>> Hi all,
>>
>> The current SVN HEAD of NumPy is broken and should not be used.
>> Extensions compiled against this version may (will) segfault.
>>
>
> Can you be more specific? I haven't had any problems running current svn
> with s
2009/10/6 Stéfan van der Walt
> Hi all,
>
> The current SVN HEAD of NumPy is broken and should not be used.
> Extensions compiled against this version may (will) segfault.
>
>
Can you be more specific? I haven't had any problems running current svn
with scipy.
Chuck
_
2009/10/6 Stéfan van der Walt
> Hi all,
>
> The current SVN HEAD of NumPy is broken and should not be used.
> Extensions compiled against this version may (will) segfault.
>
> Travis, if you could have a look at the side-effects caused by r7050,
> that would be great. I meant to figure out what
Hi all,
The current SVN HEAD of NumPy is broken and should not be used.
Extensions compiled against this version may (will) segfault.
Travis, if you could have a look at the side-effects caused by r7050,
that would be great. I meant to figure out what was wrong, but seeing
that this is a 3000 li
On Mar 6, 2009, at 12:46 PM, Charles R Harris wrote:
> On Fri, Mar 6, 2009 at 8:28 AM, Ryan May wrote:
> Hi,
>
> Is anyone getting mails of the SVN commits? I've gotten 1 spam
> message from that list, but no commits.
>
> Ryan
>
> I'm not seeing them either...Chuck
Hey guys, I'm working on th
On Fri, Mar 6, 2009 at 8:28 AM, Ryan May wrote:
> Hi,
>
> Is anyone getting mails of the SVN commits? I've gotten 1 spam message
> from that list, but no commits.
>
> Ryan
>
I'm not seeing them either...Chuck
___
Numpy-discussion mailing list
Numpy-di
Hi,
Is anyone getting mails of the SVN commits? I've gotten 1 spam message from
that list, but no commits.
Ryan
--
Ryan May
Graduate Research Assistant
School of Meteorology
University of Oklahoma
___
Numpy-discussion mailing list
Numpy-discussion@sc
On Thu, Mar 5, 2009 at 1:33 AM, Bruce Southey wrote:
> David Cournapeau wrote:
>> On Thu, Mar 5, 2009 at 12:06 AM, Scott Sinclair
>> wrote:
>>
>>
>>> I had to do a fresh checkout from http://svn.scipy.org/svn/numpy/
>>> (note changed URL).
>>>
>>
>> I did not know we could access svn from scipy.o
David Cournapeau wrote:
> On Thu, Mar 5, 2009 at 12:06 AM, Scott Sinclair
> wrote:
>
>
>> I had to do a fresh checkout from http://svn.scipy.org/svn/numpy/
>> (note changed URL).
>>
>
> I did not know we could access svn from scipy.org. I have alway used
> svn.scipy.org - in which case you
On Thu, Mar 5, 2009 at 12:06 AM, Scott Sinclair
wrote:
> I had to do a fresh checkout from http://svn.scipy.org/svn/numpy/
> (note changed URL).
I did not know we could access svn from scipy.org. I have alway used
svn.scipy.org - in which case you don't need to do anything to go to
the new repo.
> 2009/3/4 David Cournapeau :
> Travis E. Oliphant wrote:
>> Is commit to NumPy SVN still turned off? How do I get a working SVN
>> again?
>
> It is on - I could commit a few things 1-2 hours ago. If you still get
> an administrative error message ("repo is read only ..."), it means you
> are on
On Mar 4, 2009, at 8:37 AM, David Cournapeau wrote:
> Travis E. Oliphant wrote:
>> Is commit to NumPy SVN still turned off? How do I get a working SVN
>> again?
>>
>
> It is on - I could commit a few things 1-2 hours ago. If you still get
> an administrative error message ("repo is read only ...
Travis E. Oliphant wrote:
> Is commit to NumPy SVN still turned off? How do I get a working SVN
> again?
>
It is on - I could commit a few things 1-2 hours ago. If you still get
an administrative error message ("repo is read only ..."), it means you
are on the old repo.
cheers,
David
_
Is commit to NumPy SVN still turned off? How do I get a working SVN
again?
-Travis
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion
On Tue, May 20, 2008 1:36 pm, Jarrod Millman wrote:
> On Mon, May 19, 2008 at 10:29 PM, Pearu Peterson <[EMAIL PROTECTED]>
> wrote:
>> On Tue, May 20, 2008 1:26 am, Robert Kern wrote:
>>> Is this an important bugfix? If not, can you hold off until 1.1.0 is
>>> released?
>>
>> The patch fixes a long
On Tue, May 20, 2008 at 1:00 AM, Pearu Peterson <[EMAIL PROTECTED]> wrote:
> How do you define a critical bug? Critical to whom?
I know that the definition of a "critical bug" is somewhat
ill-defined, but I think that "a long existing and unreported bug"
probably wouldn't fall into the category of
On Mon, May 19, 2008 at 10:29 PM, Pearu Peterson <[EMAIL PROTECTED]> wrote:
> On Tue, May 20, 2008 1:26 am, Robert Kern wrote:
>> Is this an important bugfix? If not, can you hold off until 1.1.0 is
>> released?
>
> The patch fixes a long existing and unreported bug in f2py - I think
> the bug was
On Tue, May 20, 2008 12:03 pm, David Cournapeau wrote:
> Pearu Peterson wrote:
>> f2py changes are never critical to numpy users who do not use f2py.
>>
> No, but they are to scipy users if f2py cannot build scipy.
Well, I know pretty well what f2py features scipy uses and
what could break scipy b
Pearu Peterson wrote:
> f2py changes are never critical to numpy users who do not use f2py.
>
No, but they are to scipy users if f2py cannot build scipy.
> I have stated before that I am not developing numpy.f2py any further.
> This also means that any changes to f2py should be essentially bu
David Cournapeau wrote:
> Pearu Peterson wrote:
>> So I beg to be flexible with f2py related commits for now.
>
> Why not creating a branch for the those changes, and applying only
> critical bug fixes to the trunk ?
How do you define a critical bug? Critical to whom?
f2py changes are never c
Pearu Peterson wrote:
> So I beg to be flexible with f2py related commits for now.
Why not creating a branch for the those changes, and applying only
critical bug fixes to the trunk ?
cheers,
David
___
Numpy-discussion mailing list
Numpy-discussion@s
Stéfan van der Walt wrote:
> Hi Pearu
>
> 2008/5/20 Pearu Peterson <[EMAIL PROTECTED]>:
>> CC: numpy-discussion because of other reactions on the subject.
>>
>> On Tue, May 20, 2008 1:26 am, Robert Kern wrote:
>>> Is this an important bugfix? If not, can you hold off until 1.1.0 is
>>> released?
Hi Pearu
2008/5/20 Pearu Peterson <[EMAIL PROTECTED]>:
> CC: numpy-discussion because of other reactions on the subject.
>
> On Tue, May 20, 2008 1:26 am, Robert Kern wrote:
>> Is this an important bugfix? If not, can you hold off until 1.1.0 is
>> released?
>
> The patch fixes a long existing and
CC: numpy-discussion because of other reactions on the subject.
On Tue, May 20, 2008 1:26 am, Robert Kern wrote:
> Is this an important bugfix? If not, can you hold off until 1.1.0 is
> released?
The patch fixes a long existing and unreported bug in f2py - I think
the bug was introduced when Pyth
67 matches
Mail list logo
