Hey all, Ondrej has been tied up finishing his PhD for the past several weeks. He is defending his work shortly and should be available to continue to help with the 1.7.0 release around the first of December. He and I have been in contact during this process, and I've been helping where I can. Fortunately, other NumPy developers have been active closing tickets and reviewing pull requests which has helped the process substantially. The release has taken us longer than we expected, but I'm really glad that we've received the bug-reports and issues that we have seen because it will help the 1.7.0 release be a more stable series. Also, the merging of the Trac issues with Git has exposed over-looked problems as well and will hopefully encourage more Git-focused participation by users. We are targeting getting the final release of 1.7.0 out by mid December (based on Ondrej's availability). But, I would like to find out which issues are seen as blockers by people on this list. I think most of the issues that I had as blockers have been resolved. If there are no more remaining blockers, then we may be able to accelerate the final release of 1.7.0 to just after Thanksgiving. Best regards, -Travis
import numpy a=numpy.ndindex() a.next() () a.next() Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/opt/lisa/os/epd-7.1.2/lib/python2.7/site-packages/numpy/lib/index_tricks.py",
Hi, I updated the numpy master and recompiled it. I still have the compilation error I got from Theano. I'll pop up that email thread again to have the history and I made a PR for this. Also, I think I said that numpy.ndindex changed its interface, in the past numpy.ndindex() was valid, not this raise and error: line 577, in next raise StopIteration StopIteration
numpy.__version__ '1.6.1'
The error I have with master: [...] ValueError: __array_interface__ shape must be at least size 1 That is the only stopper I saw, but I didn't followed what was needed for other people. Fred On Tue, Nov 6, 2012 at 2:33 AM, Travis Oliphant <travis@continuum.io> wrote:
Hey all,
Ondrej has been tied up finishing his PhD for the past several weeks. He is defending his work shortly and should be available to continue to help with the 1.7.0 release around the first of December. He and I have been in contact during this process, and I've been helping where I can. Fortunately, other NumPy developers have been active closing tickets and reviewing pull requests which has helped the process substantially.
The release has taken us longer than we expected, but I'm really glad that we've received the bug-reports and issues that we have seen because it will help the 1.7.0 release be a more stable series. Also, the merging of the Trac issues with Git has exposed over-looked problems as well and will hopefully encourage more Git-focused participation by users.
We are targeting getting the final release of 1.7.0 out by mid December (based on Ondrej's availability). But, I would like to find out which issues are seen as blockers by people on this list. I think most of the issues that I had as blockers have been resolved. If there are no more remaining blockers, then we may be able to accelerate the final release of 1.7.0 to just after Thanksgiving.
Best regards,
-Travis
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
On Tue, Nov 6, 2012 at 8:33 AM, Travis Oliphant <travis@continuum.io> wrote:
Hey all,
Ondrej has been tied up finishing his PhD for the past several weeks. He is defending his work shortly and should be available to continue to help with the 1.7.0 release around the first of December. He and I have been in contact during this process, and I've been helping where I can. Fortunately, other NumPy developers have been active closing tickets and reviewing pull requests which has helped the process substantially.
The release has taken us longer than we expected, but I'm really glad that we've received the bug-reports and issues that we have seen because it will help the 1.7.0 release be a more stable series. Also, the merging of the Trac issues with Git has exposed over-looked problems as well and will hopefully encourage more Git-focused participation by users.
We are targeting getting the final release of 1.7.0 out by mid December (based on Ondrej's availability). But, I would like to find out which issues are seen as blockers by people on this list. I think most of the issues that I had as blockers have been resolved. If there are no more remaining blockers, then we may be able to accelerate the final release of 1.7.0 to just after Thanksgiving.
Still the same ones I brought up last time (datetime + MinGW & segfault on SPARC): http://thread.gmane.org/gmane.comp.python.numeric.general/50907/focus=50944 There are some more issues listed at https://github.com/numpy/numpy/issues?labels=&milestone=3&page=1&state=open. Most of the Debian issues have disappeared, but there's some work left to do there. A Python 3.3 Windows binary would also be nice to have. Ralf
Hi, On Mon, Nov 5, 2012 at 11:33 PM, Travis Oliphant <travis@continuum.io> wrote:
Hey all,
Ondrej has been tied up finishing his PhD for the past several weeks. He is defending his work shortly and should be available to continue to help with the 1.7.0 release around the first of December. He and I have been in contact during this process, and I've been helping where I can. Fortunately, other NumPy developers have been active closing tickets and reviewing pull requests which has helped the process substantially.
The release has taken us longer than we expected, but I'm really glad that we've received the bug-reports and issues that we have seen because it will help the 1.7.0 release be a more stable series. Also, the merging of the Trac issues with Git has exposed over-looked problems as well and will hopefully encourage more Git-focused participation by users.
We are targeting getting the final release of 1.7.0 out by mid December (based on Ondrej's availability). But, I would like to find out which issues are seen as blockers by people on this list. I think most of the issues that I had as blockers have been resolved. If there are no more remaining blockers, then we may be able to accelerate the final release of 1.7.0 to just after Thanksgiving.
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. So I started to work on the release again (my apologies that it got delayed, I had to devote my full attention to finishing my school first). 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 it doesn't apply anymore. This is what I am doing now. Ondrej
On Mon, Nov 12, 2012 at 10:27 PM, Ondřej Čertík <ondrej.certik@gmail.com> wrote:
Hi,
On Mon, Nov 5, 2012 at 11:33 PM, Travis Oliphant <travis@continuum.io> wrote:
Hey all,
Ondrej has been tied up finishing his PhD for the past several weeks. He is defending his work shortly and should be available to continue to help with the 1.7.0 release around the first of December. He and I have been in contact during this process, and I've been helping where I can. Fortunately, other NumPy developers have been active closing tickets and reviewing pull requests which has helped the process substantially.
The release has taken us longer than we expected, but I'm really glad that we've received the bug-reports and issues that we have seen because it will help the 1.7.0 release be a more stable series. Also, the merging of the Trac issues with Git has exposed over-looked problems as well and will hopefully encourage more Git-focused participation by users.
We are targeting getting the final release of 1.7.0 out by mid December (based on Ondrej's availability). But, I would like to find out which issues are seen as blockers by people on this list. I think most of the issues that I had as blockers have been resolved. If there are no more remaining blockers, then we may be able to accelerate the final release of 1.7.0 to just after Thanksgiving.
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.
Congrats, (almost) Dr. Čertík :) cheers, David
On Mon, Nov 12, 2012 at 3:27 PM, Ondřej Čertík <ondrej.certik@gmail.com>wrote:
Hi,
Hey all,
Ondrej has been tied up finishing his PhD for the past several weeks. He is defending his work shortly and should be available to continue to help with the 1.7.0 release around the first of December. He and I have been in contact during this process, and I've been helping where I can. Fortunately, other NumPy developers have been active closing tickets and reviewing pull requests which has helped the process substantially.
The release has taken us longer than we expected, but I'm really glad
On Mon, Nov 5, 2012 at 11:33 PM, Travis Oliphant <travis@continuum.io> wrote: that we've received the bug-reports and issues that we have seen because it will help the 1.7.0 release be a more stable series. Also, the merging of the Trac issues with Git has exposed over-looked problems as well and will hopefully encourage more Git-focused participation by users.
We are targeting getting the final release of 1.7.0 out by mid December
(based on Ondrej's availability). But, I would like to find out which issues are seen as blockers by people on this list. I think most of the issues that I had as blockers have been resolved. If there are no more remaining blockers, then we may be able to accelerate the final release of 1.7.0 to just after Thanksgiving.
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. So I started to work on the release again (my apologies that it got delayed, I had to devote my full attention to finishing my school first).
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 it doesn't apply anymore. This is what I am doing now.
Concrats. There are some commits already due for backports. Do you want to do that, or will it be OK for others to do it? Another possibility would be to open new PR's for the backports and tag them as 1.7.0. Chuck
On Mon, Nov 12, 2012 at 3:47 PM, Charles R Harris <charlesr.harris@gmail.com> wrote:
On Mon, Nov 12, 2012 at 3:27 PM, Ondřej Čertík <ondrej.certik@gmail.com> wrote:
Hi,
On Mon, Nov 5, 2012 at 11:33 PM, Travis Oliphant <travis@continuum.io> wrote:
Hey all,
Ondrej has been tied up finishing his PhD for the past several weeks. He is defending his work shortly and should be available to continue to help with the 1.7.0 release around the first of December. He and I have been in contact during this process, and I've been helping where I can. Fortunately, other NumPy developers have been active closing tickets and reviewing pull requests which has helped the process substantially.
The release has taken us longer than we expected, but I'm really glad that we've received the bug-reports and issues that we have seen because it will help the 1.7.0 release be a more stable series. Also, the merging of the Trac issues with Git has exposed over-looked problems as well and will hopefully encourage more Git-focused participation by users.
We are targeting getting the final release of 1.7.0 out by mid December (based on Ondrej's availability). But, I would like to find out which issues are seen as blockers by people on this list. I think most of the issues that I had as blockers have been resolved. If there are no more remaining blockers, then we may be able to accelerate the final release of 1.7.0 to just after Thanksgiving.
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. So I started to work on the release again (my apologies that it got delayed, I had to devote my full attention to finishing my school first).
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 it doesn't apply anymore. This is what I am doing now.
Concrats. There are some commits already due for backports. Do you want to do that, or will it be OK for others to do it? Another possibility would be to open new PR's for the backports and tag them as 1.7.0.
I'll be happy to do that. If you know which commits are those, let me know. I actually like to open a PR just for the backports as well, to see if tests pass and to have more eyes look on it to minimize mistakes. Ondrej
Congratulation. ________________________________________ De : numpy-discussion-bounces@scipy.org [numpy-discussion-bounces@scipy.org] de la part de Ondřej Čertík [ondrej.certik@gmail.com] Date d'envoi : 12 novembre 2012 17:27 À : Discussion of Numerical Python Objet : Re: [Numpy-discussion] 1.7.0 release Hi, On Mon, Nov 5, 2012 at 11:33 PM, Travis Oliphant <travis@continuum.io> wrote:
Hey all,
Ondrej has been tied up finishing his PhD for the past several weeks. He is defending his work shortly and should be available to continue to help with the 1.7.0 release around the first of December. He and I have been in contact during this process, and I've been helping where I can. Fortunately, other NumPy developers have been active closing tickets and reviewing pull requests which has helped the process substantially.
The release has taken us longer than we expected, but I'm really glad that we've received the bug-reports and issues that we have seen because it will help the 1.7.0 release be a more stable series. Also, the merging of the Trac issues with Git has exposed over-looked problems as well and will hopefully encourage more Git-focused participation by users.
We are targeting getting the final release of 1.7.0 out by mid December (based on Ondrej's availability). But, I would like to find out which issues are seen as blockers by people on this list. I think most of the issues that I had as blockers have been resolved. If there are no more remaining blockers, then we may be able to accelerate the final release of 1.7.0 to just after Thanksgiving.
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. So I started to work on the release again (my apologies that it got delayed, I had to devote my full attention to finishing my school first). 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 it doesn't apply anymore. This is what I am doing now. Ondrej _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
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 you moved to the state. You didn't loose time with your PhD. Very impressive!
On Tue, Nov 13, 2012 at 4:18 AM, Gael Varoquaux <gael.varoquaux@normalesup.org> 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)!
Congratulation.
G
PS: It seems to me that it was yesterday that you moved to the state. You didn't loose time with your PhD. Very impressive!
Thanks everybody. Gael, it feels like yesterday, but it's been 4 years ago. And I had an M.S. degree already from Prague which took 2 years, so the total time is 6, and I had to wait 0.5 years after finishing my M.S. and before coming to the US (paperwork), so this gives 6.5 years since finishing my B.C. degree. The average time for physics Ph.D. seems to be 5.5 years, at least according to [1], so I am 1 year late, but I had to overcome a few bumps along the way --- maybe I'll write a blog post later. Ondrej [1] http://physics.uchicago.edu/prospective/graduate/index.html
On Tue, Nov 13, 2012 at 9:01 AM, Ondřej Čertík <ondrej.certik@gmail.com>wrote:
On Tue, Nov 13, 2012 at 4:18 AM, Gael Varoquaux <gael.varoquaux@normalesup.org> 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)!
Congratulation.
G
PS: It seems to me that it was yesterday that you moved to the state. You didn't loose time with your PhD. Very impressive!
Thanks everybody. Gael, it feels like yesterday, but it's been 4 years ago. And I had an M.S. degree already from Prague which took 2 years, so the total time is 6, and I had to wait 0.5 years after finishing my M.S. and before coming to the US (paperwork), so this gives 6.5 years since finishing my B.C. degree. The average time for physics Ph.D. seems to be 5.5 years, at least according to [1], so I am 1 year late, but I had to overcome a few bumps along the way --- maybe I'll write a blog post later.
When I was at Columbia I think it was more like 7 for experimental physics. But then there were the theoreticians who got by in a year or two with short dissertations, and in later years picked up their Nobel prize... Chuck
On Mon, Nov 12, 2012 at 2:27 PM, Ondřej Čertík <ondrej.certik@gmail.com> 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 it doesn't apply anymore. This is what I am doing now.
Ok, I went over all the issues, closed fixed issues and sent PRs for about 6 issues. Just go to the link above to see them all (or go to issues and click on "NumPy 1.7" milestone) and left comments on most issues. Most of the minor problems are fixed. There are only 3 big issues that need to be fixed so I set them "priority high": https://github.com/numpy/numpy/issues?labels=priority%3A+high&milestone=3&page=1&state=open in particular: https://github.com/numpy/numpy/issues/568 https://github.com/numpy/numpy/issues/2668 https://github.com/numpy/numpy/issues/606 after that I think we should be good to go. If you have some spare cycles, just concentrate on these 3. Ondrej
On Wed, Nov 14, 2012 at 4:24 AM, Ondřej Čertík <ondrej.certik@gmail.com>wrote:
On Mon, Nov 12, 2012 at 2:27 PM, Ondřej Čertík <ondrej.certik@gmail.com> 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 it doesn't apply anymore. This is what I am doing now.
Ok, I went over all the issues, closed fixed issues and sent PRs for about 6 issues. Just go to the link above to see them all (or go to issues and click on "NumPy 1.7" milestone) and left comments on most issues.
Most of the minor problems are fixed. There are only 3 big issues that need to be fixed so I set them "priority high":
https://github.com/numpy/numpy/issues?labels=priority%3A+high&milestone=3&page=1&state=open
in particular:
https://github.com/numpy/numpy/issues/568 https://github.com/numpy/numpy/issues/2668 https://github.com/numpy/numpy/issues/606
after that I think we should be good to go. If you have some spare cycles, just concentrate on these 3.
Ondrej
Hi all, Having looked at the README.txt and INSTALL.txt files on the branch, I see no mention of which Python 3.x versions are supported: https://github.com/numpy/numpy/blob/maintenance/1.7.x/README.txt https://github.com/numpy/numpy/blob/maintenance/1.7.x/INSTALL.txt Is NumPy 1.7 intended to support Python 3.3? My impression from this thread is probably yes: http://mail.scipy.org/pipermail/numpy-discussion/2012-July/063483.html ... http://mail.scipy.org/pipermail/numpy-discussion/2012-August/063597.html If so, then under Windows (32 bit at least) where the Python.org provided Python 3.3 is compiled with MSCV 2010 there are some problems - see: https://github.com/numpy/numpy/pull/2726 Should an issue be filed for this? Thanks, Peter
Hi all,
Having looked at the README.txt and INSTALL.txt files on the branch, I see no mention of which Python 3.x versions are supported:
https://github.com/numpy/numpy/blob/maintenance/1.7.x/README.txt https://github.com/numpy/numpy/blob/maintenance/1.7.x/INSTALL.txt
Is NumPy 1.7 intended to support Python 3.3?
My impression from this thread is probably yes: http://mail.scipy.org/pipermail/numpy-discussion/2012-July/063483.html ... http://mail.scipy.org/pipermail/numpy-discussion/2012-August/063597.html
If so, then under Windows (32 bit at least) where the Python.org provided Python 3.3 is compiled with MSCV 2010 there are some problems - see: https://github.com/numpy/numpy/pull/2726
Thanks Peter for the email, yes I think we should support Python 3.3.
Should an issue be filed for this?
I just did: https://github.com/numpy/numpy/issues/2743 Btw, I also bumbed this issue as priority high: https://github.com/numpy/numpy/issues/2738 Because it segfaults numpy. Ondrej
participants (10)
-
Charles R Harris -
David Cournapeau -
Frédéric Bastien -
Gael Varoquaux -
Nathaniel Smith -
Ondřej Čertík -
Peter Cock -
Ralf Gommers -
Robert Lagacé -
Travis Oliphant