Re: release plans

     Sorry for the delay.  Apparently at some point the mingw compiler
became default, and it was giving me problems since I was trying to
build with the VS libpng and freetype.  All binaries are posted now.
Jon, you should probably send the announcement since I am a little out
of touch with the changes since 0.90.

- Charlie

On Nov 29, 2007 8:45 PM, Charlie Moad <cwmoad@...> wrote:
> So here's my plan.  I just got an iMac a few weeks ago and I had to
> spend a little time getting parallels setup with VS2003... yada yada
> yada.  I plan on cutting a 0.91.1 release tomorrow followed shortly by
> windows and mac builds.  Hopefully nothing radical has snuck into the
> svn tree since the 0.91.0 build.
>
> - Charlie
>
>
> On Nov 28, 2007 8:32 AM, Charlie Moad <cwmoad@...> wrote:
> > My 1 year old only let me get the source release pushed last night and
> > build the mac release.  I'll try to get the windows builds posted
> > tonight.
> >
> >
> > On Nov 28, 2007 8:23 AM, Rob Hetland <hetland@...> wrote:
> > >
> > > On Nov 28, 2007, at 12:03 AM, John Hunter wrote:
> > >
> > >
> > > > I think native tcl/tk is preferable, but this is not a terribly

Re: release plans

On Dec 1, 2007 12:03 PM, Charlie Moad <cwmoad@...> wrote:
>      Sorry for the delay.  Apparently at some point the mingw compiler
> became default, and it was giving me problems since I was trying to
> build with the VS libpng and freetype.  All binaries are posted now.
> Jon, you should probably send the announcement since I am a little out
> of touch with the changes since 0.90.

OK, I'll do this on Monday when more people are working and thinking
about python.  Thanks again for the build!

JDH

-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4

Trivial colour bar patches

Dear All,

I've placed some very simple colour bar patches at :

https://code.launchpad.net/~bojan-bnikolic/python2.4-matplotlib/bn-colourbar-patches

They make default shrink of the colour bar such that it is the same size
as the image part of the figure. Merge if/as you see fit.

Best,
Bojan

--

-- 
Bojan Nikolic

-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4

Re: Trivial colour bar patches

On Dec 1, 2007 8:15 AM, Bojan Nikolic <bojan@...> wrote:
>
> Dear All,
>
> I've placed some very simple colour bar patches at :
>
> https://code.launchpad.net/~bojan-bnikolic/python2.4-matplotlib/bn-colourbar-patches
>
> They make default shrink of the colour bar such that it is the same size
> as the image part of the figure. Merge if/as you see fit.

Eric, since you wrote the shrink code, I'll leave this one up to you...

JDH

-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4

Misleading installation instructions in INSTALL file

Hello,

first let me thank you for your excellent software - I think
it is just wonderful and very pleasant to use.

Two small things came up when I installed 0.91.1 into
my home directory (I didn't want to mess with the debian
packages since they are usually very fast in updating them)

This passage in the INSTALL file is misleading:

Note that if you install matplotlib anywhere other than the default
location, you will need to set the MATPLOTLIBDATA environment
variable to point to the install base dir.

Instead of setting MATPLOTLIBDATA to the base dir I specified
with setup.py install --prefix /home/mo/mpl I had to set
it to

/home/mo/mpl/lib/python2.4/site-packages/matplotlib/mpl-data/

for mathtext to find its fonts.

Secondly this passage in  matplotlib/mathtext.py

 544         if cached_font is None:
 545             try:
 546                 font = FT2Font(basename)
 547             except RuntimeError:
 548                 return None

Re: Trivial colour bar patches

Bojan Nikolic wrote:
> Dear All,
> 
> I've placed some very simple colour bar patches at :
> 
> https://code.launchpad.net/~bojan-bnikolic/python2.4-matplotlib/bn-colourbar-patches
> 
> They make default shrink of the colour bar such that it is the same size
> as the image part of the figure. Merge if/as you see fit.
> 
> Best,
> Bojan
> 

Bojan,

