Mailman 3 July 2008 - SciPy-Dev

scipy 0.7 release
by Nils Wagner July 10, 2008

July 10, 2008

Hi all, Is it planned to release scipy 0.7 before the forthcoming Scipy Conference ? I don't think that 89 tickets will be closed in the foreseeable future. http://projects.scipy.org/scipy/scipy/roadmap http://projects.scipy.org/scipy/scipy/query?status=new&status=assigned&stat… Nils

2 1

svn access
by Nils Wagner July 10, 2008

July 10, 2008

Hi all, If I do svn co http://svn.scipy.org/svn/numpy/trunk numpy Authentication realm: <http://svn.scipy.org:80> scipy.org Password for 'nwagner': Any idea ? Nils

1 0

possible bug in numpy.random.zipf
by Alan Jackson July 9, 2008

July 9, 2008

I think I may have found a bug in numpy.random.zipf As I was documenting the zipf function, I started playing with it to create some examples. It's pretty cool, actually. I had never heard of it before. To my surprise, it started giving occasional very large negative numbers as results whenever the 'a' parameter was less than 1.5. It appears that there is some numerical instability for parameters less than 1.5. In [44]: min(np.random.zipf(1.4, 1000)) Out[44]: 1 In [45]: min(np.random.zipf(1.4, 1000)) Out[45]: -2147483648 In [46]: min(np.random.zipf(1.4, 1000)) Out[46]: 1 In [47]: min(np.random.zipf(1.4, 1000)) Out[47]: 1 In [48]: min(np.random.zipf(1.4, 1000)) Out[48]: 1 In [49]: min(np.random.zipf(1.4, 1000)) Out[49]: 1 The minimum value should never be less than 1, I think. -- ----------------------------------------------------------------------- | Alan K. Jackson | To see a World in a Grain of Sand | | alan(a)ajackson.org | And a Heaven in a Wild Flower, | | www.ajackson.org | Hold Infinity in the palm of your hand | | Houston, Texas | And Eternity in an hour. - Blake | -----------------------------------------------------------------------

3 3

REMINDER: SciPy 2008 Early Registration ends in 2 days
by Jarrod Millman July 9, 2008

July 9, 2008

Hello, This is a reminder that early registration for SciPy 2008 ends in two days on Friday, July 11th. To register, please see: http://conference.scipy.org/to_register This year's conference has two days for tutorials, two days of presentations, and ends with a two day coding sprint. If you want to learn more see my blog post: http://jarrodmillman.blogspot.com/2008/07/scipy-2008-conference-program-pos… Cheers, -- Jarrod Millman Computational Infrastructure for Research Labs 10 Giannini Hall, UC Berkeley phone: 510.643.4014 http://cirl.berkeley.edu/

1 0

Summer Doc Marathon status report and request for more writers
by Joe Harrington July 8, 2008

July 8, 2008

