Re: [matplotlib-devel] image_nonuniform.py broken in trunk HEAD

2010-03-03 Thread Jae-Joon Lee
Should be fixed with r8178. Regards, -JJ On Wed, Mar 3, 2010 at 5:19 PM, Jae-Joon Lee wrote: > On Wed, Mar 3, 2010 at 4:48 PM, John Hunter wrote: >> JJ is this related to your commit in r8035 : "support >> unsampled image for ps backend" > > It seems to be. > I'll take a look. > > Regards, >

Re: [matplotlib-devel] image_nonuniform.py broken in trunk HEAD

2010-03-03 Thread Jae-Joon Lee
On Wed, Mar 3, 2010 at 4:48 PM, John Hunter wrote: > JJ is this related to your commit in r8035 : "support > unsampled image for ps backend" It seems to be. I'll take a look. Regards, -JJ -- Download Intel® Parallel St

[matplotlib-devel] image_nonuniform.py broken in trunk HEAD

2010-03-03 Thread John Hunter
examples/pylab_examples/image_nonuniform.py is broken in HEAD An attempt to access "self._oldxslice" in _get_unsampled_image is implicated: JJ is this related to your commit in r8035 : "support unsampled image for ps backend" File "/home/jdhunter/dev/lib/python2.6/site-packages/matplotlib/bac

Re: [matplotlib-devel] git migration

2010-03-03 Thread John Hunter
On Wed, Mar 3, 2010 at 1:31 PM, Jonathan Taylor wrote: >> I am strongly in favor of keeping the entire commit history of >> trunk/matplotlib.  While the repo is large now, most of the size comes >> from data and regression test images, and the early history is largely >> code so will not add much

Re: [matplotlib-devel] git migration

2010-03-03 Thread Jonathan Taylor
> I am strongly in favor of keeping the entire commit history of > trunk/matplotlib.  While the repo is large now, most of the size comes > from data and regression test images, and the early history is largely > code so will not add much incremental size.  I suppose one of the > downsides of git i

Re: [matplotlib-devel] favicon submission

2010-03-03 Thread Ben Axelrod
Cool. Looks good. I did tweak the image a bit to make the colors stand out better. But only slightly. Because when I made the shapes too big, the image lost it's MPL "feel". Here is the source image I used to create the icon. Feel free to give it a go. There are a number of programs that

Re: [matplotlib-devel] favicon submission

2010-03-03 Thread John Hunter
On Wed, Mar 3, 2010 at 11:16 AM, John Hunter wrote: > On Wed, Mar 3, 2010 at 9:33 AM, Ben Axelrod wrote: >> I am a big fan of favicons.  I think MPL should definitely have one for the >> impending 1.0 release.  So I made one for you. >> >> To use, simply place this file in the top level web direc

Re: [matplotlib-devel] favicon submission

2010-03-03 Thread John Hunter
On Wed, Mar 3, 2010 at 9:33 AM, Ben Axelrod wrote: > I am a big fan of favicons.  I think MPL should definitely have one for the > impending 1.0 release.  So I made one for you. > > To use, simply place this file in the top level web directory.  That is > usually all that is required.  But some br

Re: [matplotlib-devel] git migration

2010-03-03 Thread Jeff Whitaker
John Hunter wrote: > On Tue, Mar 2, 2010 at 11:41 PM, Eric Firing wrote: > >> Andrew Straw wrote: >> [...] >> >>> This is a good point. My preferred option is that we jettison all the >>> stuff that is not going to be shipped with MPL 1.0 from the git repo. >>> (More correctly - we build a

[matplotlib-devel] favicon submission

2010-03-03 Thread Ben Axelrod
I am a big fan of favicons. I think MPL should definitely have one for the impending 1.0 release. So I made one for you. To use, simply place this file in the top level web directory. That is usually all that is required. But some browsers prefer if you put: in the header of the html page

Re: [matplotlib-devel] git migration

2010-03-03 Thread John Hunter
On Wed, Mar 3, 2010 at 8:29 AM, william ratcliff wrote: > I don't want to get into a flame war over this, but if Sourceforge was > pressured into this and is having complaints and google has the same > problem, how does Github get around it?  Are they incorporated in the US or > outside?  If this

Re: [matplotlib-devel] git migration

2010-03-03 Thread william ratcliff
I don't want to get into a flame war over this, but if Sourceforge was pressured into this and is having complaints and google has the same problem, how does Github get around it? Are they incorporated in the US or outside? If this is likely to become a problem, is there another service that can

Re: [matplotlib-devel] git migration

2010-03-03 Thread John Hunter
On Tue, Mar 2, 2010 at 11:41 PM, Eric Firing wrote: > Andrew Straw wrote: > [...] >> This is a good point. My preferred option is that we jettison all the >> stuff that is not going to be shipped with MPL 1.0 from the git repo. >> (More correctly - we build a git repo without that stuff ever going