Thank you for the suggested patches.  Unfortunately, however, they do 
not in general solve the problem of size mismatch between the colorbar 
and the corresponding axes, as you will see if you try a variety of axes 
dimensions and aspect ratio settings.  Your patch is equivalent to 
setting the default shrink to 0.8 instead of 1.0, and I agree that this 
is a better default.  I did not use it originally simply for the sake of 
backwards and Matlab compatibility.  I suspect that making the change 
will please more people than it will upset, though, so I will try it in 
svn after the switch to the transforms branch. I don't see any point in 
making little changes like this right now, when we are trying to 
stabilize a last release before that switch.  Everyone has lived with 
the present default for a long time, and a few more weeks won't hurt.

A more general solution to the size-matching problem may emerge after we 

Re: Misleading installation instructions in INSTALL file

Mario Oschwald wrote:
> Hello,
> 
> first let me thank you for your excellent software - I think
> it is just wonderful and very pleasant to use.
> 
> Two small things came up when I installed 0.91.1 into
> my home directory (I didn't want to mess with the debian
> packages since they are usually very fast in updating them)
> 
> This passage in the INSTALL file is misleading:
> 
> Note that if you install matplotlib anywhere other than the default
> location, you will need to set the MATPLOTLIBDATA environment
> variable to point to the install base dir.
> 
> 
> Instead of setting MATPLOTLIBDATA to the base dir I specified
> with setup.py install --prefix /home/mo/mpl I had to set
> it to
> 
> /home/mo/mpl/lib/python2.4/site-packages/matplotlib/mpl-data/
> 
> for mathtext to find its fonts.

Was that necessary?  I routinely install matplotlib to a non-standard 
location, and have never set MATPLOTLIBDATA.  If MATPLOTLIBDATA is not 
set, it appears that matplotlib will look for the "mpl-data" directory 
underneath the main matplotlib directory.  (Which in your case is 
/home/mo/mpl/lib/python2.4/site-packages/matplotlib/).  I'm curious if 

Re: Misleading installation instructions in INSTALL file

[Brought conversation back to matplotlib-devel list].

Mario Oschwald wrote:
> Hello
> 
> Michael Droettboom wrote:
>> Mario Oschwald wrote:
>>> This passage in the INSTALL file is misleading:
>>>
>>> Note that if you install matplotlib anywhere other than the default
>>> location, you will need to set the MATPLOTLIBDATA environment
>>> variable to point to the install base dir.
>>>
>> Was that necessary?  I routinely install matplotlib to a non-standard
>> location, and have never set MATPLOTLIBDATA.  If MATPLOTLIBDATA is not
>> set, it appears that matplotlib will look for the "mpl-data" directory
>> underneath the main matplotlib directory.  (Which in your case is
>> /home/mo/mpl/lib/python2.4/site-packages/matplotlib/).  I'm curious if
>> you get errors without specifying MATPLOTLIBDATA, and what the error is.
>>  Perhaps the INSTALL docs should be updated to clarify that you only
>> need this if you install the data in a non-standard place *relative to*
>> the source code...
> 
> You are right - if I unset that variable the mpl-data directory is found
> automagically  Stupid me for reading INSTALL files . That passage
> should definitely be updated to reflect that behaviour.

I'm +1 on just removing the paragraph altogether.  It only applies if 
someone did:

Re: Misleading installation instructions in INSTALL file

On Dec 3, 2007 9:10 AM, Michael Droettboom <mdroe@...> wrote:

> I'm +1 on just removing the paragraph altogether.  It only applies if
> someone did:
>
>         python setup.py install --install-data=/some/weird/place

Yes, it should be removed.  It predates the move of the data to
mpl-data in the matplotlib installation directory, and isn't really
needed anymore.

JDH

-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4

pcolormesh in transforms branch

Hi Michael:  I've been testing basemap with the transforms branch.  All 
the examples now run, but the ones that use pcolormesh don't work 
correctly.  I've attached an example.   In the trunk, using either 
pcolor or pcolormesh produce an identical plot.  In the transforms 
branch, using pcolor produces the correct plot, but using pcolormesh 
seems to scramble the image.

-Jeff

-- 
Jeffrey S. Whitaker         Phone  : (303)497-6313
Meteorologist               FAX    : (303)497-6449
NOAA/OAR/PSD  R/PSD1        Email  : Jeffrey.S.Whitaker@...
325 Broadway                Office : Skaggs Research Cntr 1D-124
Boulder, CO, USA 80303-3328 Web    : http://tinyurl.com/5telg

-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4

_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@...
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel