Re: [Numpy-discussion] 1.7.0 release

2012-11-13 Thread Ondřej Čertík
On Mon, Nov 12, 2012 at 2:27 PM, Ondřej Čertík wrote: [...] > Here is a list of issues that need to be fixed before the release: > > https://github.com/numpy/numpy/issues?milestone=3&state=open > > If anyone wants to help, we just need to get through them and submit a > PR for each, or close it if

Re: [Numpy-discussion] 1.7.0 release

2012-11-13 Thread Charles R Harris
On Tue, Nov 13, 2012 at 9:01 AM, Ondřej Čertík wrote: > On Tue, Nov 13, 2012 at 4:18 AM, Gael Varoquaux > wrote: > > On Mon, Nov 12, 2012 at 02:27:02PM -0800, Ondřej Čertík wrote: > >> I successfully defended my Ph.D. thesis last Thursday, I just need to > >> do some changes to it and submit it a

Re: [Numpy-discussion] 1.7.0 release

2012-11-13 Thread Ondřej Čertík
On Tue, Nov 13, 2012 at 4:18 AM, Gael Varoquaux wrote: > On Mon, Nov 12, 2012 at 02:27:02PM -0800, Ondřej Čertík wrote: >> I successfully defended my Ph.D. thesis last Thursday, I just need to >> do some changes to it and submit it and I am done. > > Yey! Tag and release (the thesis, I mean)! > >

Re: [Numpy-discussion] Numpy's policy for releasing memory

2012-11-13 Thread Charles R Harris
On Tue, Nov 13, 2012 at 2:27 AM, Austin Bingham wrote: > OK, if numpy is just subject to Python's behavior then what I'm seeing > must be due to the vagaries of Python. I've noticed that things like > removing a particular line of code or reordering seemingly unrelated calls > (unrelated to the me

Re: [Numpy-discussion] Numpy's policy for releasing memory

2012-11-13 Thread Nathaniel Smith
On Tue, Nov 13, 2012 at 1:31 PM, Austin Bingham wrote: > I've been using psutil, pmap (linux command), and resource in various > capacities, all on cpython. When I wasn't seeing memory freed when I > expected, I got to wondering if maybe numpy was maintaining pools of buffers > for reuse or someth

Re: [Numpy-discussion] Numpy's policy for releasing memory

2012-11-13 Thread Austin Bingham
I've been using psutil, pmap (linux command), and resource in various capacities, all on cpython. When I wasn't seeing memory freed when I expected, I got to wondering if maybe numpy was maintaining pools of buffers for reuse or something like that. It sounds like that's not the case, though, so I'

Re: [Numpy-discussion] 1.7.0 release

2012-11-13 Thread Gael Varoquaux
On Mon, Nov 12, 2012 at 02:27:02PM -0800, Ondřej Čertík wrote: > I successfully defended my Ph.D. thesis last Thursday, I just need to > do some changes to it and submit it and I am done. Yey! Tag and release (the thesis, I mean)! Congratulation. G PS: It seems to me that it was yesterday that

Re: [Numpy-discussion] Numpy's policy for releasing memory

2012-11-13 Thread Olivier Delalleau
How are you monitoring memory usage? Personally I've been using psutil and it seems to work well, although I've used it only on Windows and not in applications with large numpy arrays, so I can't tell whether it would work you. Also, keep in mind that: - The "auto-delete object when it goes out of

Re: [Numpy-discussion] Do we want scalar casting to behave as it does at the moment?

2012-11-13 Thread Olivier Delalleau
2012/11/12 Matthew Brett > Hi, > > On Mon, Nov 12, 2012 at 8:15 PM, Benjamin Root wrote: > > > > > > On Monday, November 12, 2012, Olivier Delalleau wrote: > >> > >> 2012/11/12 Nathaniel Smith > >>> > >>> On Mon, Nov 12, 2012 at 8:54 PM, Matthew Brett < > matthew.br...@gmail.com> > >>> wrote: >

Re: [Numpy-discussion] Do we want scalar casting to behave as it does at the moment?

2012-11-13 Thread Nathaniel Smith
On Tue, Nov 13, 2012 at 6:13 AM, Benjamin Root wrote: > > On Monday, November 12, 2012, Matthew Brett wrote: >> >> Hi, >> >> On Mon, Nov 12, 2012 at 8:15 PM, Benjamin Root wrote: >> > >> > >> > On Monday, November 12, 2012, Olivier Delalleau wrote: >> >> >> >> 2012/11/12 Nathaniel Smith >> >>> >

Re: [Numpy-discussion] Numpy's policy for releasing memory

2012-11-13 Thread Francesc Alted
On 11/13/12 10:27 AM, Austin Bingham wrote: > OK, if numpy is just subject to Python's behavior then what I'm seeing > must be due to the vagaries of Python. I've noticed that things like > removing a particular line of code or reordering seemingly unrelated > calls (unrelated to the memory issu

Re: [Numpy-discussion] fix random.choice for 1.7?

2012-11-13 Thread Sebastian Berg
On Mon, 2012-11-12 at 22:44 -0500, Alan G Isaac wrote: > On 11/12/2012 8:18 PM, Sebastian Berg wrote: > > I have created a pull request > > > This is still a bit different than I thought you intended. > With `size=None` we don't get an element, > but rather a 0d array. > You are right, it should

Re: [Numpy-discussion] Numpy's policy for releasing memory

2012-11-13 Thread Austin Bingham
OK, if numpy is just subject to Python's behavior then what I'm seeing must be due to the vagaries of Python. I've noticed that things like removing a particular line of code or reordering seemingly unrelated calls (unrelated to the memory issue, that is) can affect when memory is reported as free.

Re: [Numpy-discussion] 1.7.0 release

2012-11-13 Thread Nathaniel Smith
On Mon, Nov 12, 2012 at 11:27 PM, Ondřej Čertík wrote: > I successfully defended my Ph.D. thesis last Thursday, I just need to > do some changes to it and submit it and I am done. Congratulations! ___ NumPy-Discussion mailing list NumPy-Discussion@scipy

Re: [Numpy-discussion] Numpy's policy for releasing memory

2012-11-13 Thread Nathaniel Smith
On Tue, Nov 13, 2012 at 8:26 AM, Austin Bingham wrote: > I'm trying to understand how numpy decides when to release memory and > whether it's possible to exert any control over that. The situation is that > I'm profiling memory usage on a system in which a great deal of the overall > memory is tie