On Mon, Jul 16, 2012 at 2:01 AM, Travis Oliphant tra...@continuum.iowrote:
On Jul 15, 2012, at 7:08 AM, Ralf Gommers wrote:
On Sun, Jul 15, 2012 at 12:45 AM, Travis Oliphant tra...@continuum.iowrote:
Hey all,
We are nearing a code-freeze for NumPy 1.7. Are there any last-minute
On Mon, Jul 16, 2012 at 3:52 AM, Frédéric Bastien no...@nouiz.org wrote:
Hi,
there is a PR that I think could be merged before the relase:
https://github.com/numpy/numpy/pull/326
It is the addition of the inplace_increment function. It seam good,
but I can't review it enough as it use many
In article 1342393528.28368.3.ca...@esdceeprjpstudent1.mit.edu,
Paul Natsuo Kishimoto m...@paul.kishimoto.name wrote:
On Sat, 2012-07-14 at 17:45 -0500, Travis Oliphant wrote:
Hey all,
We are nearing a code-freeze for NumPy 1.7. Are there any
last-minute changes people are wanting
On Sun, Jul 15, 2012 at 12:45 AM, Travis Oliphant tra...@continuum.iowrote:
Hey all,
We are nearing a code-freeze for NumPy 1.7. Are there any last-minute
changes people are wanting to push into NumPy 1.7? We should discuss them
as soon as possible.
I'm proposing a code-freeze at
On Jul 15, 2012 2:08 PM, Ralf Gommers ralf.gomm...@googlemail.com wrote:
On Sun, Jul 15, 2012 at 12:45 AM, Travis Oliphant tra...@continuum.io
wrote:
Hey all,
We are nearing a code-freeze for NumPy 1.7. Are there any last-minute
changes people are wanting to push into NumPy 1.7? We
On Sun, Jul 15, 2012 at 5:33 PM, Thouis (Ray) Jones tho...@gmail.comwrote:
On Jul 15, 2012 2:08 PM, Ralf Gommers ralf.gomm...@googlemail.com
wrote:
On Sun, Jul 15, 2012 at 12:45 AM, Travis Oliphant tra...@continuum.io
wrote:
Hey all,
We are nearing a code-freeze for NumPy
On Sun, Jul 15, 2012 at 1:08 PM, Ralf Gommers
ralf.gomm...@googlemail.com wrote:
On Sun, Jul 15, 2012 at 12:45 AM, Travis Oliphant tra...@continuum.io
wrote:
Hey all,
We are nearing a code-freeze for NumPy 1.7. Are there any last-minute
changes people are wanting to push into NumPy
On Sun, Jul 15, 2012 at 5:57 PM, Nathaniel Smith n...@pobox.com wrote:
On Sun, Jul 15, 2012 at 1:08 PM, Ralf Gommers
ralf.gomm...@googlemail.com wrote:
On Sun, Jul 15, 2012 at 12:45 AM, Travis Oliphant tra...@continuum.io
wrote:
Hey all,
We are nearing a code-freeze for NumPy
On Sun, Jul 15, 2012 at 10:32 AM, Ralf Gommers
ralf.gomm...@googlemail.comwrote:
On Sun, Jul 15, 2012 at 5:57 PM, Nathaniel Smith n...@pobox.com wrote:
On Sun, Jul 15, 2012 at 1:08 PM, Ralf Gommers
ralf.gomm...@googlemail.com wrote:
On Sun, Jul 15, 2012 at 12:45 AM, Travis Oliphant
On Sun, Jul 15, 2012 at 5:42 PM, Charles R Harris
charlesr.har...@gmail.com wrote:
On Sun, Jul 15, 2012 at 10:32 AM, Ralf Gommers ralf.gomm...@googlemail.com
wrote:
On Sun, Jul 15, 2012 at 5:57 PM, Nathaniel Smith n...@pobox.com wrote:
On Sun, Jul 15, 2012 at 1:08 PM, Ralf Gommers
Nathaniel Smith n...@pobox.com wrote:
What about the tickets still open for 1.7.0
(http://projects.scipy.org/numpy/report/3)? There are a few important ones
left.
These I would consider blockers:
- #2108 Datetime failures with MinGW
I wonder if this might be a blocker: Python-3.3
On Sun, Jul 15, 2012 at 10:56 AM, David Cournapeau courn...@gmail.comwrote:
On Sun, Jul 15, 2012 at 5:42 PM, Charles R Harris
charlesr.har...@gmail.com wrote:
On Sun, Jul 15, 2012 at 10:32 AM, Ralf Gommers
ralf.gomm...@googlemail.com
wrote:
On Sun, Jul 15, 2012 at 5:57 PM,
Just added PR #359. The purpose is to allow the nditer object operand and
iter flags to be set for a ufunc to provide better control over how an
array is iterated over by a ufunc and how the ufunc uses the operands
passed to it. One specific motivation for this is to be able to specify an
input
On Sat, 2012-07-14 at 17:45 -0500, Travis Oliphant wrote:
Hey all,
We are nearing a code-freeze for NumPy 1.7. Are there any
last-minute changes people are wanting to push into NumPy 1.7? We
should discuss them as soon as possible.
I'm proposing a code-freeze at midnight UTC on July
On Jul 15, 2012, at 7:08 AM, Ralf Gommers wrote:
On Sun, Jul 15, 2012 at 12:45 AM, Travis Oliphant tra...@continuum.io wrote:
Hey all,
We are nearing a code-freeze for NumPy 1.7. Are there any last-minute
changes people are wanting to push into NumPy 1.7? We should discuss them
Bump for: https://github.com/numpy/numpy/pull/351
As requested by njsmith, I gave a more detailed explanation and asked
the list for input at:
http://www.mail-archive.com/numpy-discussion@scipy.org/msg38306.html
There was one qualified negative reply and nothing (yet) further. I'd
Hi,
there is a PR that I think could be merged before the relase:
https://github.com/numpy/numpy/pull/326
It is the addition of the inplace_increment function. It seam good,
but I can't review it enough as it use many numpy internal that I
never used or looked at. But the tests seam to cover
This looked like an interesting one for sure. I can't look at the PR right
now for some reason (Github gave me a 500 error). I know there were some
comments, though.
-Travis
On Jul 15, 2012, at 9:52 PM, Frédéric Bastien wrote:
Hi,
there is a PR that I think could be merged before
A very small PR about documentation:
https://github.com/numpy/numpy/pull/332
Fred
On Sat, Jul 14, 2012 at 6:45 PM, Travis Oliphant tra...@continuum.io wrote:
Hey all,
We are nearing a code-freeze for NumPy 1.7. Are there any last-minute
changes people are wanting to push into NumPy 1.7?
Hi,
On Sat, Jul 14, 2012 at 3:45 PM, Travis Oliphant tra...@continuum.io wrote:
Hey all,
We are nearing a code-freeze for NumPy 1.7. Are there any last-minute
changes people are wanting to push into NumPy 1.7? We should discuss them as
soon as possible.
I'm proposing a code-freeze at
On Sat, Jul 14, 2012 at 7:02 PM, Matthew Brett matthew.br...@gmail.comwrote:
Hi,
On Sat, Jul 14, 2012 at 3:45 PM, Travis Oliphant tra...@continuum.io
wrote:
Hey all,
We are nearing a code-freeze for NumPy 1.7. Are there any last-minute
changes people are wanting to push into NumPy
21 matches
Mail list logo