This is an interim status report on the Summer Documentation Marathon. It is also an invitation and plea for all experienced users to participate! I am cross-posting in an effort to get broader participation. Please hold any discussion on the scipy-dev mailing list. As you know, our immediate goal is to produce first-draft docstrings for the user-visible parts of Numpy in time for a release before Fall classes (about 1 August). The short version is: We are really moving along! But, we need *your* help to make it in time for August. Here's the scoop: 1. We have all our infrastructure, standards, and procedure in place: We have a wiki that makes editing the docs easy and even fun. It communicates directly with the numpy sources. We have PDF and HTML reference guides being generated essentially automatically: http://sd-2116.dedibox.fr/pydocweb http://mentat.za.net/numpy/refguide/NumPy.pdf http://mentat.za.net/numpy/refguide/ The wiki front page contains or points to all you need to get started. The wiki lets you pull down a docstring with a few mouse clicks, edit on your machine, upload it, and see how it will look in its HTML version right away. You can also read everyone else's docstrings, comment on them, see the status of the project, and so on. The formatted versions necessarily lag the docstrings on the wiki because they are made whenever the docstrings are checked into the sources. 2. We have documented about 1/4 of numpy in a fairly professional way, comparable to the reference pages of the major commercial packages. The doc wiki is probably the next place to go if your question isn't answered by the docstring in the current version's help(), since you can look at the new docstrings we've generated, and they're *good*! 3. But, we're only 1/4 of the way there, we're halfway through the summer, and some of the initial enthusiasm is waning. The following page tells the tale: http://sd-2116.dedibox.fr/pydocweb/stats/ As you can see (you did click, right? please click...), there are 2323 numpy objects with docstrings. Of these, 1464 we deemed "unimportant" (for now). These are generally items not seen by regular users. This left 859 objects to document in this first pass. We've done 24% of them at this writing. Now, 24% is really exciting, and I'd like to take a moment to say a public "Hooray!" for the team (no particular order): Stéfan van der Walt Pauli Virtanen Robert Hetland Gael Varoquaux Scott Sinclair Alan Jackson Tim Cera Johann Cohen-Tanugi David Huard Keith Goodman Together these ten have written around 7500 words of documentation on the community's behalf, mainly as volunteers. HOWEVER, we can all do the math. We've spent one of our two months. We are 1/4 of the way there. Progress is slowing, and even if it didn't, we wouldn't make it in time. This is not a sprint, it's a MARATHON. WE NEED YOUR HELP! And we need it now. Are you excited by the idea of having documentation for numpy by the Fall release? Of having docs that answer your questions, that have *good* examples, that really save you time? If so, then please invest just a fraction of the time that documentation will save you in the next year alone by signing up on the wiki and writing some. If each experienced user wrote just a few pages, we'd be done! If you don't think you know enough to write, then do some reviewing. Are the docs readable? Do you understand the examples? Each docstring on the wiki has an easy comment box waiting for your thoughts. You will have a reference guide in the next release of numpy! I hope you will help make it a complete one. Sign up on the doc wiki today: http://sd-2116.dedibox.fr/pydocweb/ Thanks, --jh-- and the SciPy Doc Team Prof. Joseph Harrington Department of Physics MAP 414 4000 Central Florida Blvd. University of Central Florida Orlando, FL 32816-2385 (407) 823-3416 voice (407) 823-5112 fax (407) 823-2325 physics office jh(a)physics.ucf.edu

7 12

scipy documentation marathon
by nicky van foreest July 5, 2008

July 5, 2008

Dear all, I like to participate as a reviewer in the documentation marathon. Thanks for all the effort you put into this. bye Nicky

1 0

[numscons] 0.8.1 released
by David Cournapeau July 5, 2008

July 5, 2008

Hi, I am pleased to announce numscons 0.8.1. numscons is a tentative for a new build system for numpy/scipy and other packages depending on numpy.distutils for extension code. You can get it through the usual channels: http://projects.scipy.org/scipy/numpy/wiki/NumScons I did not announce releases of numscons for quite some time, but this did not mean I did not continue working on numscons. The goal is to have a beta available for scipy conference in August, where I will present numscons. Most changes since 0.8.0 are internal, with code simplification (compiler customization, etc...). The goal is to put most of the code upstream into scons (numscons is now around 3700 lines of code, and I hope to be able to reduce this to ~ 2000 lines of code). In particular: - no custom code for fortran anymore, everything is now integrated upstream. - python extensions are now built using a scons tool. This means more reliability, and hopefully at some point upstream integration. There are still some rough edges, but hopefully, nothing fundamental. - VS 2003/2005/2008 are supported as well (numpy can build with python 2.6 alpha and Visual Studio express), using a method similar to distutils in python 2.6 to get informations from the var*.bat files (much simpler and more robust than relying on the brain-dead registry). Since 0.8, the changes are not backward compatible with < 0.8. In particular the names of python builders have changed, and you should now use 2 scons scripts instead of one. I am sorry I have not yet updated the documentation, but I really want to get a beta ready for scipy conference, and I don't have so much time to keep the doc in sync. The examples are up to date, though. cheers, David

1 0

joining the docs marathon
by Ralf Gommers July 5, 2008

July 5, 2008

Hi, I would like to help out with the documentation effort. The results look great so far, thanks for pushing hard for this! I'd like to do both reviewing and editing, and registered as RalfGommers. Cheers, Ralf

1 0

http://projects.scipy.org/scipy/scipy/ticket/573 and mkufunc
by Nils Wagner July 4, 2008

July 4, 2008

Hi, There seems to be a conflict of interest between http://projects.scipy.org/scipy/scipy/ticket/573 and the recent sandbox package mkufunc. Nils

1 0

joining the effort
by Roban Kramer July 4, 2008

July 4, 2008

Hi, I'd like to join the docstrings marathon. I probably won't get to contribute until I'm back from a conference in a week or so, but I'd guess I'll mostly be reviewing and proofreading, though I could do some editing, too. Thanks, Roban

2 2