[matplotlib-devel] 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 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" - Date: Wed, 24 Feb 2010 12:54:52 -0800 From: "C. Titus Brown" 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 - -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Bug in julian2num()/num2julian()?
Günter Lichtenberg wrote: > On Thursday 04 March 2010 14:20:41 you wrote: >> 2010/3/4 Günter Lichtenberg : >>> Hi >>> >>> I think there is a bug in the conversion routines jul2num() and >>> num2jul(). I tried to define a date axis for satellite data. The time is >>> measured in a modified Julian Date (JD). So reading in the data and then >>> doing >> Hi Günter, >> >> Thanks for digging into this. Could you file a report on the bug tracker >> > > Done under > > 2963391 Wrong conversion in julian2num/num2julian > > gl > Thanks. Fixed in 8181 (branch) and 8182 (trunk). Eric -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
[matplotlib-devel] PDF bug in stable release
I have a system that creates PDF output using matplotlib/basemap, and I'm wondering if anyone can give me some information on how to work around a bug in the PDF backend. I submitted the following bug to the mailing list: http://old.nabble.com/error-with-basemap-and-pdf-td25899014.html#a25899014 and then to the bug tracker: https://sourceforge.net/tracker/index.php?func=detail&aid=2879910&group_id=80706&atid=560720 last October, _after_ the most recent stable matplotlib release. According to those discussions, the bug has been fixed in SVN. Accordingly, I have recently tried to build matplotlib from source, but cannot use the resulting binaries, due to the problem described in the following mailing list thread and bug report: http://old.nabble.com/Cannot-import-ft2font-on-Mac-OSX-td27756808.html#a27758227 https://sourceforge.net/tracker/index.php?func=detail&aid=2959725&group_id=80706&atid=560720 I figure I could solve my problem one of three ways: 1) Waiting for the current SVN code to become a stable release. This would need to happen before my system goes live. 2) Patch my current code with the fix already in SVN. I would need someone to point me to the relevant files, and give me some pointers on applying the patch. 3) Getting some help with my SVN build issue. Does anyone have any tips? Thanks, Mike -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
[matplotlib-devel] Possible Tk version issue in setupext.py
Hi- This is probably a low-probability event, however it may be worth noting that the check for the Tk framework location in setupext.py's detect_tkinter_darwin examines possible framework paths in a different order than they are checked in Python's setup.py for the purpose of building _tkinter. Python's setup.py searches: /Library/Frameworks /System/Library/Frameworks/ $HOME/Library/Frameworks MPL's setupext.py searches: $HOME/Library/Frameworks /Library/Frameworks /System/Library/Frameworks/ If a user has installed more than one new (non-Apple) Tcl/Tk, it is possible for MPL and _tkinter to link against different frameworks. I think MPL does some version checking that would prevent a build if there is a mismatch, but the source of the difficulty may not be obvious to the installer. The Snow Leopard Xcode man page for ld says the following about ld's framework searching: The default framework search path is /Library/Frameworks then /System/Library/Frameworks. It says nothing about searching under $HOME. So from the point of view of Xcode it looks like there is no "right" order between the two options, but MPL's looks "right" to me, i.e., if a user has installed something under $HOME, the user probably intends it to override the system. -Tom - This mail sent through IMP: http://horde.org/imp/ -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
[matplotlib-devel] Update numpy version tests in setupext.py and __init__.py
Hi folks- I've been experimenting with SVN checkouts of numpy and scipy, and found they are not compatible with mpl-0.99.1. The problem is that the numpy version number for recent checkouts is 2.0.x (2.0.0.dev8289 for the version I'm currently using), but mpl's numpy version checking (on the 1st two digits) isn't quite smart enough to know that 2.0 > 1.1. It's easy enough to fix by hand; the obvious lines in setupext.py and __init__py need to be changed to something like: if not ( (int(nn[0]) == 1 and int(nn[1]) >= 1) or (int(nn[0]) > 1) ): I haven't kept up with the recent discussion about how to number the next numpy (there was some back and forth about how soon to move to 2.x), but sooner or later it will get up to 2.x, so this should be fixed in the mpl repo. Cheers, Tom - This mail sent through IMP: http://horde.org/imp/ -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
