Re: [Numpy-discussion] Status of the 1.7 release
On Sun, Dec 16, 2012 at 3:17 AM, Nathaniel Smith n...@pobox.com wrote: #294 is a regression, so probably should be considered release critical. I can't tell if #2750 is a real problem or not. #378 looks serious, but afaict has actually been fixed even though the bug is still marked open? At least fixed in 1.7.x? On 15 Dec 2012 23:52, Ondřej Čertík ondrej.cer...@gmail.com wrote: Hi, If you go to the issues for 1.7 and click high priority: https://github.com/numpy/numpy/issues?labels=priority%3A+highmilestone=3state=open you will see 3 issues as of right now. Two of those have PR attached. It's been a lot of work to get to this point and I'd like to thank all of you for helping out with the issues. In particular, I have just fixed a very annoying segfault (#2738) in the PR: https://github.com/numpy/numpy/pull/2831 If you can review that one carefully, that would be highly appreciated. The more people the better, it's a reference counting issue and since this would go into the 1.7 release and it's in the core of numpy, I want to make sure that it's correct. So the last high priority issue is: https://github.com/numpy/numpy/issues/568 and that's the one I will be concentrating on now. After it's fixed, I think we are ready to release the rc1. There are more open issues (that are not high priority): https://github.com/numpy/numpy/issues?labels=milestone=3page=1state=open But I don't think we should delay the release any longer because of them. Let me know if there are any objections. Of course, if you attach a PR fixing any of those, we'll merge it. Properly documenting .base (gh-2737) and casting rules (gh-561) changes should be finished before rc1. I agree that the Debian issues all shouldn't block the release. Ralf ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] MKL licenses for core scientific Python projects
All open source software and research projects with numpy in the stack,
including PyClaw and petsc4py.
A
On Saturday, December 15, 2012, Ralf Gommers wrote:
On Sat, Dec 15, 2012 at 2:21 PM, Aron Ahmadia
a...@ahmadia.netjavascript:_e({}, 'cvml', 'a...@ahmadia.net');
wrote:
Ralf,
Does performance testing come under building/testing?
As long as it's for the project(s) that these licenses are for, and not
for your own research. Would this be for PyClaw?
Ralf
If so,
Aron Ahmadia
OS X.8
Thanks,
A
On Sat, Dec 15, 2012 at 8:13 AM, Ralf Gommers
ralf.gomm...@gmail.comjavascript:_e({}, 'cvml', 'ralf.gomm...@gmail.com');
wrote:
On Sat, Dec 15, 2012 at 5:06 AM, Chris Barker - NOAA Federal
chris.bar...@noaa.gov javascript:_e({}, 'cvml',
'chris.bar...@noaa.gov'); wrote:
Ralf,
Do these licenses allow fully free distribution of binaries? And are
those binaries themselves redistributive? I.e. with py2exe and friends?
If so, that could be nice.
Good point. It's not entirely clear from the emails I received. I've
asked for clarification.
Ralf
On Dec 14, 2012, at 1:01 PM, Ralf Gommers
ralf.gomm...@gmail.comjavascript:_e({}, 'cvml',
'ralf.gomm...@gmail.com');
wrote:
Hi all,
Intel has offered to provide free MKL licenses for main contributors to
scientific Python projects - at least those listed at
numfocus.org/projects/. Licenses for all OSes that are required can be
provided, the condition is that they're used for building/testing our
projects and not for broader purposes.
If you're interested, please let me know your full name and what OS you
need a license for.
Cheers,
Ralf
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org javascript:_e({}, 'cvml',
'NumPy-Discussion@scipy.org');
http://mail.scipy.org/mailman/listinfo/numpy-discussion
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org javascript:_e({}, 'cvml',
'NumPy-Discussion@scipy.org');
http://mail.scipy.org/mailman/listinfo/numpy-discussion
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org javascript:_e({}, 'cvml',
'NumPy-Discussion@scipy.org');
http://mail.scipy.org/mailman/listinfo/numpy-discussion
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org javascript:_e({}, 'cvml',
'NumPy-Discussion@scipy.org');
http://mail.scipy.org/mailman/listinfo/numpy-discussion
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] www.numpy.org home page
On Thu, Dec 13, 2012 at 5:35 PM, Travis Oliphant teoliph...@gmail.comwrote: For people interested in the www.numpy.org home page: Jon Turner has officially transferred the www.numpy.org domain to NumFOCUS. Thank you, Jon for this donation and for being a care-taker of the domain-name. We have setup the domain registration to point to numpy.github.com and I've changed the CNAME in that repostiory to www.numpy.org I've sent an email to have the numpy.scipy.org page to redirect to www.numpy.org. The NumPy home page can still be edited in this repository: g...@github.com:numpy/numpy.org.git. Pull requests are always welcome --- especially pull requests that improve the look and feel of the web-page. Two of the content changes that we need to make a decision about is 1) whether or not to put links to books published (Packt publishing for example has offered a higher percentage of their revenues if we put a prominent link on www.numpy.org) I'm +1 on showing links to books in a sidebar on the main page and/or on the documentation page, provided that (a) someone in this community can vouch for the quality of the book, and (b) we accept links for all books that are relevant and of sufficient quality. 2) whether or not to accept Sponsored by links on the home page for donations to the project (e.g. Continuum Analytics has sponsored Ondrej release management, other companies have sponsored pull requests, other companies may want to provide donations and we would want to recognize their contributions to the numpy project). +1 for putting this on the main page. Something like the Support section on the IPython main page would be good. It lists specifically what the support was for. These decisions should be made by the NumPy community which in my mind are interested people on this list. Who is interested in this kind of discussion? We could have these discussions on this list or on the numfo...@googlegroups.com list and keep this list completely technical (which I prefer, but I will do whatever the consensus is). I'd prefer things that are cross-project to move to the numfocus list, but things that are specifically about NumPy (which numpy.org content is) to stay on this list. Ralf ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] www.numpy.org home page
On Sun, Dec 16, 2012 at 2:38 PM, Ralf Gommers ralf.gomm...@gmail.comwrote: On Thu, Dec 13, 2012 at 5:35 PM, Travis Oliphant teoliph...@gmail.comwrote: For people interested in the www.numpy.org home page: Jon Turner has officially transferred the www.numpy.org domain to NumFOCUS. Thank you, Jon for this donation and for being a care-taker of the domain-name. We have setup the domain registration to point to numpy.github.com and I've changed the CNAME in that repostiory to www.numpy.org I've sent an email to have the numpy.scipy.org page to redirect to www.numpy.org. The NumPy home page can still be edited in this repository: g...@github.com:numpy/numpy.org.git. Pull requests are always welcome --- especially pull requests that improve the look and feel of the web-page. Two of the content changes that we need to make a decision about is 1) whether or not to put links to books published (Packt publishing for example has offered a higher percentage of their revenues if we put a prominent link on www.numpy.org) I'm +1 on showing links to books in a sidebar on the main page and/or on the documentation page, provided that (a) someone in this community can vouch for the quality of the book, and (b) we accept links for all books that are relevant and of sufficient quality. Does anyone have an informed opinion on the quality of these books: NumPy 1.5 Beginner's Guide, Ivan Idris, http://www.packtpub.com/numpy-1-5-using-real-world-examples-beginners-guide/book NumPy Cookbook, Ivan Idris, http://www.packtpub.com/numpy-for-python-cookbook/book Python for Data Analysis, Wes McKinney, http://shop.oreilly.com/product/0636920023784.do SciPy and NumPy, Eli Bressert, http://shop.oreilly.com/product/0636920020219.do The first 5 books at http://stackoverflow.com/questions/4375094/numpy-what-are-the-authoritative-numpy-resources-e-g-documentation-tutorial Are there any more I missed? Ralf 2) whether or not to accept Sponsored by links on the home page for donations to the project (e.g. Continuum Analytics has sponsored Ondrej release management, other companies have sponsored pull requests, other companies may want to provide donations and we would want to recognize their contributions to the numpy project). +1 for putting this on the main page. Something like the Support section on the IPython main page would be good. It lists specifically what the support was for. These decisions should be made by the NumPy community which in my mind are interested people on this list. Who is interested in this kind of discussion? We could have these discussions on this list or on the numfo...@googlegroups.com list and keep this list completely technical (which I prefer, but I will do whatever the consensus is). I'd prefer things that are cross-project to move to the numfocus list, but things that are specifically about NumPy (which numpy.org content is) to stay on this list. Ralf ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] www.numpy.org home page
Does anyone have an informed opinion on the quality of these books: NumPy 1.5 Beginner's Guide, Ivan Idris, http://www.packtpub.com/numpy-1-5-using-real-world-examples-beginners-guide/book NumPy Cookbook, Ivan Idris, http://www.packtpub.com/numpy-for-python-cookbook/book Packt is looking for reviewers for this (new) book. I will do one in the next few weeks. Cheers, -- Information System Engineer, Ph.D. Blog: http://matt.eifelle.com LinkedIn: http://www.linkedin.com/in/matthieubrucher Music band: http://liliejay.com/ ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] www.numpy.org home page
On 16 Dec 2012 13:38, Ralf Gommers ralf.gomm...@gmail.com wrote: On Thu, Dec 13, 2012 at 5:35 PM, Travis Oliphant teoliph...@gmail.com wrote: For people interested in the www.numpy.org home page: Jon Turner has officially transferred the www.numpy.org domain to NumFOCUS. Thank you, Jon for this donation and for being a care-taker of the domain-name. We have setup the domain registration to point to numpy.github.com and I've changed the CNAME in that repostiory to www.numpy.org I've sent an email to have the numpy.scipy.org page to redirect to www.numpy.org. The NumPy home page can still be edited in this repository: g...@github.com:numpy/numpy.org.git. Pull requests are always welcome --- especially pull requests that improve the look and feel of the web-page. Two of the content changes that we need to make a decision about is 1) whether or not to put links to books published (Packt publishing for example has offered a higher percentage of their revenues if we put a prominent link on www.numpy.org) I'm +1 on showing links to books in a sidebar on the main page and/or on the documentation page, provided that (a) someone in this community can vouch for the quality of the book, and (b) we accept links for all books that are relevant and of sufficient quality. I agree, so long as we're careful to avoid all the huge drama that could arise from trying to come up with official community judgements on the quality of books produced by members of our community. In practice I guess this means that we err on the side of inclusion, where all a book would need is one person who likes it, with no voting or vetoes possible. But that seems like a fine system - there are plenty of places to get more fine-gained recommendations. 2) whether or not to accept Sponsored by links on the home page for donations to the project (e.g. Continuum Analytics has sponsored Ondrej release management, other companies have sponsored pull requests, other companies may want to provide donations and we would want to recognize their contributions to the numpy project). +1 for putting this on the main page. Something like the Support section on the IPython main page would be good. It lists specifically what the support was for. These decisions should be made by the NumPy community which in my mind are interested people on this list. Who is interested in this kind of discussion? We could have these discussions on this list or on the numfo...@googlegroups.com list and keep this list completely technical (which I prefer, but I will do whatever the consensus is). I'd prefer things that are cross-project to move to the numfocus list, but things that are specifically about NumPy (which numpy.org content is) to stay on this list. +1 -n ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] www.numpy.org home page
On Sun, 16 Dec 2012 14:52:28 +0100, Ralf Gommers ralf.gomm...@gmail.com wrote: Does anyone have an informed opinion on the quality of these books: NumPy 1.5 Beginner's Guide, Ivan Idris, http://www.packtpub.com/numpy-1-5-using-real-world-examples-beginners-guide/book NumPy Cookbook, Ivan Idris, http://www.packtpub.com/numpy-for-python-cookbook/book Some reviews on first title: http://gael-varoquaux.info/blog/?p=161 http://glowingpython.blogspot.com/2011/12/book-review-numpy-15-beginners-guide.html Gael noted http://scipy-lectures.github.com/ which IMHO could be more promoted. Same for Travis' free Numpy book. The second title is very fresh, I don't know if anyone did review, but seems like good companion. Python for Data Analysis, Wes McKinney, http://shop.oreilly.com/product/0636920023784.do This is already allover pandas, and although there is introduction to numpy, it's more focused on pandas data object model then numpy arrays, logically. SciPy and NumPy, Eli Bressert, http://shop.oreilly.com/product/0636920020219.do This is very short introductory course to numpy and scipy in 40 pages and next 10 pages about scikit.learn and scikit.image The first 5 books at http://stackoverflow.com/questions/4375094/numpy-what-are-the-authoritative-numpy-resources-e-g-documentation-tutorial Voted answer contains great suggestions. All those books are very good companions, especially those Springer published. ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Support for python 2.4 dropped. Should we drop 2.5 also?
On Thu, Dec 13, 2012 at 10:38 AM, Charles R Harris charlesr.har...@gmail.com wrote: The previous proposal to drop python 2.4 support garnered no opposition. How about dropping support for python 2.5 also? The proposal to drop support for python 2.5 and 2.4 in numpy 1.8 has carried. It is now a todo issue on githubhttps://github.com/numpy/numpy/issues/2830 . ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] required nose version.
Hi All, Looking at INSTALL.txt with an eye to updating it since we have dropped Python 2.4 -2.5 support, it looks like we could update the nose version also. The first version of nose to support Python 3 was 1.0, but I think 1.1 would better because of some bug fixes. IPython also requires nose 1.1. So I propose the required nose version be updated to 1.1. Thoughts? ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Status of the 1.7 release
Thanks Ralf and Nathan, I have put high priority on the issues that need to be fixed before the rc1. There are now 4 issues: https://github.com/numpy/numpy/issues?labels=priority%3A+highmilestone=3page=1state=open I am working on the mingw one, as that one is the most difficult. Ralf (or anyone else), do you know how to fix this one: https://github.com/numpy/numpy/issues/438 I am not very familiar with this part of numpy, so maybe you know how to document it well. The sooner we can fix these 4 issues, the sooner we can release. Ondrej On Sun, Dec 16, 2012 at 1:49 AM, Ralf Gommers ralf.gomm...@gmail.com wrote: On Sun, Dec 16, 2012 at 3:17 AM, Nathaniel Smith n...@pobox.com wrote: #294 is a regression, so probably should be considered release critical. I can't tell if #2750 is a real problem or not. #378 looks serious, but afaict has actually been fixed even though the bug is still marked open? At least fixed in 1.7.x? On 15 Dec 2012 23:52, Ondřej Čertík ondrej.cer...@gmail.com wrote: Hi, If you go to the issues for 1.7 and click high priority: https://github.com/numpy/numpy/issues?labels=priority%3A+highmilestone=3state=open you will see 3 issues as of right now. Two of those have PR attached. It's been a lot of work to get to this point and I'd like to thank all of you for helping out with the issues. In particular, I have just fixed a very annoying segfault (#2738) in the PR: https://github.com/numpy/numpy/pull/2831 If you can review that one carefully, that would be highly appreciated. The more people the better, it's a reference counting issue and since this would go into the 1.7 release and it's in the core of numpy, I want to make sure that it's correct. So the last high priority issue is: https://github.com/numpy/numpy/issues/568 and that's the one I will be concentrating on now. After it's fixed, I think we are ready to release the rc1. There are more open issues (that are not high priority): https://github.com/numpy/numpy/issues?labels=milestone=3page=1state=open But I don't think we should delay the release any longer because of them. Let me know if there are any objections. Of course, if you attach a PR fixing any of those, we'll merge it. Properly documenting .base (gh-2737) and casting rules (gh-561) changes should be finished before rc1. I agree that the Debian issues all shouldn't block the release. Ralf ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Status of the 1.7 release
On Sun, Dec 16, 2012 at 3:50 PM, Ondřej Čertík ondrej.cer...@gmail.comwrote: Thanks Ralf and Nathan, I have put high priority on the issues that need to be fixed before the rc1. There are now 4 issues: https://github.com/numpy/numpy/issues?labels=priority%3A+highmilestone=3page=1state=open I am working on the mingw one, as that one is the most difficult. Ralf (or anyone else), do you know how to fix this one: https://github.com/numpy/numpy/issues/438 I am not very familiar with this part of numpy, so maybe you know how to document it well. The sooner we can fix these 4 issues, the sooner we can release. I believe mingw was updated last month to a new compiler version. I don't know what other changes there were, but it is possible that some problems have been fixed. snip Chuck ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Status of the 1.7 release
On 16 Dec 2012 23:01, Charles R Harris charlesr.har...@gmail.com wrote: On Sun, Dec 16, 2012 at 3:50 PM, Ondřej Čertík ondrej.cer...@gmail.com wrote: Thanks Ralf and Nathan, I have put high priority on the issues that need to be fixed before the rc1. There are now 4 issues: https://github.com/numpy/numpy/issues?labels=priority%3A+highmilestone=3page=1state=open I am working on the mingw one, as that one is the most difficult. Ralf (or anyone else), do you know how to fix this one: https://github.com/numpy/numpy/issues/438 I am not very familiar with this part of numpy, so maybe you know how to document it well. The sooner we can fix these 4 issues, the sooner we can release. I believe mingw was updated last month to a new compiler version. I don't know what other changes there were, but it is possible that some problems have been fixed. It'd be worth checking in case it allows us to get off the (incredibly old) GCC that we currently require on windows. But that's a long-term problem that we probably shouldn't be messing with for 1.7 purposes. afaict all we need to do for 1.7 is switch to using our current POSIX code on win32 as well, instead of the (weird and broken) MS-specific API that we're currently using. (Plus suppress some totally spurious warnings): http://mail.scipy.org/pipermail/numpy-discussion/2012-July/063346.html (Or I could be missing something, but I don't think any problems with that solution have been discussed on the list anyway.) -n ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] On the difference of two positive definite matrices
Suppose I have two positive definite matrices, A and B. Is it possible to use U*D*U^T factorizations of these matrices to obtain a numerically stable result for their difference, A - B ? My application is the UD factorization method for the Kalman filter followed by the Rauch-Tung-Striebel smoother --- this is where the difference of two positive definite matrices occurs. I hope that this question is appropriate for this list and does not offend any subscribers. ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] On the difference of two positive definite matrices
On Sun, Dec 16, 2012 at 6:20 PM, Virgil Stokes v...@it.uu.se wrote: Suppose I have two positive definite matrices, A and B. Is it possible to use U*D*U^T factorizations of these matrices to obtain a numerically stable result for their difference, A - B ? My application is the UD factorization method for the Kalman filter followed by the Rauch-Tung-Striebel smoother --- this is where the difference of two positive definite matrices occurs. I hope that this question is appropriate for this list and does not offend any subscribers. Not sure what you are asking, but there is a coordinate system in which they are both diagonal. Nevertheless, the difference may not be positive definite. Chuck ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] DARPA funding for Blaze and passing the NumPy torch
Hello all, There is a lot happening in my life right now and I am spread quite thin among the various projects that I take an interest in. In particular, I am thrilled to publicly announce on this list that Continuum Analytics has received DARPA funding (to the tune of at least $3 million) for Blaze, Numba, and Bokeh which we are writing to take NumPy, SciPy, and visualization into the domain of very large data sets.This is part of the XDATA program, and I will be taking an active role in it.You can read more about Blaze here: http://blaze.pydata.org. You can read more about XDATA here: http://www.darpa.mil/Our_Work/I2O/Programs/XDATA.aspx I personally think Blaze is the future of array-oriented computing in Python. I will be putting efforts and resources next year behind making that case. How it interacts with future incarnations of NumPy, Pandas, or other projects is an interesting and open question. I have no doubt the future will be a rich ecosystem of interoperating array-oriented data-structures. I invite anyone interested in Blaze to participate in the discussions and development at https://groups.google.com/a/continuum.io/forum/#!forum/blaze-dev or watch the project on our public GitHub repo: https://github.com/ContinuumIO/blaze. Blaze is being incubated under the ContinuumIO GitHub project for now, but eventually I hope it will receive its own GitHub project page later next year. Development of Blaze is early but we are moving rapidly with it (and have deliverable deadlines --- thus while we will welcome input and pull requests we won't have a ton of time to respond to simple queries until at least May or June).There is more that we are working on behind the scenes with respect to Blaze that will be coming out next year as well but isn't quite ready to show yet. As I look at the coming months and years, my time for direct involvement in NumPy development is therefore only going to get smaller. As a result it is not appropriate that I remain as head steward of the NumPy project (a term I prefer to BFD12 or anything else). I'm sure that it is apparent that while I've tried to help personally where I can this year on the NumPy project, my role has been more one of coordination, seeking funding, and providing expert advice on certain sections of code.I fundamentally agree with Fernando Perez that the responsibility of care-taking open source projects is one of stewardship --- something akin to public service.I have tried to emulate that belief this year --- even while not always succeeding. It is time for me to make official what is already becoming apparent to observers of this community, namely, that I am stepping down as someone who might be considered head steward for the NumPy project and officially leaving the development of the project in the hands of others in the community. I don't think the project actually needs a new head steward --- especially from a development perspective. Instead I see a lot of strong developers offering key opinions for the project as well as a great set of new developers offering pull requests. My strong suggestion is that development discussions of the project continue on this list with consensus among the active participants being the goal for development. I don't think 100% consensus is a rigid requirement --- but certainly a super-majority should be the goal, and serious changes should not be made with out a clear consensus. I would pay special attention to under-represented people (users with intense usage of NumPy but small voices on this list). There are many of them.If you push me for specifics then at this point in NumPy's history, I would say that if Chuck, Nathaniel, and Ralf agree on a course of action, it will likely be a good thing for the project. I suspect that even if only 2 of the 3 agree at one time it might still be a good thing (but I would expect more detail and discussion).There are others whose opinion should be sought as well: Ondrej Certik, Perry Greenfield, Robert Kern, David Cournapeau, Francesc Alted, and Mark Wiebe to name a few.For some questions, I might even seek input from people like Konrad Hinsen and Paul Dubois --- if they have time to give it. I will still be willing to offer my view from time to time and if I am asked. Greg Wilson (of Software Carpentry fame) asked me recently what letter I would have written to myself 5 years ago. What would I tell myself to do given the knowledge I have now? I've thought about that for a bit, and I have some answers. I don't know if these will help anyone, but I offer them as hopefully instructive: 1) Do not promise to not break the ABI of NumPy --- and in fact emphasize that it will be broken at least once in the 1.X series.NumPy was designed to add new data-types --- but not without breaking the ABI.NumPy has
Re: [Numpy-discussion] DARPA funding for Blaze and passing the NumPy torch
On Mon, Dec 17, 2012 at 7:07 AM, Travis Oliphant tra...@continuum.iowrote: Hello all, There is a lot happening in my life right now and I am spread quite thin among the various projects that I take an interest in. In particular, I am thrilled to publicly announce on this list that Continuum Analytics has received DARPA funding (to the tune of at least $3 million) for Blaze, Numba, and Bokeh which we are writing to take NumPy, SciPy, and visualization into the domain of very large data sets.This is part of the XDATA program, and I will be taking an active role in it.You can read more about Blaze here: http://blaze.pydata.org. You can read more about XDATA here: http://www.darpa.mil/Our_Work/I2O/Programs/XDATA.aspx Hi Travis, that is fantastic news, congratulations! I can't wait to see what you guys will come up with in the near future. Also thank you for the rest of this thoughtful post; it'll take me some time to digest but I enjoyed the reflection on the past. Best, Ralf I personally think Blaze is the future of array-oriented computing in Python. I will be putting efforts and resources next year behind making that case. How it interacts with future incarnations of NumPy, Pandas, or other projects is an interesting and open question. I have no doubt the future will be a rich ecosystem of interoperating array-oriented data-structures. I invite anyone interested in Blaze to participate in the discussions and development at https://groups.google.com/a/continuum.io/forum/#!forum/blaze-dev or watch the project on our public GitHub repo: https://github.com/ContinuumIO/blaze. Blaze is being incubated under the ContinuumIO GitHub project for now, but eventually I hope it will receive its own GitHub project page later next year. Development of Blaze is early but we are moving rapidly with it (and have deliverable deadlines --- thus while we will welcome input and pull requests we won't have a ton of time to respond to simple queries until at least May or June).There is more that we are working on behind the scenes with respect to Blaze that will be coming out next year as well but isn't quite ready to show yet. As I look at the coming months and years, my time for direct involvement in NumPy development is therefore only going to get smaller. As a result it is not appropriate that I remain as head steward of the NumPy project (a term I prefer to BFD12 or anything else). I'm sure that it is apparent that while I've tried to help personally where I can this year on the NumPy project, my role has been more one of coordination, seeking funding, and providing expert advice on certain sections of code.I fundamentally agree with Fernando Perez that the responsibility of care-taking open source projects is one of stewardship --- something akin to public service. I have tried to emulate that belief this year --- even while not always succeeding. It is time for me to make official what is already becoming apparent to observers of this community, namely, that I am stepping down as someone who might be considered head steward for the NumPy project and officially leaving the development of the project in the hands of others in the community. I don't think the project actually needs a new head steward --- especially from a development perspective. Instead I see a lot of strong developers offering key opinions for the project as well as a great set of new developers offering pull requests. My strong suggestion is that development discussions of the project continue on this list with consensus among the active participants being the goal for development. I don't think 100% consensus is a rigid requirement --- but certainly a super-majority should be the goal, and serious changes should not be made with out a clear consensus. I would pay special attention to under-represented people (users with intense usage of NumPy but small voices on this list). There are many of them.If you push me for specifics then at this point in NumPy's history, I would say that if Chuck, Nathaniel, and Ralf agree on a course of action, it will likely be a good thing for the project. I suspect that even if only 2 of the 3 agree at one time it might still be a good thing (but I would expect more detail and discussion).There are others whose opinion should be sought as well: Ondrej Certik, Perry Greenfield, Robert Kern, David Cournapeau, Francesc Alted, and Mark Wiebe to name a few.For some questions, I might even seek input from people like Konrad Hinsen and Paul Dubois --- if they have time to give it. I will still be willing to offer my view from time to time and if I am asked. Greg Wilson (of Software Carpentry fame) asked me recently what letter I would have written to myself 5 years ago. What would I tell myself to do given the knowledge I have now? I've thought about that for a bit, and I
Re: [Numpy-discussion] Status of the 1.7 release
On Mon, Dec 17, 2012 at 12:26 AM, Nathaniel Smith n...@pobox.com wrote: On 16 Dec 2012 23:01, Charles R Harris charlesr.har...@gmail.com wrote: On Sun, Dec 16, 2012 at 3:50 PM, Ondřej Čertík ondrej.cer...@gmail.com wrote: Thanks Ralf and Nathan, I have put high priority on the issues that need to be fixed before the rc1. There are now 4 issues: https://github.com/numpy/numpy/issues?labels=priority%3A+highmilestone=3page=1state=open I am working on the mingw one, as that one is the most difficult. Ralf (or anyone else), do you know how to fix this one: https://github.com/numpy/numpy/issues/438 I am not very familiar with this part of numpy, so maybe you know how to document it well. The sooner we can fix these 4 issues, the sooner we can release. I believe mingw was updated last month to a new compiler version. I don't know what other changes there were, but it is possible that some problems have been fixed. It'd be worth checking in case it allows us to get off the (incredibly old) GCC that we currently require on windows. But that's a long-term problem that we probably shouldn't be messing with for 1.7 purposes. afaict all we need to do for 1.7 is switch to using our current POSIX code on win32 as well, instead of the (weird and broken) MS-specific API that we're currently using. (Plus suppress some totally spurious warnings): http://mail.scipy.org/pipermail/numpy-discussion/2012-July/063346.html (Or I could be missing something, but I don't think any problems with that solution have been discussed on the list anyway.) AFAICT Nathaniel's suggestion in the thread linked above is the way to go. Trying again to go to gcc 4.x doesn't sound like a good idea. Probably David C. already has a good idea about whether recent changes to MinGW have made a difference to the issue he ran into about a year ago. Ralf ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
