[Numpy-discussion] [ANN] CFP: SciPy India 2012 -- Dec 27-29 -- IIT Bombay
Hello, The CFP for SciPy India 2012, to be held in IIT Bombay from December 27-29 is open. Please spread the word! Scipy.in is a conference providing opportunities to spread the use of the Python programming language in the Scientific Computing community in India. It provides a unique opportunity to interact with the Who's who of the Python for Scientific Computing fraternity and learn, understand, participate, and contribute to Scientific Computing using Python. Attendees of the conference and participants of the sprints planned will be able to access and review the tools available. They will also be able to learn domain-specific applications and how the tools apply to a plethora of application problems. One of the goals of the conference is to combine education, engineering, and science with computing through the medium of Python. This conference also aims to spread the use of Python for Scientific Computing in various fields and among different communities. Call for Papers We look forward to your submissions on the use of Python for Scientific Computing and Education. This includes pedagogy, exploration, modeling and analysis from both applied and developmental perspectives. We welcome contributions from academia as well as industry. Submission of Papers = If you wish to present your paper using this platform, please submit an abstract of 300 to 700 words describing the topic, including its relevance to scientific computing. Based on the number and quality of the submissions, the conference organizers will allot 10 - 30 minutes for each accepted talk. In addition to these talks, there will be an open session of lightning talks, during which any attendee who wishes to talk on a pertinent topic is invited to do a presentation not exceeding five minutes in duration. If you wish to present a talk at the conference, please follow the guidelines below. Submission Guidelines == - Submit your proposals at sc...@fossee.in - Submissions whose main purpose is to promote a commercial product or service will be refused. - All accepted proposals must be presented at the SciPy conference by at least one author. Important Dates - Call for proposals start: 27th September 2012, Thursday - Call for proposals end: 1st November 2012, Thursday - List of accepted proposals will be published: 19th November 2012, Monday - Submission of first presentation: 10th December 2012, Monday - Submission of final presentation(with final changes): 20th December 2012, Thursday ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] scipy.org still says source in some subversion repo -- should be git !?
On Mon, Nov 28, 2011 at 1:19 PM, Matthew Brett matthew.br...@gmail.comwrote: Maybe the content could be put in http://github.com/scipy/scipy.github.com so we can make pull requests there? The source is here: https://github.com/scipy/scipy.org-new ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] [ANN] SciPy India 2011 Abstracts due November 2nd
== SciPy 2011 Call for Papers == The third `SciPy India Conference http://scipy.in`_ will be held from December 4th through the 7th at the `Indian Institute of Technology, Bombay (IITB) http://www.iitb.ac.in/`_ in Mumbai, Maharashtra India. At this conference, novel applications and breakthroughs made in the pursuit of science using Python are presented. Attended by leading figures from both academia and industry, it is an excellent opportunity to experience the cutting edge of scientific software development. The conference is followed by two days of tutorials and a code sprint, during which community experts provide training on several scientific Python packages. We invite you to take part by submitting a talk abstract on the conference website at: http://scipy.in Talk/Paper Submission == We solicit talks and accompanying papers (either formal academic or magazine-style articles) that discuss topics regarding scientific computing using Python, including applications, teaching, development and research. We welcome contributions from academia as well as industry. Important Dates == November 2, 2011, Wednesday: Abstracts Due November 7, 2011, Monday: Schedule announced November 28, 2011, Monday: Proceedings paper submission due December 4-5, 2011, Sunday-Monday: Conference December 6-7 2011, Tuesday-Wednesday: Tutorials/Sprints Organizers == * Jarrod Millman, Neuroscience Institute, UC Berkeley, USA (Conference Co-Chair) * Prabhu Ramachandran, Department of Aerospace Engineering, IIT Bombay, India (Conference Co-Chair) * FOSSEE Team ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] Call for GSoC 2011 NumPy mentors
Hi, It is time to start preparing for the 2011 Google Summer of Code (SoC). As in the past, we will participate in SoC with the Python Software Foundation (PSF) as our mentoring organization. The PSF has requested that every project, which wishes to participate in the SoC, provide a list of at least *three* potential mentors. If you are interested and willing to potentially mentor someone this summer to work on NumPy, please send me the following information by Monday evening: Name, Email, Phone, and Link_ID. You can find additional information on the 2011 SoC homepage: http://socghop.appspot.com/ Here is the PSF SoC page: http://wiki.python.org/moin/SummerOfCode Please start thinking about potential projects and add them to the SoC ideas page: http://projects.scipy.org/scipy/wiki/SummerofCodeIdeas Thanks, Jarrod ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Question regarding submitting patches
On Tue, Jan 4, 2011 at 7:49 PM, Justin Peel wrote: I've been submitting some patches recently just by putting them on Trac. However, I noticed in the Numpy Developer Guide that it says: The recommended way to proceed is either to attach these files to an enhancement ticket in the Numpy Trac and send a mail about the enhancement to the NumPy mailing list. For now, we should just remove the 'either'. I will take a look at how to reintegrate the changes into the master gitwash document later tonight: https://github.com/matthew-brett/gitwash/blob/master/gitwash/patching.rst Thanks for pointing out the grammatical error. Jarrod PS. Just to be clear, the developer doc you are referring to is: http://docs.scipy.org/doc/numpy/dev/gitwash/patching.html I just want to make sure that there isn't some old wiki page somewhere that needs to be deleted. ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] [ANN] SciPy India 2010 Call for Presentations
== SciPy 2010 Call for Papers == The second `SciPy India Conference http://scipy.in`_ will be held from December 13th to 18th, 2010 at `IIIT-Hyderabad http://www.iiit.ac.in/`_. At this conference, novel applications and breakthroughs made in the pursuit of science using Python are presented. Attended by leading figures from both academia and industry, it is an excellent opportunity to experience the cutting edge of scientific software development. The conference is followed by two days of tutorials and a code sprint, during which community experts provide training on several scientific Python packages. We invite you to take part by submitting a talk abstract on the conference website at: http://scipy.in Talk/Paper Submission == We solicit talks and accompanying papers (either formal academic or magazine-style articles) that discuss topics regarding scientific computing using Python, including applications, teaching, development and research. Papers are included in the peer-reviewed conference proceedings, published online. Please note that submissions primarily aimed at the promotion of a commercial product or service will not be considered. Important Dates == Monday, Oct. 11: Abstracts Due Saturday, Oct. 30: Schedule announced Tuesday, Nov. 30: Proceedings paper submission due Monday-Tuesday, Dec. 13-14: Conference Wednesday-Friday, Dec. 15-17: Tutorials/Sprints Saturday, Dec. 18: Sprints Organizers == * Jarrod Millman, Neuroscience Institute, UC Berkeley, USA (Conference Co-Chair) * Prabhu Ramachandran, Department of Aerospace Engineering, IIT Bombay, India (Conference Co-Chair) * FOSSEE Team ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] sf.net export controls for numpy/scipy
Hello, I plan to update the export controls settings for both numpy and scipy to: This project does NOT incorporate, access, call upon, or otherwise use encryption of any kind, including, but not limited to, open source algorithms and/or calls to encryption in the operating system or underlying platform. Unless I hear from someone that I overlooked something, I will make the changes tomorrow. Best, Jarrod ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] update on the transition to git/github
Hello all, On May 26th, I sent an email titled curious about how people would feel about moving to github. While there were a few concerns raised, everyone was generally positive and were mainly concerned that this transition would need to be done carefully with clear workflow instructions and an clearly marked master repository. Since then David Cournapeau has done a lot of work looking into how to make the transition go as smoothly as possible. He has written a script to convert the svn repository to a git repository. And I've registered a numpy organization account on github. Over the next week, David, Stefan, and I will set things up so that everyone can see how things will work after the transition to git. David will convert the current trunk to a git repository and put it on the github site. We will write up instructions on how to use git and the github site. Everyone who wants to can get a github account and test out the workflow. At that point everyone can provide feedback and we can decide if we are ready to move forward. If we are ready to move forward, we will set up a date for the transition. On that date, we would turn off the old subversion account and create a new git repository which would from the point forward be the new master branch. If the transition to git and github for numpy goes smoothly, we will turn our attention to scipy. During the SciPy conference in Austin, we had a Birds-of-a-Feather to discuss the transition to git and github. [[ Here is a picture of the git/github BOF (several people joined the discussion later including Travis Oliphant and Fernando Perez): http://www.flickr.com/photos/irees/4750650877/sizes/l/in/set-72157624272131693/ ]] At the end of the discussion there was a general consensus that it was time to make the move. Several questions and concerns were raised: 1. Since there are many possible workflows, it is important to clearly document are proposed workflow. This document should provide simple cut-and-paste commands necessary to get developers up and running with git. 2. The question was raised about how to handle bug reports. It was pointed out that while our current trac bug report system isn't perfect, it does work and people are used to it. We decided to keep our existing trac instance and integrate it with the github site. Potentially moving from trac to another system like redmine was brought up, but most people felt it was better to only change one thing at a time (and besides that no one volunteered to do the work necessary to move to a new bug tracking system). 3. Since Ralf Gommers is in the middle of making a release, did he want us to delay any transition preparation until he was finished. This is Ralf's response when Stefan van der Walt contacted him: Thanks for asking! For me the sooner the better, I do everything with git and haven't touched svn since I discovered Mercurial while writing my thesis (and that feels like a long long time ago). When Stefan contacted Ralf, Ralf raised the following additional concern: 4. The two things I haven't seen a good solution for are the svn/externals in scipy which pulls in doc/sphinxext from numpy, and the vendor branch. In response, Stefan asked whether submodules would provide a solution. David Cournapeau responded to Stefan stating submodules are very awkward to use. Then David added in response to Ralf's original query: For vendor, it will be a separate repo, and there is no need for synchronization, so that's easy to deal with. For the sphinx extension, I would just merge with the subtree strategy from time to time from a separate repository. That's what I do for bento + yaku: yaku has its own repo, and when I update the copy in bento, I just use git merge -s subtree --no-squash, so everything is updated in one commit. The big advantage is that there is no need to even be aware of the second repo for users (git clone will bring everything), and there is no chance of screwing things up: http://book.git-scm.com/5_advanced_branching_and_merging.html; Best, Jarrod ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] update on the transition to git/github
On Tue, Jul 13, 2010 at 8:15 PM, Charles R Harris charlesr.har...@gmail.com wrote: How should we handle commits during the next week or two? I have a few things I want to get in before 1.5 is tagged. Just keep committing as normal using svn for now. Once we are ready to make the transition (which includes having documentation for windows' users posted and having received positive feedback during the testing phase), we will announce a commit freeze and make sure the time is OK for everyone. During the testing phase and up until we've actually made the transition, the only place where committed code counts is in the svn repo. Once the testing phase has successfully been completed, the testing git repo will be deleted. Then when the commit freeze starts we will make the svn repo read only. At that point David will create a new git repo from the svn repo and host it on github. At that point forward, the svn repo will remain read only so that no one can mistakenly write to it. I hope that makes sense (I just got back from the Euroscipy conference and didn't get any sleep on the plane). Jarrod ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Technicalities of the SVN - GIT transition
On Wed, Jun 2, 2010 at 10:08 AM, Matthew Brett matthew.br...@gmail.com wrote: Do y'all think opt-in? Or opt-out? If it's opt-in I guess you'll catch most of the current committers, and most of the others you'll lose, but maybe that's good enough. I think it should be opt-in. How would opt-out work? Would someone create new accounts for all the contributors and then give them access? If that is the case, I would really rather avoid this. If someone wants an account on github, they should register an account on their own. Or am I missing something? Thanks, Jarro ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] curious about how people would feel about moving to github
On Thu, May 27, 2010 at 2:28 AM, Anne Archibald aarch...@physics.mcgill.ca wrote: To get back to the original point of the thread: nobody has yet objected to git, and all we have are some debates about the ultimate workflow that don't make much difference to whether or how git should be adopted. Is this a fair description? Yes, that is my take on it. Since it seems that everyone is open to *discuss* moving to git/github, Stefan and I will draft a NEP for this transition. Stefan is currently visiting Berkeley, so we can easily work together on this over the next few days. However, we are going camping this weekend so we will be off-line more or less from Thursday night until Monday night. We will start the git/github NEP during the trip and then post it to the list for feedback and discussion on Monday night or Tuesday morning. If anyone else is interested in helping draft the NEP over the weekend, please let me know ASAP. We will raise and address as many concerns as possible. I believe the concerns raised so far can be satisfactorily addressed and hopefully the process of writing the NEP will let us systematically explore any potential concerns or problems. Here is a quick list of topics we will address in the NEP: - Client (Windows, Mac, and Linux) support - Issue tracking system integration - Buildbot interaction - Workflow - Legacy support for svn clients - Testing and deployment - Potential timeline If you have any other areas of concern you would like to see addressed, please let us know. Obviously, the weekend draft will be subject to change according to the feedback. Thanks, Jarrod ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] curious about how people would feel about moving to github
On Thu, May 27, 2010 at 2:28 AM, Anne Archibald aarch...@physics.mcgill.ca wrote: * Set up a git repository somewhere on scipy.org. It's a minor point, but setting up and maintaining our own git repository will require extra work without gaining anything useful. Github has a number of very useful features and is gaining new functionality all the time. It also greatly simplifies account management, which is a royal pain with our current system. Obviously this is a separate issue from whether we move to git or not, but I just wanted to address it quickly. I've registered the following github accounts just to reserve them for now: http://github.com/numpy http://github.com/scipy http://github.com/scikits Jarrod ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Introduction to Scott, Jason, and (possibly) others from Enthought
2010/5/25 Stéfan van der Walt ste...@sun.ac.za: Awesome! Since github now supports SVN interaction, and all the core devs use Git, now might be a good time to move the entire numpy source tree? It will certainly make it easier to merge the refactor changes! I would love to move numpy to github as well. Almost everything I work on is there now and I am really enjoying using git and the github infrastructure is really nice. This is obviously a separate issue and one that shouldn't deflect the discussion on the proposed refactoring. But given how many of the developers are using git-svn and that you can use an svn client with github, it might be worth having a quick discussion about this in the near future. For instance, I wonder how many of the developer's prefer using git at this point. Also it would be interesting to hear from any of the developer's who would be opposed to git. A few year's ago this was a hot topic for discussion, but it may be that this isn't very controversial at this point. Jarrod ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] curious about how people would feel about moving to github
Hello, I changed the subject line for this thread, since I didn't want to hijack another thread. Anyway, I am not proposing that we actually decide whether to move to git and github now, but I am just curious how people would feel. We had a conversation about this a few years ago and it was quite contentious at the time. Since then, I believe a number of us have started using git and github for most of our work. And there are a number of developers using git-svn to develop numpy now. So I was curious to get a feeling for what people would think about it, if we moved to git. (I don't want to rehash the arguments for the move.) Anyway, Chuck listed the main concerns we had previously when we discussed moving from svn to git. See the discussion below. Are there any other concerns? Am I right in thinking that most of the developers would prefer git at this point? Or are there still a number of developers who would prefer using svn still? On Wed, May 26, 2010 at 12:54 PM, Charles R Harris charlesr.har...@gmail.com wrote: I think the main problem has been windows compatibility. Git is best from the command line whereas the windows command line is an afterthought. Another box that needs a check-mark is the buildbot. If svn clients are supported then it may be that neither of those are going to be a problem. I was under the impression that there were a number of decent git clients for Windows now, but I don't know anyone who develops on Windows. Are there any NumPy developers who use Windows who could check out the current situation? Pulling from github with an svn client works very well, so buildbot could continue working as is: http://github.com/blog/626-announcing-svn-support And if it turns out the Windows clients are still not good enough, we could look into the recently add svn write support to github: http://github.com/blog/644-subversion-write-support No need for us to make any changes immediately. I am just curious how people would feel about it at this point. Jarrod ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] curious about how people would feel about moving to github
On Wed, May 26, 2010 at 4:12 PM, Travis Oliphant oliph...@enthought.com wrote: I think we are ready for such a move. Someone should think about the implications, though (with Trac integration, check-in mailings, etc.) and make sure we get something we all like. Somebody probably has thought through all of these things already, though. Cool. At this point, I am just testing the water. If enough people seem to be OK with the idea in general, I can spend some time looking into the details more closely. Before we make an actual decision, it would be worth turning this into an actual NEP and then asking people to review it. Jarrod ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Introduction to Scott, Jason, and (possibly) others from Enthought
On Wed, May 26, 2010 at 6:35 PM, Charles R Harris charlesr.har...@gmail.com wrote: Heh. Can you to try the svn interface to github using your favorite svn ap. I suppose we need to set up a test account there. Is it possible to have a multiple user git account on github, or is it all push and merge? Yes, that is possible. Currently it is not officially allowed according to their terms of service, but they are planning to enable that and have granted exceptions to their current policy in a few instances (that I am familiar with). But this is a detail that we can easily address in a NEP, if there seems to be interest (which there currently seems to be). So for now just keep sending emails with issues you want addressed in any actual proposal for this transition. Let's move this discussion to the git thread and use the thread for the discussion related directly to the subject line. Thanks, -- Jarrod Millman Helen Wills Neuroscience Institute 10 Giannini Hall, UC Berkeley http://cirl.berkeley.edu/ ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] curious about how people would feel about moving to github
On Wed, May 26, 2010 at 8:08 PM, Matthew Brett matthew.br...@gmail.com wrote: That's the model we've gone for in nipy and ipython too. We wrote it up in a workflow doc project. Here are the example docs giving the git workflow for ipython: https://cirl.berkeley.edu/mb312/gitwash/ and in particular: https://cirl.berkeley.edu/mb312/gitwash/development_workflow.html I would highly recommend using this workflow. Ideally, we should use the same git workflow for all the scipy-related projects. That way developers can switch between projects without having to switch workflows. The model that Matthew and Fernando developed for nipy and ipython seem like a very reasonable place to start. ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] curious about how people would feel about moving to github
On Wed, May 26, 2010 at 7:38 PM, Benjamin Root ben.r...@ou.edu wrote: I wouldn't call myself a developer, but I have been wanting to contribute recently. I learned source control with svn, so I am much more comfortable with it. My one attempt at using git for a personal project ended in failure. Then I discovered this guide, Git-SVN Crash Course: http://git.or.cz/course/svn.html I hope this would be useful to other subversioners like me who might be hesistant to switch to git. Thanks for the link. If we move to git, we will also develop a suggested workflow and post it online so that anyone should be able to just cut-and-paste the git commands. As Matthew mentioned both ipython and nipy have adopted the same workflow: https://cirl.berkeley.edu/mb312/gitwash/development_workflow.html The idea of the above document is not to teach people how to use git in general, but just for the specific way git is used in the development workflow for nipy and ipython. If you have some time to look at the ipython/nipy workflow, it would be useful to know how helpful you think a document like this would be for SVNers switching to git. If you have any other suggestions for what the NEP should include, please let us know. Thanks, Jarrod PS. I am glad to hear that you are interested in contributing to NumPy development. If you are looking for a good place to start, you may want to consider helping with the 2010 summer documentation marathon or submitting a patch to address an open ticket. ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] proposing a beware of [as]matrix() warning
On Wed, Apr 28, 2010 at 2:46 PM, David Warde-Farley d...@cs.toronto.edu wrote: Would it be acceptable to retain the matrix class but not have it imported in the default namespace, and have to import e.g. numpy.matlib to get at them? +1 Jarrod ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] PSF GSoC 2010 (Py3K focus)
Hello, Given the interest in participating in the GSoC this summer, I am forwarding a very interesting email from Titus Brown. If you are interested in doing a GSoC or mentoring, please read his email carefully. Basically, the PSF will be focuing on Py3K-related projects. Given Pauli's work on Py3K support for NumPy, I think we might be in a good position to move forward on porting the rest of our stack to Py3K. So we should focus on projects to: 1. finish porting and testing NumPy with Py3K 2. port and test SciPy with Py3K 3. port and test matplotlib with Py3K 4. port and test ipython with Py3K 5. etc. Given the PSF's stated emphasis this year, it probably doesn't make sense to pursue any non-Py3K projects. Jarrod -- Forwarded message -- From: C. Titus Brown c...@msu.edu Date: Tue, Mar 2, 2010 at 6:12 AM Subject: [SoC2009-mentors] [...@msu.edu: GSoC 2010 - it's on!] To: soc2009-ment...@python.org - Forwarded message from C. Titus Brown c...@msu.edu - Date: Wed, 24 Feb 2010 12:54:52 -0800 From: C. Titus Brown c...@msu.edu To: psf-memb...@python.org Cc: gsoc2010-ment...@python.org Subject: GSoC 2010 - it's on! Hi all, it's that time of year again, and Google has decided to run the Google Summer of Code again! http://groups.google.com/group/google-summer-of-code-discuss/browse_thread/thread/d839c0b02ac15b3f http://socghop.appspot.com/ Arc Riley has stepped up to run it for the PSF again this year, and I'm backstopping him. If you are interested in mentoring or kibbitzing on those who are, please sign up for the soc2010-mentors mailing list here, http://mail.python.org/mailman/listinfo/soc2010-mentors This year we're proposing to solicit and prioritize applications for Python 3.x -- 3K tools, porting old projects, etc. Python 2.x projects will be a distinct second. There will be no core category this year, although obviously if someone on one of the core teams wants to push a project it'll help! If you have an idea for a project, please send it to the -mentors list and add it to the wiki at http://wiki.python.org/moin/SummerOfCode/2010 We're also going to change a few things up to make it more useful to the PSF. Specifically, - the foundation is going to *require* 1 blog post/wk from each student. - we're going to hire an administrative assistant to monitor the students. - the student application process will be a bit more rigorous and job-app like; the Django SF has been doing this for at least one round and they claim that it results in much better and more serious students. - we'll be focusing on student quality more than on project egalitarianism. If project X can recruit three fantastic students to one fantastic and one mediocre student for project Y, then project X gets three and project Y gets one. The hope is that this will make the GSoC much more useful for Python than it has been in the past. Arc will be posting something to the www.python.org site and python-announce soon, too. Followups to soc2010-mentors. cheers, --titus -- C. Titus Brown, c...@msu.edu - End forwarded message - ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] PSF GSoC 2010 (Py3K focus)
I added Titus' email regarding the PSF's focus on Py3K-related projects to our SoC ideas wiki page: http://projects.scipy.org/scipy/wiki/SummerofCodeIdeas Given Titus' email, this is the most likely list of projects we will get accepted this year: - finish porting NumPy to Py3K - port SciPy to Py3K - port matplotlib to Py3K - port ipython to Py3K Given that we know what projects we will likely have accepted, it is worth starting to flesh these proposals out in detail. Also, we should start discussing how we will choose which student's we want to work on these ports. In particular, we should list what skills and background will be necessary to successfully complete these ports. Thoughts? Ideas? Best, Jarrod ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] todos before 1.4.1 RC1
On Mon, Mar 1, 2010 at 6:52 AM, Ralf Gommers ralf.gomm...@googlemail.com wrote: Here are some requests / things I think need to be done before a 1.4.1 RC1 can be put out. 1. Bump up the version to 1.4.1 2. Update the release notes, including an explanation of why 1.4.0 was pulled. 3. Patrick and I need info on how to upload to Sourceforge. David or Jarrod, can you tell us how this works (offlist)? I guess I can do 1 and 2, but I don't have commit rights. I'm happy to get them, if you'd all prefer that I submit patches for a while first that's fine too. Sure, I will send you a follow-up email right away. Then, I'm also going to try this once more: in my opinion we should not release numpy 1.4.1 before scipy 0.7.2. Consider this: numpy 1.3 + scipy 0.7.1 = OK numpy 1.4.1 + scipy 0.7.2 = OK numpy 1.3 + scipy 0.7.2 = OK numpy 1.4.1 + scipy 0.7.1 = NOT OK (Cython issue) So either release 1.4.1 and 0.7.2 at the same time, or scipy 0.7.2 first. You should release scipy 0.7.2 first. Since this is your first time managing the release process, it would be easier to do them one at a time. Thanks, -- Jarrod Millman Helen Wills Neuroscience Institute 10 Giannini Hall, UC Berkeley http://cirl.berkeley.edu/ ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] 1.4 still the candidate for easy_install
Good catch. I just removed the 1.4.0 tarball from PyPI. Thanks, -- Jarrod Millman Helen Wills Neuroscience Institute 10 Giannini Hall, UC Berkeley http://cirl.berkeley.edu/ ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] numpy 2.0, what else to do?
On Sat, Feb 13, 2010 at 1:49 PM, Travis Oliphant oliph...@enthought.com wrote: This is exactly what I was worried about with calling the next release 2.0. This is not the time to change all the things we wish were done differently. The release is scheduled for 3 weeks. Hey Travis, I agree with your general sentiment (and I assume Chuck does too). And I don't think either of us is suggesting that we change all the things we want done differently. I do think that it is reasonable for us to suggest a few changes that could be implemented quickly to the list and just have a quick up or down vote on that specific issue without having to have a general discussion regarding what 2.0 is. So there are at least three suggestions on the table right now: 1. I would like to add deprecation warnings for the numarray and numeric support (but leave all the code in at least until the 3.0 release). 2. Chuck proposed requiring explicit imports for things like fft. 3. Chuck also suggested deprecating the old polynomial support and make it not be imported by default. These things are relatively small and easy to implement. If someone is willing to do the work within, say a week, I think we should go for it. I am sure others may disagree. Why can't we just agree that the release is scheduled for 3 weeks from now. And if someone suggests a change that they commit to implementing in one weeks time and that won't require very much new code (for instance a deprecation warning), let's just vote for or against it. If it seems like people are generally in favor of the change, let's include it. So without changing the timing of the next release, would you still be against the three changes suggested by Chuck and me? I am in favor of making the above three changes as long as they don't add a ton of new code, functionality, or delay the release in any way. What do other people think? Thanks, Jarrod ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Removing datetime support for 1.4.x series ?
On Thu, Feb 11, 2010 at 3:41 PM, Pierre GM pgmdevl...@gmail.com wrote: Jus to make sure I understand: * 2.0 will be w/ datetime support and corresponds to the current trunk * 1.5 will be w/o datetime support ? I may have misunderstood, but my understanding is that there will be no 1.5 release under the current proposal. The next release will be 2.0 and will come out in 3-4 weeks time. 2.0 will basically be 1.4.0 with at least the ABI changes Travis outlined. If 2.0 is coming out in 3-4 weeks time we will need to be careful about how aggressive we are in terms of doing any more than 1.4 + ABI changes. Once the general plan is agreed upon, which seems to be the direction that things are headed, then we will need to decide whether we should just work on the trunk or use the 1.4 branch with possibly a few things backported from the branch. I am happy to simply back whatever strategy David Cournapeau thinks is best. Personally, I would love to see Pauli's work toward supporting Py3k make it in to the NumPy 2.0 release and I believe that Pauli thinks that is reasonable to do in a 3-4 week timeframe. I don't think we should even try to provide binaries for Py3k during this release, though. I would also like to mark the numarray and numeric support as deprecated and planned for removal in NumPy 3.0. Just marking it deprecated shouldn't cause any problems and should give anyone left using the old interfaces plenty of time to migrate prior to a future 3.0 release. -- Jarrod Millman Helen Wills Neuroscience Institute 10 Giannini Hall, UC Berkeley http://cirl.berkeley.edu/ ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Python 2.6 and numpy 1.3.0/1.4.0 from an extension
On Mon, Feb 8, 2010 at 11:11 AM, Alan G Isaac ais...@american.edu wrote: I see that NumPy 1.4.0 is still the download offered on SourceForge. Did I misunderstand that a decision had been made to withdraw it, at least until the ongoing discussion about ABI breakage is resolved? I went ahead and set the default download for NumPy back to the 1.3.0 release on sourceforge. I also added a news item stating that 1.4.0 has temporarily been pulled due to the unintended ABI break. -- Jarrod Millman Helen Wills Neuroscience Institute 10 Giannini Hall, UC Berkeley http://cirl.berkeley.edu/ ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Removing datetime support for 1.4.x series ?
I went ahead and set the default download for NumPy back to the 1.3.0 release on sourceforge. I also added a news item stating that 1.4.0 has temporarily been pulled due to the unintended ABI break pending a decision by the developers. Currently, the 1.4.0 release can still be accessed if you go to the download manager for sourceforge. Jarrod ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Removing datetime support for 1.4.x series ?
On Mon, Feb 8, 2010 at 1:57 PM, Charles R Harris charlesr.har...@gmail.com wrote: Should the release containing the datetime/hasobject changes be called a) 1.5.0 b) 2.0.0 My vote goes to b. Jarrod ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Removing datetime support for 1.4.x series ?
On Mon, Feb 8, 2010 at 2:08 PM, Darren Dale dsdal...@gmail.com wrote: You don't matter. Nor do I. I definitely should have counted to 100 before sending that. It wasn't helpful and I apologize. No worries, your first email brought a smile to my face. ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Removing datetime support for 1.4.x series ?
On Sat, Feb 6, 2010 at 7:16 PM, Travis Oliphant oliph...@enthought.com wrote: I will just work on trunk and assume that the next release will be ABI incompatible. At this point I would rather call the next version 1.5 than 2.0, though. When the date-time work is completed, then we could release an ABI-compatible-with-1.5 version 2.0. My view of the timeline for the 1.5 release is the end of February. I would prefer that we follow our previously discussed, agreed upon, and explicitly stated version numbering policy: * The releases will be numbered major.minor.bugfix * There will be no ABI changes in minor releases * There will be no API changes in bugfix releases In addition to it being our policy, it is also more closely aligned with my general expectations for any mature open source project. Just to be clear, I would prefer to see the ABI-breaking release be called 2.0. I don't see why we have to get the release out in three weeks, though. I think it would be better to use this opportunity to take some time to make sure we get it right. I am not suggesting that we delay for months. Instead, why don't we agree to consider ABI-breakage for to 2-3 weeks. Then close the discussion and try to get the 2.0 release out as quickly after that as possible. -- Jarrod Millman Helen Wills Neuroscience Institute 10 Giannini Hall, UC Berkeley http://cirl.berkeley.edu/ ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Removing datetime support for 1.4.x series ?
On Fri, Feb 5, 2010 at 12:32 PM, Christopher Barker chris.bar...@noaa.gov wrote: If that's the case, and particularly if it's going to be a while before 1.4.1 is ready, I suggest that the 1.4.0 release be pulled from current release status on the download sites. +1 ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Removing datetime support for 1.4.x series ?
On Thu, Feb 4, 2010 at 10:06 AM, Charles R Harris charlesr.har...@gmail.com wrote: Let me propose a schedule: 1.4.1 : Bug fix, no datetime, ~4-6wks from now. 2.0 : API break, datetime, hasobject changes, April - May timeframe 2.1 : Python 3K - Fall I like your schedule in general. The only change I would suggest is releasing 1.4.1 ASAP with just datetime removed. We can always release a 1.4.2 with more bugfixes later. I like getting a 2.0 out in April-May with API break, datetime, and hasobject changes. It gives us time to communicate with all the other packagers and doesn't prevent us from quickly getting datetime out. The only thing I would suggest is that we try to get at least experimental support for Py3k out with the 2.0 release in April-May (even in an unreleased branch). That way other projects (scipy, matplotlib, etc) could potentially work on Py3k support over the summer as well. -- Jarrod Millman Helen Wills Neuroscience Institute 10 Giannini Hall, UC Berkeley http://cirl.berkeley.edu/ ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Removing datetime support for 1.4.x series ?
On Tue, Feb 2, 2010 at 12:11 AM, David Cournapeau courn...@gmail.com wrote: Both Chuck and myself are in favor of removing the datetime altogether for 1.4.x as a solution. At least in my case, it is mostly justified by the report from David Huard that the current datetime support is still a bit too experimental to be useful for people who rely on binaries. +1 I know some people at Berkeley looked into using the current datetime code and also felt it was too experimental to use at this point. I also agree with you that it is important to solve this issue ASAP. Thanks for all your hard work with the 1.4 release and your effort in tracking down this problem. Jarrod ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Wanted: new release manager for 1.5 and above
First I want to give David Cournapeau a big thank you for all his hard work as release manager for the last few years. It is a lot of work and he has done a great job managing the releases (not to mention all the work he has done as one of the primary developers). I also want to thank Patrick Marsh and Ralf Gommers for stepping up to the plate and volunteering to help with the next release. I would like to ask you both to consider committing to managing the next few releases. I believe managing the releases takes some skills, which you will develop over a few releases. It will be much better for the community and for the project if we can have some consistency over the release process. I know David is willing to help you with at least the first release and I am happy to help as well. One of the things that both David and I would really like to see is finally moving to a time-based release. Both of us had moved in the direction of a time-based release and I think David had more success than I did. Ideally I would like to see the two of you commit to two years as release managers. So if we move to a time-based release every 6 months, then you would be responsible for 4 releases. As release managers, you will be responsible for keeping an eye of the trunk and making sure that it stays in a healthy releasable state. It would be great if you could work on improving the testing infrastructure and coverage. You will need to keep a good line of communication with the developers and keep everyone focused on the release date. You will also need to help write the release notes and build the binaries. Thanks, Jarrod ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Numpy 1.4.0 rc1 released
On Tue, Dec 1, 2009 at 4:47 AM, David Cournapeau courn...@gmail.com wrote: The first release candidate for 1.4.0 has been released. Excellent! Thanks for all your effort, Jarrod ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] 1.4.0: Setting a firm release date for 1st december.
On Fri, Nov 13, 2009 at 3:25 AM, Ralf Gommers ralf.gomm...@googlemail.com wrote: All wiki changes are now reviewed and can be merged. Under numpy/doc there is a file HOWTO_MERGE_WIKI_DOCS.txt with details on how this is done. I checked in the majority of the doc changes, but there are some minor problems with the remaining diffs. I have to run now, but I will look at it later today. Thanks, -- Jarrod Millman Helen Wills Neuroscience Institute 10 Giannini Hall, UC Berkeley http://cirl.berkeley.edu/ ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] 1.4.0: Setting a firm release date for 1st december.
On Wed, Nov 4, 2009 at 1:37 AM, Ralf Gommers ralf.gomm...@googlemail.com wrote: It would be good if we could also have one more merge of the work in the doc editor (close to 300 new/changed docstrings now). I can have it all reviewed by the 13th. That would be great. Thanks for taking care of that. Unless you object, I'd also like to include the distutils docs. Complete docs with some possible minor inaccuracies is better than no docs. +1 -- Jarrod Millman Helen Wills Neuroscience Institute 10 Giannini Hall, UC Berkeley http://cirl.berkeley.edu/ ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] GSOC 2010
On Wed, Oct 21, 2009 at 12:02 PM, Charles R Harris charlesr.har...@gmail.com wrote: I don't feel that numpy/scipy did as well in GSOC 2009 as it could have. I'd be curious to hear why you felt that numpy/scipy didn't do as well this year. We had more projects than any other year and I think that most of the code ended being used. It could be that the work done wasn't publicized enough or that the most of the contributions end up contributed to related projects like in a scikit or (hopefully soon to be merged work) in cython. At any rate, I'd be curious to hear more about your concerns so that they we don't repeat them next year (assuming the program is run again next year). I think this was mostly due to lack of preparation on our part, we weren't ready when the students started showing up on the lists. So I would like to put together a selection of suitable projects and corresponding mentors that we could put on the wiki somewhere and advertise. Just to start things off, here are two things that come to mind. Regardless, better preparation would be a huge help. Having detailed lists of summer projects will be useful even if the SoC program doesn't get approved for next year. Python 3k transition. I think it is time to start looking at this seriously. Best of breed special functions in cython. These could be part of a separate numpy extras package where code is restricted to C, Cython, and Python. Both of these ideas sounds very interesting. Personally, I would like to see ideas like these make there way into fully fleshed out NEPs: http://projects.scipy.org/numpy/browser/trunk/doc/neps -- Jarrod Millman Helen Wills Neuroscience Institute 10 Giannini Hall, UC Berkeley http://cirl.berkeley.edu/ ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] merging docs from wiki
On Thu, Oct 1, 2009 at 9:19 AM, Ralf Gommers ralf.gomm...@googlemail.com wrote: Sorry to ask again, but it would really be very useful to get those docstrings merged for both scipy and numpy. I will do this now. Jarrod ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] ANN: SciPy 2009 early registration ends today
Today is the last day to register for SciPy 2009 at the early bird rates. Please register (http://conference.scipy.org/to_register ) by the end of the day to take advantage of the reduced early registration rate. The conference schedule is available here: http://conference.scipy.org/schedule The special group rate for the Marriot Hotel is no longer available. However, there are a number of closer and less expensive choices still available: http://admissions.caltech.edu/visiting/accommodations I've been staying at the Vagabond Inn for the last several years: http://www.vagabondinn-pasadena-hotel.com/ It is within easy walking distance of the conference and has just been completely renovated. Rooms at the Vagabond start at $79/night. About the conference SciPy 2009, the 8th Python in Science conference, will be held from August 18-23, 2009 at Caltech in Pasadena, CA, USA. The conference starts with two days of tutorials to the scientific Python tools. There will be two tracks, one for introduction of the basic tools to beginners, and one for more advanced tools. The tutorials will be followed by two days of talks. Both days of talks will begin with a keynote address. The first day’s keynote will be given by Peter Norvig, the Director of Research at Google; while, the second keynote will be delivered by Jon Guyer, a Materials Scientist in the Thermodynamics and Kinetics Group at NIST. The program committee will select the remaining talks from submissions to our call for papers. All selected talks will be included in our conference proceedings edited by the program committee. After the talks each day we will provide several rooms for impromptu birds of a feather discussions. Finally, the last two days of the conference will be used for a number of coding sprints on the major software projects in our community. For the 8th consecutive year, the conference will bring together the developers and users of the open source software stack for scientific computing with Python. Attendees have the opportunity to review the available tools and how they apply to specific problems. By providing a forum for developers to share their Python expertise with the wider commercial, academic, and research communities, this conference fosters collaboration and facilitates the sharing of software components, techniques, and a vision for high level language use in scientific computing. For further information, please visit the conference homepage: http://conference.scipy.org. Important Dates --- * Friday, July 3: Abstracts Due * Wednesday, July 15: Announce accepted talks, post schedule * Wednesday, July 22: Early Registration ends * Tuesday-Wednesday, August 18-19: Tutorials * Thursday-Friday, August 20-21: Conference * Saturday-Sunday, August 22-23: Sprints * Friday, September 4: Papers for proceedings due Executive Committee --- * Jarrod Millman, UC Berkeley, USA (Conference Chair) * Gaël Varoquaux, INRIA Saclay, France (Program Co-Chair) * Stéfan van der Walt, University of Stellenbosch, South Africa (Program Co-Chair) * Fernando Pérez, UC Berkeley, USA (Tutorial Chair) ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Scipy Conference 2009 Lecture Recordings
On Fri, Jul 17, 2009 at 10:37 AM, Gökhan SEVERgokhanse...@gmail.com wrote: I think, it would be great to have a similar equipment setup during the SciPy09. Absolutely. It would be *great* to have the tutorials and talks recorded. If anyone steps up to bring equipment, record the talks, and post them, everyone would be very appreciative. If no one offers to do this, it won't happen. If anyone wants to volunteer to take care of this, feel free to contact Gael, Stefan, or I off-list. Jarrod ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] ANN: SciPy 2009 early registration extended to July 22nd
The early registration deadline for SciPy 2009 has been extended until Wednesday, July 22, 2009. Please register ( http://conference.scipy.org/to_register ) by this date to take advantage of the reduced early registration rate. Since we just announced the conference schedule, I was asked to provide extra time for people to register. Fortunately, we were able to get a few extra days from our vendors. But we will have to place orders next Thursday, so this is the last time we will be able to extend the deadline for registration. The conference schedule is available here: http://conference.scipy.org/schedule About the conference SciPy 2009, the 8th Python in Science conference, will be held from August 18-23, 2009 at Caltech in Pasadena, CA, USA. The conference starts with two days of tutorials to the scientific Python tools. There will be two tracks, one for introduction of the basic tools to beginners, and one for more advanced tools. The tutorials will be followed by two days of talks. Both days of talks will begin with a keynote address. The first day’s keynote will be given by Peter Norvig, the Director of Research at Google; while, the second keynote will be delivered by Jon Guyer, a Materials Scientist in the Thermodynamics and Kinetics Group at NIST. The program committee will select the remaining talks from submissions to our call for papers. All selected talks will be included in our conference proceedings edited by the program committee. After the talks each day we will provide several rooms for impromptu birds of a feather discussions. Finally, the last two days of the conference will be used for a number of coding sprints on the major software projects in our community. For the 8th consecutive year, the conference will bring together the developers and users of the open source software stack for scientific computing with Python. Attendees have the opportunity to review the available tools and how they apply to specific problems. By providing a forum for developers to share their Python expertise with the wider commercial, academic, and research communities, this conference fosters collaboration and facilitates the sharing of software components, techniques, and a vision for high level language use in scientific computing. For further information, please visit the conference homepage: http://conference.scipy.org. Important Dates --- * Friday, July 3: Abstracts Due * Wednesday, July 15: Announce accepted talks, post schedule * Wednesday, July 22: Early Registration ends * Tuesday-Wednesday, August 18-19: Tutorials * Thursday-Friday, August 20-21: Conference * Saturday-Sunday, August 22-23: Sprints * Friday, September 4: Papers for proceedings due Executive Committee --- * Jarrod Millman, UC Berkeley, USA (Conference Chair) * Gaël Varoquaux, INRIA Saclay, France (Program Co-Chair) * Stéfan van der Walt, University of Stellenbosch, South Africa (Program Co-Chair) * Fernando Pérez, UC Berkeley, USA (Tutorial Chair) ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] ANN: SciPy 2009 early registration extended to July 17th
The early registration deadline for SciPy 2009 has been extended for one week to July 17, 2009. Please register ( http://conference.scipy.org/to_register ) by this date to take advantage of the reduced early registration rate. About the conference SciPy 2009, the 8th Python in Science conference, will be held from August 18-23, 2009 at Caltech in Pasadena, CA, USA. The conference starts with two days of tutorials to the scientific Python tools. There will be two tracks, one for introduction of the basic tools to beginners, and one for more advanced tools. The tutorials will be followed by two days of talks. Both days of talks will begin with a keynote address. The first day’s keynote will be given by Peter Norvig, the Director of Research at Google; while, the second keynote will be delivered by Jon Guyer, a Materials Scientist in the Thermodynamics and Kinetics Group at NIST. The program committee will select the remaining talks from submissions to our call for papers. All selected talks will be included in our conference proceedings edited by the program committee. After the talks each day we will provide several rooms for impromptu birds of a feather discussions. Finally, the last two days of the conference will be used for a number of coding sprints on the major software projects in our community. For the 8th consecutive year, the conference will bring together the developers and users of the open source software stack for scientific computing with Python. Attendees have the opportunity to review the available tools and how they apply to specific problems. By providing a forum for developers to share their Python expertise with the wider commercial, academic, and research communities, this conference fosters collaboration and facilitates the sharing of software components, techniques, and a vision for high level language use in scientific computing. For further information, please visit the conference homepage: http://conference.scipy.org. Important Dates --- * Friday, July 3: Abstracts Due * Wednesday, July 15: Announce accepted talks, post schedule * Friday, July 17: Early Registration ends * Tuesday-Wednesday, August 18-19: Tutorials * Thursday-Friday, August 20-21: Conference * Saturday-Sunday, August 22-23: Sprints * Friday, September 4: Papers for proceedings due Executive Committee --- * Jarrod Millman, UC Berkeley, USA (Conference Chair) * Gaël Varoquaux, INRIA Saclay, France (Program Co-Chair) * Stéfan van der Walt, University of Stellenbosch, South Africa (Program Co-Chair) * Fernando Pérez, UC Berkeley, USA (Tutorial Chair) ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] ANN: SciPy 2009 student sponsorship
I am pleased to announce that the Python Software Foundation is sponsoring 10 students' travel, registration, and accommodation for the SciPy 2009 conference (Aug. 18-23). The focus of the conference is both on scientific libraries and tools developed with Python and on scientific or engineering achievements using Python. If you're in college or a graduate program, please check out the details here: http://conference.scipy.org/student-funding About the conference SciPy 2009, the 8th Python in Science conference, will be held from August 18-23, 2009 at Caltech in Pasadena, CA, USA. The conference starts with two days of tutorials to the scientific Python tools. There will be two tracks, one for introduction of the basic tools to beginners, and one for more advanced tools. The tutorials will be followed by two days of talks. Both days of talks will begin with a keynote address. The first day’s keynote will be given by Peter Norvig, the Director of Research at Google; while, the second keynote will be delivered by Jon Guyer, a Materials Scientist in the Thermodynamics and Kinetics Group at NIST. The program committee will select the remaining talks from submissions to our call for papers. All selected talks will be included in our conference proceedings edited by the program committee. After the talks each day we will provide several rooms for impromptu birds of a feather discussions. Finally, the last two days of the conference will be used for a number of coding sprints on the major software projects in our community. For the 8th consecutive year, the conference will bring together the developers and users of the open source software stack for scientific computing with Python. Attendees have the opportunity to review the available tools and how they apply to specific problems. By providing a forum for developers to share their Python expertise with the wider commercial, academic, and research communities, this conference fosters collaboration and facilitates the sharing of software components, techniques, and a vision for high level language use in scientific computing. For further information, please visit the conference homepage: http://conference.scipy.org. Important Dates --- * Friday, July 3: Abstracts Due * Friday, July 10: Announce accepted talks, post schedule * Friday, July 10: Early Registration ends * Tuesday-Wednesday, August 18-19: Tutorials * Thursday-Friday, August 20-21: Conference * Saturday-Sunday, August 22-23: Sprints * Friday, September 4: Papers for proceedings due Executive Committee --- * Jarrod Millman, UC Berkeley, USA (Conference Chair) * Gaël Varoquaux, INRIA Saclay, France (Program Co-Chair) * Stéfan van der Walt, University of Stellenbosch, South Africa (Program Co-Chair) * Fernando Pérez, UC Berkeley, USA (Tutorial Chair) ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] SciPy 2009 Call for Papers
== SciPy 2009 Call for Papers == SciPy 2009, the 8th Python in Science conference, will be held from August 18-23, 2009 at Caltech in Pasadena, CA, USA. Each year SciPy attracts leading figures in research and scientific software development with Python from a wide range of scientific and engineering disciplines. The focus of the conference is both on scientific libraries and tools developed with Python and on scientific or engineering achievements using Python. We welcome contributions from the industry as well as the academic world. Indeed, industrial research and development as well academic research face the challenge of mastering IT tools for exploration, modeling and analysis. We look forward to hearing your recent breakthroughs using Python! Submission of Papers The program features tutorials, contributed papers, lightning talks, and bird-of-a-feather sessions. We are soliciting talks and accompanying papers (either formal academic or magazine-style articles) that discuss topics which center around scientific computing using Python. These include applications, teaching, future development directions, and research. A collection of peer-reviewed articles will be published as part of the proceedings. Proposals for talks are submitted as extended abstracts. There are two categories of talks: Paper presentations These talks are 35 minutes in duration (including questions). A one page abstract of no less than 500 words (excluding figures and references) should give an outline of the final paper. Proceeding papers are due two weeks after the conference, and may be in a formal academic style, or in a more relaxed magazine-style format. Rapid presentations These talks are 10 minutes in duration. An abstract of between 300 and 700 words should describe the topic and motivate its relevance to scientific computing. In addition, there will be an open session for lightning talks during which any attendee willing to do so is invited to do a couple-of-minutes-long presentation. If you wish to present a talk at the conference, please create an account on the website (http://conference.scipy.org). You may then submit an abstract by logging in, clicking on your profile and following the Submit an abstract link. Submission Guidelines - * Submissions should be uploaded via the online form. * Submissions whose main purpose is to promote a commercial product or service will be refused. * All accepted proposals must be presented at the SciPy conference by at least one author. * Authors of an accepted proposal can provide a final paper for publication in the conference proceedings. Final papers are limited to 7 pages, including diagrams, figures, references, and appendices. The papers will be reviewed to help ensure the high-quality of the proceedings. For further information, please visit the conference homepage: http://conference.scipy.org. Important Dates === * Friday, June 26: Abstracts Due * Saturday, July 4: Announce accepted talks, post schedule * Friday, July 10: Early Registration ends * Tuesday-Wednesday, August 18-19: Tutorials * Thursday-Friday, August 20-21: Conference * Saturday-Sunday, August 22-23: Sprints * Friday, September 4: Papers for proceedings due Tutorials = Two days of tutorials to the scientific Python tools will precede the conference. There will be two tracks: one for introduction of the basic tools to beginners and one for more advanced tools. Tutorials will be announced later. Birds of a Feather Sessions === If you wish to organize a birds-of-a-feather session to discuss some specific area of scientific development with Python, please contact the organizing committee. Executive Committee === * Jarrod Millman, UC Berkeley, USA (Conference Chair) * Gaël Varoquaux, INRIA Saclay, France (Program Co-Chair) * Stéfan van der Walt, University of Stellenbosch, South Africa (Program Co-Chair) * Fernando Pérez, UC Berkeley, USA (Tutorial Chair) ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] [ANN] Numpy 1.3.0rc2
On Fri, Apr 3, 2009 at 8:18 AM, David Cournapeau da...@ar.media.kyoto-u.ac.jp wrote: I am pleased to announce the release of the rc2 for numpy 1.3.0. I have decided to go for a rc2 instead of the release directly because of the serious mac os X issue. You can find source tarballs and installers for both Mac OS X and Windows on the sourceforge page: Thanks to David and everyone else who worked on this release! I am looking forward to 1.3.0 final. Jarrod ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Is it ok to include GPL scripts in the numpy *repository* ?
On Fri, Mar 27, 2009 at 3:48 AM, David Cournapeau da...@ar.media.kyoto-u.ac.jp wrote: To build the numpy .dmg mac os x installer, I use a script from the adium project, which uses applescript and some mac os x black magic. The script seems to be GPL, as adium itself: Why do you need to use the adium project? I am just curious why the scripts I was using aren't sufficient: http://projects.scipy.org/numpy/browser/trunk/tools/osxbuild Jarrod ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] [SciPy-user] Google summer of Code 2009
On Tue, Mar 10, 2009 at 11:32 AM, Christopher Barker chris.bar...@noaa.gov wrote: hmmm -- I wonder if that is best -- it would put MPL projects in competition with all other python projects. My first thought is that a SciPy application would be best -- with SciPy, numpy, MPL, Sage, Cython, etc, it's plenty big, but would have a bit more focus. I spoke with the SoC coordinator about this last year and was told they would prefer us to stay under the PSF umbrella. This year they plan to sponsor fewer mentoring organizations, I believe (so less chance we would get accepted). Finally, the deadline for submitting an application to be a mentoring organization is Friday (March 13) at 12 noon PDT: http://code.google.com/opensource/gsoc/2009/faqs.html#0_1_mentoring_orgs_52990812492_14255507054617844 ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Update webpage for python requirements for Numpy/SciPy
On Thu, Feb 19, 2009 at 1:24 PM, Bruce Southey bsout...@gmail.com wrote: Hi, Could someone please update the website to clearly state that numpy 1.2 requires Python 2.4 or later? I know it is in the release notes but that assumes people read them :-) It would be great to state this on the download and installation pages: http://www.scipy.org/Download http://www.scipy.org/Installing_SciPy Also there should be a mention that nose is required at for testing. A couple of dated material that I noticed are: http://www.scipy.org/Installing_SciPy/BuildingGeneral 'To build SciPy, Python version 2.3 or newer is required.' The FAQ page (http://www.scipy.org/FAQ) NumPy/SciPy installation 'Prerequisities NumPy requires the following software installed: 1. Python 2.3.x or 2.4.x or 2.5.x ' It is extremely difficult to keep track of the numerous pages that explain what the requirements are and how to build and install everything. I would love it if someone would volunteer to add this information to the user documentation for numpy: http://docs.scipy.org/doc/numpy/user/ and scipy: http://docs.scipy.org/doc/scipy/reference/(maybe in the tutorial)? Then we can just link to the relevant authoritative site on as many pages as we want. Since the docs are checked into the source code, it will be much easier--and more likely--that developers will update this information will they are working on the code. Unfortunately I don't have the time to do this myself, but I would be extremely appreciative if some else was able to take the time to do this. It would be very useful. You could start here: http://projects.scipy.org/scipy/scipy/browser/trunk/INSTALL.txt http://projects.scipy.org/scipy/numpy/browser/trunk/INSTALL.txt And the integrate the various information from the other sites listed above. As soon as the information is moved from the wiki to the official docs, you could replace the source pages with links to the official, authoritative site. I am thinking the final version would look something like this: http://neuroimaging.scipy.org/site/doc/manual/html/users/installation.html http://neuroimaging.scipy.org/site/doc/manual/html/devel/install/index.html Of course, the information might not always be correct; but if there is one authoritative site where everyone can point out things that are broken or don't work, it hopefully won't take too long to get everything in good shape. So if you are up to the challenge, I would recommend just merging everything to start and not worrying to much about testing and verifying that everything works correctly before starting. Thanks, Jarrod ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] ANN: SciPy 0.7.0
I'm pleased to announce SciPy 0.7.0. SciPy is a package of tools for science and engineering for Python. It includes modules for statistics, optimization, integration, linear algebra, Fourier transforms, signal and image processing, ODE solvers, and more. This release comes sixteen months after the 0.6.0 release and contains many new features, numerous bug-fixes, improved test coverage, and better documentation. Please note that SciPy 0.7.0 requires Python 2.4 or greater (but not Python 3) and NumPy 1.2.0 or greater. For information, please see the release notes: https://sourceforge.net/project/shownotes.php?release_id=660191group_id=27747 You can download the release from here: https://sourceforge.net/project/showfiles.php?group_id=27747package_id=19531release_id=660191 Thank you to everybody who contributed to this release. Enjoy, Jarrod Millman ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] A buildbot farm with shell access - for free ?
On Wed, Jan 28, 2009 at 6:11 PM, David Cournapeau da...@ar.media.kyoto-u.ac.jp wrote: It is said in the email that this is reserved to the python project, and prominent python projects like Twisted and Django. Would it be ok to try to be qualified as a prominent python project as well ? That would be great. ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] failure
On Wed, Jan 21, 2009 at 10:53 AM, Gideon Simpson simp...@math.toronto.edu wrote: == FAIL: test_umath.TestComplexFunctions.test_against_cmath -- Traceback (most recent call last): File /usr/local/nonsystem/simpson/lib/python2.5/site-packages/nose/ case.py, line 182, in runTest self.test(*self.arg) File /usr/local/nonsystem/simpson/lib/python2.5/site-packages/ numpy/core/tests/test_umath.py, line 268, in test_against_cmath assert abs(a - b) atol, %s %s: %s; cmath: %s%(fname,p,a,b) AssertionError: arcsinh -2j: (-1.31695789692-1.57079632679j); cmath: (1.31695789692-1.57079632679j) -- Ran 1740 tests in 9.839s FAILED (KNOWNFAIL=1, failures=1) nose.result.TextTestResult run=1740 errors=0 failures=1 How would you recommend I troubleshoot this? How seriously should I take it? This is with a fresh Python 2.5.4 installation too. I think it is a problem with cmath and should probably be marked as a knownfailure: http://bugs.python.org/issue1381 ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Trying to implement the array interface
On Wed, Jan 14, 2009 at 3:17 AM, Mark Asbach asb...@ient.rwth-aachen.de wrote: I'm currently extending the Python wrapper for the Open Computer Vision Library (opencv) with the goal to interface numerical libraries as seemless as possible. Unfortunately, it doesn't seem to be that easy ;-) This is really great. Thanks for working on this. - pymat: didn't check. Seems to use Numeric, test results cover Numeric 23 and Matlab 6.5 only, so this package might be dead? It is pretty much dead. Take a look at the mlabwrap scikit: http://scikits.appspot.com/mlabwrap mlabwrap hasn't been updated since 2007, but it works pretty well, supports numpy, and is much better than pymat. Jarrod ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] remove need for site.cfg on default
Due to the fact that I was tired of adding site.cfg to scipy and numpy when building on Fedora and Ubuntu systems as well as a scipy ticket (http://scipy.org/scipy/numpy/ticket/985), I decided to try and add default system paths to numpy.distutils. You can find out more details on this ticket: http://projects.scipy.org/scipy/scipy/ticket/817 I would like to have as many people test this as possible. So I would like everyone, who has had to build numpy/scipy with a site.cfg despite having installed all the dependencies in the system default locations, to test this. If you would please update to the numpy trunk and build numpy and scipy without your old site.cfg. Regardless of whether it works or not, I would appreciate it if you could let me know. Thanks, Jarrod ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Removal of deprecated test framework stuff
On Wed, Dec 31, 2008 at 2:53 AM, Alan McIntyre alan.mcint...@gmail.com wrote: Unless somebody objects, I'd like to remove from NumPy 1.3 the following numpy.testing items that were deprecated in NumPy 1.2 (since the warnings promise we'll do so ;): - ParametricTestCase (also removing the entire file numpy/testing/parametric.py) - The following arguments from numpy.testing.Tester.test() (which is used for module test functions): level, verbosity, all, sys_argv, testcase_pattern - Path manipulation functions: set_package_path, set_local_path, restore_path - NumpyTestCase, NumpyTest Thanks for taking care of this. Jarrod ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] numpy on windows x64 with mingw: it (almost) works
On Sun, Dec 21, 2008 at 12:13 AM, David Cournapeau da...@ar.media.kyoto-u.ac.jp wrote: Just a few words to mention that I've finally managed to build numpy with the mingw-w64 project (port of mingw to AMD 64 bits MS OS), and it almost run OK. Thanks for working on this. Jarrod ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] unique1d docs
On Mon, Dec 15, 2008 at 8:37 PM, josef.p...@gmail.com wrote: What's the future of the example list, on the example list with docs it says Numpy 1.0.4. It hasn't been updated in a while. When I started out with numpy, I used it as a main reference, but now, some examples, that I wanted to look at, had outdated function signature. At some point, we should make sure everything is in the new docs. Maybe we should lock down the pages for editing, point everyone to the new docs.scipy.org webpage, and then eventually make sure everything is the new docs and remove the old pages. For me, the new docs are now more usable than the example list. I was thinking of starting an example list for scipy.stats, but I guess the effort is better placed in improving the new docs. Yes. Please don't start new moin wiki documentation. We have a good solution for documentation that didn't exist when the moin documentation was started. Either put new docs in the docstrings or in the scipy tutorial. Thanks, -- Jarrod Millman Computational Infrastructure for Research Labs 10 Giannini Hall, UC Berkeley phone: 510.643.4014 http://cirl.berkeley.edu/ ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] genloadtxt : last call
there has been some recent activity in this area I thought I'd mention it. As always--thanks to everyone who is actually putting in hard work! Sorry I am not offering to actually help out here, but I hope that someone will be interested and able to pursue some of these issues. Thanks again, Jarrod On Thu, Dec 4, 2008 at 3:41 PM, Jarrod Millman [EMAIL PROTECTED] wrote: I am not familiar with this, but it looks quite useful: http://www.stecf.org/software/PYTHONtools/astroasciidata/ or (http://www.scipy.org/AstroAsciiData) Within the AstroAsciiData project we envision a module which can be used to work on all kinds of ASCII tables. The module provides a convenient tool such that the user easily can: * read in ASCII tables; * manipulate table elements; * save the modified ASCII table; * read and write meta data such as column names and units; * combine several tables; * delete/add rows and columns; * manage metadata in the table headers. Is anyone familiar with this package? Would make sense to investigate including this or adopting some of its interface/features? ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] Please help prepare the SciPy 0.7 release notes
We are almost ready for SciPy 0.7.0rc1 (we just need to sort out the Numerical Recipes issues and I haven't had time to look though them yet). So I wanted to ask once more for help with preparing the release notes: http://projects.scipy.org/scipy/scipy/browser/trunk/doc/release/0.7.0-notes.rst There have been numerous improvements and changes. As always I would appreciate any feedback about mistakes or omissions. It would also be nice to know how many tests were in the last release and how many are there now. Highlighting major bug fixes or pointing out know issues would be very useful. I would also like to ask if anyone would be interested in stepping forward to work on something like Andrew Kuchling's What's New in Python : http://docs.python.org/whatsnew/2.6.html This would be a great area to contribute. The release notes provide visibility for our developers' immense contributions of time and effort. They help provide an atmosphere of momentum, maturity, and excitement to a project. It is also a great service to users who haven't been following the trunk closely as well as other developer's who have missed what is happening in other areas of the code. It is also becomes a nice historical artifact for the future. It would be great if someone wanted to contribute in this way. Ideally, I would like to have someone who be interested in doing this for several releases of scipy and numpy. Such a person could develop a standard template for this and write some scripts to gather specific statistics (e.g., how many lines of code have changed, how many unit tests were added, what is the test coverage, what is the docstring coverage, who were the top contributors, who has increased their code contributions the most, how many new developers, etc.) Just a thought. Figure it won't happen, if I don't ask. Thanks, -- Jarrod Millman Computational Infrastructure for Research Labs 10 Giannini Hall, UC Berkeley phone: 510.643.4014 http://cirl.berkeley.edu/ ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Python2.4 support
On Sun, Dec 7, 2008 at 12:02 PM, Pierre GM [EMAIL PROTECTED] wrote: * What versions of Python should be supported by what version of numpy ? Are we to expect users to rely on Python2.5 for the upcoming 1.3.x ? Could we have some kind of timeline on the trac site or elsewhere (and if such a timeline exists already, can I get the link?) ? NumPy 1.3.x should work with Python 2.4, 2.5, and 2.6. At some point we can drop 2.4, but I would like to wait a bit since we just dropped 2.3 support. The timeline is on the trac site: http://projects.scipy.org/scipy/numpy/milestone/1.3.0 * Talking about 1.3.x, what's the timeline? Are we still shooting for a release in 2008 or could we wait till mid Jan. 2009 ? I am fine with pushing the release back, if there is interest in doing that. I have been mainly focusing on getting SciPy 0.7.x out, so I haven't been following the NumPy development closely. But it is good that you are asking for more concrete details about the next NumPy release. We need to start making plans. Does anyone have any suggestions about whether we should push the release back? Is 1 month long enough? What is left to do? Please feel free to update the release notes, which are checked into the trunk: http://scipy.org/scipy/numpy/browser/trunk/doc/release/1.3.0-notes.rst Thanks, -- Jarrod Millman Computational Infrastructure for Research Labs 10 Giannini Hall, UC Berkeley phone: 510.643.4014 http://cirl.berkeley.edu/ ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Python2.4 support
On Sun, Dec 7, 2008 at 9:42 PM, David Cournapeau [EMAIL PROTECTED] wrote: I am strongly against dropping 2.4 support anytime soon. I haven't seen a strong rationale for using = 2.5 features in numpy, supporting 2.4 is not so hard, and 2.4 is still the default python version on many OS (mac os X 10.4 I believe, RHEL for sure, open solaris). While my feelings aren't as strong as David's, they are pretty much identical. As a point of reference, Red Hat Enterprise Linux 6 won't come out until at least the first quarter of 2010. Until then we should make a serious effort to support Python 2.4, which ships with RHEL 5. It looks like RHEL 6 will be based on the upcoming Fedora 11 release, which will ship with Python 2.6. That gives us a minimum of one year for 2.4 support. Once RHEL 6 is released, it will take several months before a sizable number of users upgrade. Moin has a detailed list of Python versions for various OSes and hosting services: http://moinmo.in/PollAboutRequiringPython24 -- Jarrod Millman Computational Infrastructure for Research Labs 10 Giannini Hall, UC Berkeley phone: 510.643.4014 http://cirl.berkeley.edu/ ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] in(np.nan) on python 2.6
On Thu, Dec 4, 2008 at 11:14 AM, Pierre GM [EMAIL PROTECTED] wrote: Raise a ValueError (even in 2.5, therefore risking to break something) +1 -- Jarrod Millman Computational Infrastructure for Research Labs 10 Giannini Hall, UC Berkeley phone: 510.643.4014 http://cirl.berkeley.edu/ ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Py3k and numpy
On Thu, Dec 4, 2008 at 12:15 PM, Tommy Grav [EMAIL PROTECTED] wrote: On Dec 4, 2008, at 2:03 PM, Robert Kern wrote: It does. What problems are people seeing? Is it just the Windows build that causes people to say numpy doesn't work with Python 2.6? There is currently no official Mac OSX binary for numpy for python 2.6, but you can build it from source. Is there any time table for generating a 2.6 Mac OS X binary? My intention was to make 2.6 Mac binaries for the NumPy 1.3 release. We haven't finalized a timetable for the 1.3 release yet, but the current plan was to try and get the release out near the end of December. Once SciPy 0.7 is out, I will turn my attention to the next NumPy release. -- Jarrod Millman Computational Infrastructure for Research Labs 10 Giannini Hall, UC Berkeley phone: 510.643.4014 http://cirl.berkeley.edu/ ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] genloadtxt: second serving
I am not familiar with this, but it looks quite useful: http://www.stecf.org/software/PYTHONtools/astroasciidata/ or (http://www.scipy.org/AstroAsciiData) Within the AstroAsciiData project we envision a module which can be used to work on all kinds of ASCII tables. The module provides a convenient tool such that the user easily can: * read in ASCII tables; * manipulate table elements; * save the modified ASCII table; * read and write meta data such as column names and units; * combine several tables; * delete/add rows and columns; * manage metadata in the table headers. Is anyone familiar with this package? Would make sense to investigate including this or adopting some of its interface/features? -- Jarrod Millman Computational Infrastructure for Research Labs 10 Giannini Hall, UC Berkeley phone: 510.643.4014 http://cirl.berkeley.edu/ ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] 2D phase unwrapping
On Tue, Nov 25, 2008 at 11:17 PM, Nadav Horesh [EMAIL PROTECTED] wrote: I read a presentation by GERI (http://www.ljmu.ac.uk/GERI) that their code is implemented in scipy, but I could not find it. One of my colleagues has been using 2D and 3D phase unwrapping code from Munther Gdeisat from GERI: https://cirl.berkeley.edu/trac/browser/bic/trunk/recon-tools/src https://cirl.berkeley.edu/trac/browser/bic/trunk/recon-tools/root/recon/punwrap This code is very high quality and replicating it from scratch would be a fairly daunting task. I was hoping to get this code integrated into SciPy, but no one in my group has had time to do this. Munther Gdeisat and I spoke on the phone and had an email exchange about relicensing his code and integrating it into SciPy. Munther was very interested in having this happen and had some discussions with the Institute Director to get permission for relicencing the code. I have appended our email exchange below. If anyone is interested in picking this up and going through the effort of incorporating this code in scipy I would be happy to help resolve any remaining licensing issues. I also may be able to devote some programming resources to helping out, if someone else volunteers to do the majority of the work. Thanks, -- Forwarded message -- From: Gdeisat, Munther [EMAIL PROTECTED] Date: Fri, Sep 28, 2007 at 1:07 PM Subject: RE: 3D phase unwrap To: Jarrod Millman [EMAIL PROTECTED] Cc: Daniel Sheltraw [EMAIL PROTECTED], Travis E. Oliphant [EMAIL PROTECTED] Dear Jarrod, On behalf of the General Engineering Research Institute (GERI), Liverpool John Moores University, UK, I am very happy to license our 2D and 3D phase unwrappers to use in your NumPy and SciPy libraries. I spoke with this matter with the director of our institute (GERI), prof. Burton, and he is also happy to license the code for both libraries mentioned above. But myself and Prof. Burton would like to stress on the following issues 1- We disclaims all responsibility for the use which is made of the Software. We further disclaim any liability for the outcomes arising from using the Software. 2-We are not obliged to update the software or give any support to the users of the software. We generally help researchers around the world but we are not obliged to do that. Following our phone call, you mentioned to me that you already have these two points mentioned in the license of both libraries. So, I can confirm you that you can include our software in your library. Yours Truly, Dr. Munther Gdeisat The General Engineering Research Institute (GERI) Liverpool John Moores University, UK From: [EMAIL PROTECTED] on behalf of Jarrod Millman Sent: Fri 9/28/2007 9:54 PM To: Gdeisat, Munther Cc: Daniel Sheltraw; Travis E. Oliphant Subject: Re: 3D phase unwrap Hello Munther, It was good to speak to you on the phone. I am happy that you will be able to relicense your code for us. Here is the license we use: http://projects.scipy.org/scipy/scipy/browser/trunk/LICENSE.txt It should address all your concerns. Feel free to let me know if you have any questions about it. Thanks, -- Jarrod Millman Computational Infrastructure for Research Labs 10 Giannini Hall, UC Berkeley phone: 510.643.4014 http://cirl.berkeley.edu/ From: [EMAIL PROTECTED] on behalf of Jarrod Millman Sent: Fri 9/28/2007 3:02 AM To: Gdeisat, Munther Cc: Daniel Sheltraw; Travis E. Oliphant Subject: Re: 3D phase unwrap On 9/26/07, Gdeisat, Munther [EMAIL PROTECTED] wrote: Firstly, I would like to than Daniel to bring us together. I am happy to include the 2D and 3D phase unwrappers in the NumPy/SciPy project. If you need any help regarding this matter such as documentation, I am happy to do so. Kind regards. Hello Munther, I am very excited about the possibility of getting your 2D and 3D phase unwrappers incorporated into SciPy (http://www.scipy.org/ http://www.scipy.org/ ). Travis Oliphant (the main author of NumPy and a major contributor to SciPy) spoke about where your phase unwrapping coding would best fit, and we both agreed that they belong in SciPy. NumPy and SciPy are both part of the same technology stack. We try to keep NumPy as lean as possible leaving SciPy to provide a more comprehensive set of tools. Here is an article about NumPy/SciPy written by Travis from a recent special issue of IEEE's Computing in Science and Engineering, which was devoted to Python for scientific programming: http://www.computer.org/portal/cms_docs_cise/cise/2007/n3/10-20.pdf http://www.computer.org/portal/cms_docs_cise/cise/2007/n3/10-20.pdf Anyway, I am the current release manager of SciPy and am eager to get your phase unwrappers incorporated ASAP. Phase unwrapping is currently missing from SciPy and Daniel has spoken very highly of your algorithms and code. The only potential issue I see involves the licensing. Both SciPy and NumPy
[Numpy-discussion] ANN: SciPy 0.7.0b1 (beta release)
I'm pleased to announce the first beta release of SciPy 0.7.0. SciPy is a package of tools for science and engineering for Python. It includes modules for statistics, optimization, integration, linear algebra, Fourier transforms, signal and image processing, ODE solvers, and more. This beta release comes almost one year after the 0.6.0 release and contains many new features, numerous bug-fixes, improved test coverage, and better documentation. Please note that SciPy 0.7.0b1 requires Python 2.4 or greater and NumPy 1.2.0 or greater. For information, please see the release notes: http://sourceforge.net/project/shownotes.php?group_id=27747release_id=642769 You can download the release from here: http://sourceforge.net/project/showfiles.php?group_id=27747package_id=19531release_id=642769 Thank you to everybody who contributed to this release. Enjoy, -- Jarrod Millman Computational Infrastructure for Research Labs 10 Giannini Hall, UC Berkeley phone: 510.643.4014 http://cirl.berkeley.edu/ ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] status of numpy 1.3.0
Now that scipy 0.7.0b1 has been tagged, I wanted to start planning for the NumPy 1.3.0: http://projects.scipy.org/scipy/numpy/milestone/1.3.0 The original plan was to release 1.3 at the end of November. At this point, we are going to have to push back the release date a bit. I would like to get 1.3 out ASAP, so I would like aim for the third week of December. This is how I see the current development trunk: * 2.6 compatablity (Linux 32- and 64-bit done, Windows 32-bit done, Mac 32-bit done) * Generalized Ufuncs (committed) * Ufunc clean-up (committed) * Refactoring numpy.core math configuration (?? bump to 1.4 ??) * Improvements to build warnings (?? bump to 1.4 ??) * Histogram (committed) * NumPy testing improvements (http://projects.scipy.org/scipy/numpy/ticket/957) * Documentation improvements * MaskedArray improvements * Bugfixes Am I missing anything? Is there anything else that we should get in before releasing 1.3? Does it seem reasonable that we could release 1.3 during the third week of December? Who will have time to work on NumPy for the next month? Thanks, -- Jarrod Millman Computational Infrastructure for Research Labs 10 Giannini Hall, UC Berkeley phone: 510.643.4014 http://cirl.berkeley.edu/ ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Proposal for changing the names of inverse trigonometrical/hyperbolic functions
On Mon, Nov 24, 2008 at 10:45 AM, Francesc Alted [EMAIL PROTECTED] wrote: So, IMHO, I think it would be better to rename the inverse trigonometric functions from ``arc*`` to ``a*`` prefix. Of course, in order to do that correctly, one should add the new names and add a ``DeprecationWarning`` informing that people should start to use the new names. After two or three NumPy versions, the old function names can be removed safely. What people think? +1 It seems there is a fair amount of favor for adding the new names. There is some resistance to removing the old ones. I would be happy to deprecate the old ones, but leave them in until we release a new major release (i.e., NumPy 2.0.0). We could start creating a list of API/ABI clean-ups for whenever we find a compelling reason to release a new major version. In the meantime, we can leave the old names in and just add a deprecation note to the docs. Once we are ready to release 2.0, we can release a 1.x with deprecation warnings. -- Jarrod Millman Computational Infrastructure for Research Labs 10 Giannini Hall, UC Berkeley phone: 510.643.4014 http://cirl.berkeley.edu/ ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Numpy 1.2.2 ?
On Sun, Nov 23, 2008 at 11:41 PM, Charles R Harris [EMAIL PROTECTED] wrote: I'd like to do a 1.1.2 release for the Python 2.3 user(s) to get out some fixes for Python 2.3 that went in after the last release. I don't want to do any more than that, although if something can be copied straight over that might be a go. +1. I am happy to help out with this too. How soon do you want to release 1.1.2? I could help later this week. If you can get the branch ready and take care of the release notes, I can take care of everything after that. It would also be great if you could help figure out what needs to be back-ported from the trunk to the 1.2.x branch. Thanks, -- Jarrod Millman Computational Infrastructure for Research Labs 10 Giannini Hall, UC Berkeley phone: 510.643.4014 http://cirl.berkeley.edu/ ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] added nep for generalized ufuncs
http://projects.scipy.org/scipy/numpy/browser/trunk/doc/neps/generalized-ufuncs.rst Please feel free to add to this or improve it as you see fit. Thanks, -- Jarrod Millman Computational Infrastructure for Research Labs 10 Giannini Hall, UC Berkeley phone: 510.643.4014 http://cirl.berkeley.edu/ ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Changes to histogram semantics: follow-up
On Wed, Nov 12, 2008 at 12:58 PM, David Huard [EMAIL PROTECTED] wrote: Revision 6020 proceeds with the planned changes to histogram semantics for the 1.3 release. Thanks, -- Jarrod Millman Computational Infrastructure for Research Labs 10 Giannini Hall, UC Berkeley phone: 510.643.4014 http://cirl.berkeley.edu/ ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] License review, cont.
Now that I have removed all GPL/LGPL code from scipy, I wanted to double check on the licenses of some NumPy code. In particular, 1. FreeBSD license: http://projects.scipy.org/scipy/numpy/browser/trunk/numpy/core/include/numpy/fenv/fenv.c http://projects.scipy.org/scipy/numpy/browser/trunk/numpy/core/include/numpy/fenv/fenv.h 2. Python license: SafeEval class in http://projects.scipy.org/scipy/numpy/browser/trunk/numpy/lib/utils.py Is there any need to look into getting the authors to re-license their code? The license are pretty liberal (and both look like they are compatible with the revised BSD license), but I thought I'd ask anyway. Should we note the additional licenses in: http://projects.scipy.org/scipy/numpy/browser/trunk/LICENSE.txt I was imagining something like: http://projects.scipy.org/scipy/scipy/browser/trunk/scipy/weave/LICENSE.txt Thanks, -- Jarrod Millman Computational Infrastructure for Research Labs 10 Giannini Hall, UC Berkeley phone: 510.643.4014 http://cirl.berkeley.edu/ ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Simplifying compiler optimization flags logic (fortran compilers)
On Sat, Nov 1, 2008 at 1:07 AM, Robert Kern [EMAIL PROTECTED] wrote: On Fri, Oct 31, 2008 at 05:25, David Cournapeau [EMAIL PROTECTED] wrote: I was wondering whether it was really worth having a lot of magic going on in fcompilers for flags like -msse2 and co (everything done in get_flags_arch, for example). It is quite fragile (we had several problems wrt buggy compilers, buggy CPU detection), and I am not sure it buys us much anyway. Did some people notice a difference between gfortran -O3 -msse2 and gfortran -O3 ? You're probably right. I think it is probably best to take out some of the magic in fcompilers as well. -- Jarrod Millman Computational Infrastructure for Research Labs 10 Giannini Hall, UC Berkeley phone: 510.643.4014 http://cirl.berkeley.edu/ ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] ANN: NumPy 1.2.1
I'm pleased to announce the release of NumPy 1.2.1. NumPy is the fundamental package needed for scientific computing with Python. It contains: * a powerful N-dimensional array object * sophisticated (broadcasting) functions * basic linear algebra functions * basic Fourier transforms * sophisticated random number capabilities * tools for integrating Fortran code. Besides it's obvious scientific uses, NumPy can also be used as an efficient multi-dimensional container of generic data. Arbitrary data-types can be defined. This allows NumPy to seamlessly and speedily integrate with a wide-variety of databases. This bugfix release comes almost one month after the 1.2.0 release. Please note that NumPy 1.2.1 requires Python 2.4 or greater. For information, please see the release notes: https://sourceforge.net/project/shownotes.php?release_id=636728group_id=1369 You can download the release from here: https://sourceforge.net/project/showfiles.php?group_id=1369 Thank you to everybody who contributed to this release. Enjoy, -- Jarrod Millman Computational Infrastructure for Research Labs 10 Giannini Hall, UC Berkeley phone: 510.643.4014 http://cirl.berkeley.edu/ ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] NumPy 1.2.1 to be tagged 10/28/08
Hey, I plan to release NumPy 1.2.1 before the SciPy 0.7 sprint that Stefan is organizing for Nov. 1-2. So I will be tagging the release on Wednesday, Oct. 29th. Is anyone planning to back port anymore fixes to the 1.2.x branch? If so, please do so by Tuesday, Oct. 28th. Here is what has been back ported (http://projects.scipy.org/scipy/numpy/log/branches/1.2.x): bug fix for subclassing object arrays: http://projects.scipy.org/scipy/numpy/changeset/5891 MaskedArray fixes: http://projects.scipy.org/scipy/numpy/changeset/5936 http://projects.scipy.org/scipy/numpy/changeset/5948 Python 2.4 compatible lookfor: http://projects.scipy.org/scipy/numpy/changeset/5945 Setuptools fix: http://projects.scipy.org/scipy/numpy/changeset/5956 Thanks, -- Jarrod Millman Computational Infrastructure for Research Labs 10 Giannini Hall, UC Berkeley phone: 510.643.4014 http://cirl.berkeley.edu/ ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] docs.scipy.org -- new site for the documentation marathon
Thanks so much for doing this. It looks great. On Sun, Oct 26, 2008 at 7:13 AM, Pauli Virtanen [EMAIL PROTECTED] wrote: Now, the role of docs.scipy.org warrants discussion, because on the one hand, the domain docs.scipy.org looks very official, and on the other hand, scipy.org/Documentation claims to be the place for official documentation. What do you think: should we use the current front page of docs.scipy.org, shifting the focus and entry point of documentation to the Sphinx-generated pages, or still keep the focus on the Moin wiki at scipy.org? docs.scipy.org should be the official documentation. The Moin wiki documentation served its purpose, but now there is something much better. I propose that the 'Documentation' sidebar on http://www.scipy.org/ point to http://docs.scipy.org. Eventually, I would like to see all the content from http://www.scipy.org/Documentation move into the Sphinx-based system (and then we can just delete the Moin page). Until that happens we can just leave the link on http://docs.scipy.org to http://www.scipy.org/. Also I have cross-posted my response to the numpy list, but let's have this discussion on the scipy developer's list going forward. Thanks, -- Jarrod Millman Computational Infrastructure for Research Labs 10 Giannini Hall, UC Berkeley phone: 510.643.4014 http://cirl.berkeley.edu/ ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] windows install problem for 1.2
On Mon, Oct 20, 2008 at 8:38 PM, David Cournapeau : This is the first time I heard of this problem. I guess you checked the obvious (do you have enough ram). What is your platform exactly ? Did you check your installer is ok ? Something I should have done is to provide for a checksum: here is the checksum for the time being: ad603ad13cf403fbf394d7e3eba8b996 numpy-1.2.0-win32-superpack-python2.5.exe The md5 checksums are also in the release notes (which you can find by clicking on the little notepad by the release on the download page). Here are the release notes for the 1.2.0 release: http://sourceforge.net/project/shownotes.php?group_id=1369release_id=628858 Of course, that is terribly difficult to find. I haven't been able to figure out a better way to have sourceforge display checksum information. Ideally, they could display the checksum information like they do for the filesize and architecture information: http://sourceforge.net/project/showfiles.php?group_id=1369package_id=175103release_id=628858 If anyone knows how to make sourceforge display this information, please let me know. I would also like it if you could somehow embed the checksum in the URL. Maybe something like this: https://wiki.mozilla.org/Firefox/Feature_Brainstorming:Downloads#MD5_Checksum -- Jarrod Millman Computational Infrastructure for Research Labs 10 Giannini Hall, UC Berkeley phone: 510.643.4014 http://cirl.berkeley.edu/ ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] windows install problem for 1.2
On Tue, Oct 21, 2008 at 2:23 AM, Francesc Alted [EMAIL PROTECTED] wrote: I normally put the MD5 information in a separate file in the same repository. I was thinking about doing something like that, but I have been trying to minimize the number of files that I upload to sourceforge, because each file requires a ridiculous number of mouse clicks. The whole process of making a file release on sourceforge is annoyingly manual. Of course, I should actually just figure out how to script making a release on sourceforge. I have seen a couple of tools that look like they might be useful: Releaseforge: http://releaseforge.sourceforge.net/ Sourceforge Utilities: http://sfutils.sourceforge.net/ Has anyone found a good way of scripting sourceforge? Thanks, -- Jarrod Millman Computational Infrastructure for Research Labs 10 Giannini Hall, UC Berkeley phone: 510.643.4014 http://cirl.berkeley.edu/ ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] windows install problem for 1.2
On Tue, Oct 21, 2008 at 2:28 AM, David Cournapeau [EMAIL PROTECTED] wrote: What do we use sourceforge for now ? It seems that we only use it for the source/installers archives, now, right ? We use sourceforge neither for ML, Forums, bug tracking or source code control, so why using it at all ? I don't mind hosting them somewhere else. Do you have some place in mind? Google Code looks like it has a 10MB file size limit: http://code.google.com/support/bin/answer.py?answer=56621topic=10456 Launchpad seems to be considering upping their limit to 200MB: https://bugs.launchpad.net/launchpad-foundations/+bug/254052 The scipy server can't handle the load or bandwidth needed. My first inclination would be to look at Launchpad: https://launchpad.net/numpy https://launchpad.net/scipy How do you like releasing files on launchpad? Can you write a script to upload release files and notes? Can you script making the announcement? It looks like they md5 support builtin: https://code.launchpad.net/numpy.scons.support/+download Ideas? Comments? -- Jarrod Millman Computational Infrastructure for Research Labs 10 Giannini Hall, UC Berkeley phone: 510.643.4014 http://cirl.berkeley.edu/ ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Please backport fixes to the 1.2.x branch
On Sun, Oct 5, 2008 at 7:59 PM, Jarrod Millman [EMAIL PROTECTED] wrote: I would like to get a 1.2.1 release out ASAP. There are several bug-fixes on the trunk that need to be backported. If you have made a bug-fix to the trunk that you have been waiting to backport to the 1.2.x branch, please do so now: http://svn.scipy.org/svn/numpy/branches/1.2.x Ideally, I would like to freeze the branch for the 1.2.1 release in about 1 week. Please let me know if you need more time or if there is something in particular that you would like to see backported. Hey, Is anyone planning to back port anymore fixes to the 1.2.x branch? So this is all that has been back ported: bug fix for subclassing object arrays: http://projects.scipy.org/scipy/numpy/changeset/5891 MaskedArray fixes: http://projects.scipy.org/scipy/numpy/changeset/5936 Python 2.4 compatible lookfor: http://projects.scipy.org/scipy/numpy/changeset/5945 -- Jarrod Millman Computational Infrastructure for Research Labs 10 Giannini Hall, UC Berkeley phone: 510.643.4014 http://cirl.berkeley.edu/ ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Please backport fixes to the 1.2.x branch
I would also like to back port revision 5833: http://projects.scipy.org/scipy/numpy/changeset/5833 Are there any other fixes that should be back ported? -- Jarrod Millman Computational Infrastructure for Research Labs 10 Giannini Hall, UC Berkeley phone: 510.643.4014 http://cirl.berkeley.edu/ ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Merged clean_math_config branch
On Sun, Oct 5, 2008 at 1:25 AM, David Cournapeau [EMAIL PROTECTED] wrote: Just to mention that I merged back my changes from the clean_math_config branch into trunk. The main point of the branch is to clean our math configuration. If this causes problems, please report it. I built and tested on mac os x, linux 32 bits and windows (both mingw32 and VS 2003). It breaks windows 64 bits ATM, but this will be fixed soon. The numscons built is broken as well, but the missing features are already backported from numpy.distutils to numscons; a new working version of numscons is about to be released. Excellent. Thanks for working on this. -- Jarrod Millman Computational Infrastructure for Research Labs 10 Giannini Hall, UC Berkeley phone: 510.643.4014 http://cirl.berkeley.edu/ ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] Please backport fixes to the 1.2.x branch
Hello, I would like to get a 1.2.1 release out ASAP. There are several bug-fixes on the trunk that need to be backported. If you have made a bug-fix to the trunk that you have been waiting to backport to the 1.2.x branch, please do so now: http://svn.scipy.org/svn/numpy/branches/1.2.x Ideally, I would like to freeze the branch for the 1.2.1 release in about 1 week. Please let me know if you need more time or if there is something in particular that you would like to see backported. Thanks, -- Jarrod Millman Computational Infrastructure for Research Labs 10 Giannini Hall, UC Berkeley phone: 510.643.4014 http://cirl.berkeley.edu/ ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] 1.2.0rc2 tagged! --PLEASE TEST--
On Fri, Oct 3, 2008 at 12:35 AM, Francesc Alted [EMAIL PROTECTED] wrote: It would be nice if you can update the PYPI package index too. Perhaps having a list of places on where to announce NumPy on every release would be handy. Done. Thanks, -- Jarrod Millman Computational Infrastructure for Research Labs 10 Giannini Hall, UC Berkeley phone: 510.643.4014 http://cirl.berkeley.edu/ ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] 1.2.0rc2 tagged! --PLEASE TEST--
On Thu, Oct 2, 2008 at 4:29 PM, Chris Barker [EMAIL PROTECTED] wrote: Robert Kern wrote: Superceded by the 1.2.0 release. See the thread ANN: NumPy 1.2.0. I thought I'd seen that, but when I went to: http://www.scipy.org/Download And I still got 1.1 I updated the page to point to the sourceforge page. Thanks for catching that. -- Jarrod Millman Computational Infrastructure for Research Labs 10 Giannini Hall, UC Berkeley phone: 510.643.4014 http://cirl.berkeley.edu/ ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] ANN: NumPy 1.2.0
I'm pleased to announce the release of NumPy 1.2.0. NumPy is the fundamental package needed for scientific computing with Python. It contains: * a powerful N-dimensional array object * sophisticated (broadcasting) functions * basic linear algebra functions * basic Fourier transforms * sophisticated random number capabilities * tools for integrating Fortran code. Besides it's obvious scientific uses, NumPy can also be used as an efficient multi-dimensional container of generic data. Arbitrary data-types can be defined. This allows NumPy to seamlessly and speedily integrate with a wide-variety of databases. This minor release comes almost four months after the 1.1.0 release. The major features of this release are a new testing framework and huge amount of documentation work. It also includes a some minor API breakage scheduled in the 1.1 release. Please note that NumPy 1.2.0 requires Python 2.4 or greater. For information, please see the release notes: http://sourceforge.net/project/shownotes.php?group_id=1369release_id=628858 You can download the release from here: http://sourceforge.net/project/showfiles.php?group_id=1369package_id=175103 Thank you to everybody who contributed to this release. Enjoy, -- Jarrod Millman Computational Infrastructure for Research Labs 10 Giannini Hall, UC Berkeley phone: 510.643.4014 http://cirl.berkeley.edu/ ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] 1.2.0rc2 tagged! --PLEASE TEST--
On Thu, Sep 25, 2008 at 7:19 AM, [EMAIL PROTECTED] wrote: I hope you'll grab the updated docstrings before tagging. At least grab numpy.__doc__. The main numpy help string didn't adequately point users to alternatives to help() for the ufuncs. That will have to wait until 1.2.1, which we will put out shortly. Thanks, -- Jarrod Millman Computational Infrastructure for Research Labs 10 Giannini Hall, UC Berkeley phone: 510.643.4014 http://cirl.berkeley.edu/ ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] 1.2.0rc2 tagged! --PLEASE TEST--
On Wed, Sep 24, 2008 at 11:13 AM, Bruce Southey [EMAIL PROTECTED] wrote: What is the status of NumPy 1.2 and when can we expect the final version? I hope to announce it on Friday or Saturday. The only thing I am looking into now is whether we should back port the fix to lookfor or not: http://projects.scipy.org/scipy/numpy/changeset/5862 Either way, I plan to tag later today. -- Jarrod Millman Computational Infrastructure for Research Labs 10 Giannini Hall, UC Berkeley phone: 510.643.4014 http://cirl.berkeley.edu/ ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] python 2.4 incompatibility in numpy.lookfor in numpy 1.2.0rc2
On Tue, Sep 23, 2008 at 1:35 PM, Robert Kern [EMAIL PROTECTED] wrote: On Tue, Sep 23, 2008 at 15:18, joep [EMAIL PROTECTED] wrote: Hi, I was trying to use lookfor on python 2.4 and got an exception with np.lookfor because of a missing method in pkgutil that was added in python 2.5. Hmmm. Unfortunately, that's an intrinsic part of the lookfor() functionality. We could just bring in all of pkgutil.py. Or we remove lookfor(). Or we document it as working with Python 2.5 only. For 1.2.0, let's add a note to the docstring stating it currently works for 2.5 and make it raise a more informative exception. lookfor is in 1.1.x as well. -- Jarrod Millman Computational Infrastructure for Research Labs 10 Giannini Hall, UC Berkeley phone: 510.643.4014 http://cirl.berkeley.edu/ ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] ready to tag 1.2.0
Hey, I would like to tag 1.2.0 from the 1.2.x branch. Are there any problems with this? In particular, are there any known problems that would require us having another release candidate? As soon as we get this release out we can start back-porting bugfixes from the trunk to the 1.2.x branch in preparation for a 1.2.1 release. Thanks, -- Jarrod Millman Computational Infrastructure for Research Labs 10 Giannini Hall, UC Berkeley phone: 510.643.4014 http://cirl.berkeley.edu/ ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] 1.2.0rc2 tagged! --PLEASE TEST--
Which version of gcc are you using? Do I remember correctly that you had the same failure with numpy 1.1.1 when using gcc 3.3 and that the problem went away when you used gcc 4.1. If you are using 3.3, could you try with 4.1 and let us know if you run into the same problem? Thanks, -- Jarrod Millman Computational Infrastructure for Research Labs 10 Giannini Hall, UC Berkeley phone: 510.643.4014 http://cirl.berkeley.edu/ ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] 1.2.0rc2 tagged! --PLEASE TEST--
On Tue, Sep 16, 2008 at 12:18 PM, Charles Doutriaux [EMAIL PROTECTED] wrote: Thanks Jarrod it's coming back now. I thought they had updated the system... but no luck... Ok that's the issue i'm using: gcc (GCC) 3.4.6 20060404 (Red Hat 3.4.6-8) Glad to hear it is a known issue. By the way, does anyone know what version of gcc we require? Where is that documented? The only occurrence of a recommended gcc version is here: http://scipy.org/Installing_SciPy/BuildingGeneral And it states gcc 3.x compilers are recommended. -- Jarrod Millman Computational Infrastructure for Research Labs 10 Giannini Hall, UC Berkeley phone: 510.643.4014 http://cirl.berkeley.edu/ ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] 1.2.0rc2 tagged! --PLEASE TEST--
Hey, I would like to release 1.2.0 final soon, but I need to know whether anyone is having any problems with the rc2 binaries. Please test them and let me know whether or not you have any problems with them. Thanks, Jarrod On Sat, Sep 13, 2008 at 4:00 PM, Jarrod Millman [EMAIL PROTECTED] wrote: Hello, The 1.2.0rc2 is now available: http://svn.scipy.org/svn/numpy/tags/1.2.0rc2 The source tarball is here: https://cirl.berkeley.edu/numpy/numpy-1.2.0rc2.tar.gz Here is the universal Mac binary: https://cirl.berkeley.edu/numpy/numpy-1.2.0rc2-py2.5-macosx10.5.dmg Here are the Window's binaries: http://www.ar.media.kyoto-u.ac.jp/members/david/archives/numpy/numpy-1.2.0rc2-win32-superpack-python2.4.exe http://www.ar.media.kyoto-u.ac.jp/members/david/archives/numpy/numpy-1.2.0rc2-win32-superpack-python2.5.exe Here are the release notes: http://scipy.org/scipy/numpy/milestone/1.2.0 Please test this release ASAP and let us know if there are any problems. If there are no show stoppers, this will become the 1.2.0 release. Thanks, -- Jarrod Millman Computational Infrastructure for Research Labs 10 Giannini Hall, UC Berkeley phone: 510.643.4014 http://cirl.berkeley.edu/ -- Jarrod Millman Computational Infrastructure for Research Labs 10 Giannini Hall, UC Berkeley phone: 510.643.4014 http://cirl.berkeley.edu/ ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] 1.2.0rc2 tagged! --PLEASE TEST--
On Mon, Sep 15, 2008 at 10:49 AM, Mark Miller [EMAIL PROTECTED] wrote: Warning, errors, and failures here on XP Pro (numpy installed with the python 2.5 superpack). Just passing it along, and apologies if these have already been caught. Thanks for testing this. It looks like you have some old files sitting around (e.g., numpy\core\tests\test_ma.py). Could you delete C:\Python25\lib\site-packages\numpy and reinstall 1.2.0rc2? Thanks, -- Jarrod Millman Computational Infrastructure for Research Labs 10 Giannini Hall, UC Berkeley phone: 510.643.4014 http://cirl.berkeley.edu/ ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] 1.2.0rc2 tagged! --PLEASE TEST--
On Mon, Sep 15, 2008 at 11:10 AM, Mark Miller [EMAIL PROTECTED] wrote: OK..thanks. That did the trick. All clear now, save for 3 known failures. Excellent. Thanks for testing this. -- Jarrod Millman Computational Infrastructure for Research Labs 10 Giannini Hall, UC Berkeley phone: 510.643.4014 http://cirl.berkeley.edu/ ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] F2py errors still
On Fri, Sep 12, 2008 at 12:34 PM, Blubaugh, David A. [EMAIL PROTECTED] wrote: In response to your statement I cannot find Numpy 1.2 listed. Where is it??? I haven't announced rc2 yet, since I am still waiting to get the binaries built (should be out later today). But since you are building yourself, here are the links: The 1.2.0rc2 svn tag: http://svn.scipy.org/svn/numpy/tags/1.2.0rc2 The source tarball: https://cirl.berkeley.edu/numpy/numpy-1.2.0rc2.tar.gz -- Jarrod Millman Computational Infrastructure for Research Labs 10 Giannini Hall, UC Berkeley phone: 510.643.4014 http://cirl.berkeley.edu/ ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] mixed-EOL problems w/
I have been trying to get Launchpad to do continuous imports of the SciPy subversion repository into Bazaar: https://code.launchpad.net/~vcs-imports/scipy/trunk This works fine for NumPy: https://code.launchpad.net/~vcs-imports/numpy/trunk However, this doesn't work for SciPy due to a mixed-EOL issue: https://bugs.launchpad.net/launchpad-cscvs/+bug/256050 Colin Watson has recently volunteered to look into fixing this issue and was asking if anyone had a preference about how this should be solved. Please let me know if you see any reason for one solution over another. Thanks, -- Jarrod Millman Computational Infrastructure for Research Labs 10 Giannini Hall, UC Berkeley phone: 510.643.4014 http://cirl.berkeley.edu/ ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] planning for numpy 1.3.0 release
Now that 1.2.0 is almost finalized, I wanted to ask everyone to start thinking about what they plan to work on for the next minor release: http://scipy.org/scipy/numpy/milestone/1.3.0 We have been gradually moving toward a more time-based release schedule over the last several months. In this vein, I would like to move feature and code discussion and planning to the beginning of the release cycle, rather than waiting until the end of the release cycle. So if there is something that you would like to work on during this release cycle, please bring it up now. Also it is important for us to keep the trunk as stable as possible; if you wish to work on a major new feature or an significant refactoring of the codebase, please work in a branch. Thanks, -- Jarrod Millman Computational Infrastructure for Research Labs 10 Giannini Hall, UC Berkeley phone: 510.643.4014 http://cirl.berkeley.edu/ ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] distance matrix and (weighted) p-norm
On Sun, Sep 7, 2008 at 4:07 PM, Emanuele Olivetti [EMAIL PROTECTED] wrote: David said that distance computation will be moved in a separate package soon. I guess that your implementation will be the suitable one for this package. Am I wrong? Yes, that is correct. David was talking about pulling Damian's distance code out of scipy.cluster and into its own scipy subpackage. -- Jarrod Millman Computational Infrastructure for Research Labs 10 Giannini Hall, UC Berkeley phone: 510.643.4014 http://cirl.berkeley.edu/ ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] 1.2.0rc1 tagged!
Hello, The 1.2.0rc1 is now available: http://svn.scipy.org/svn/numpy/tags/1.2.0rc1 The source tarball is here: https://cirl.berkeley.edu/numpy/numpy-1.2.0rc1.tar.gz Here is the universal Mac binary: https://cirl.berkeley.edu/numpy/numpy-1.2.0rc1-py2.5-macosx10.5.dmg Here are the Window's binaries: http://www.ar.media.kyoto-u.ac.jp/members/david/archives/numpy/numpy-1.2.0rc1-win32-superpack-python2.4.exe http://www.ar.media.kyoto-u.ac.jp/members/david/archives/numpy/numpy-1.2.0rc1-win32-superpack-python2.5.exe Here are the release notes: http://scipy.org/scipy/numpy/milestone/1.2.0 Please test this release ASAP and let us know if there are any problems. If there are no show stoppers, this will likely become the 1.2.0 release. Thanks, -- Jarrod Millman Computational Infrastructure for Research Labs 10 Giannini Hall, UC Berkeley phone: 510.643.4014 http://cirl.berkeley.edu/ ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
