Re: [matplotlib-devel] OS X Leopard install, snag

2007-11-04 Thread John Hunter
On 11/4/07, Robert Kern <[EMAIL PROTECTED]> wrote:

> Are you using the gfortran from hpc.sf.net? I don't recommend it anymore. I 
> use
> the binary from http://r.research.att.com/tools/. It is universal. That 
> should help.

Yep, I was.  That was the binary recommended first on the wiki (at
with a note at the end that some have had problems with it that do not
appear related to my problem).  Using the universal binary at the att
site fixed my problem, and I updated the wiki at
http://www.scipy.org/Installing_SciPy/Mac_OS_X.

Now for my next problem: I built zlib, libpng an freetype from source
and I get a

ld: warning in /Developer/SDKs/MacOSX10.4u.sdk/usr/local/lib/libpng.dylib,
file is not of required architecture

error when building mpl.  Is there an easy way in the
configure/make/make install cycle to tell the compiler to build
universal binaries?

Alternatively, can I instruct distutils to simply not provide the
-arch ppc build?  I can see how
this will be a problem down the road, since any non universal library
I install on my system will potentially break my builds.

Thanks,
JDH

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


Re: [matplotlib-devel] STIX fonts

2007-11-04 Thread Michael Droettboom
This is maybe another push in the direction of using fontconfig (which claims 
to support otf fonts already).  I'd really prefer to go in that direction 
rather than continue to tack on partial reimplementations of it in 
font_manager.py -- but it does complicate dependencies on non-X11 platforms).

There is experimental support for using fontconfig (through the commandline 
interface, not an API wrapper), that may work.  Just set the USE_FONTCONFIG 
variable to True in font_manager.py.  You will have to copy the MPL fonts to a 
system font directory (such as ~/.fonts) in order for fontconfig to find them.

(I can also look into this myself when I return to the office on Monday...)

Cheers,
Mike

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


Re: [matplotlib-devel] STIX fonts

2007-11-04 Thread Michael Droettboom
I should also add -- it would be really nice to have STIX fonts working in the 
upcoming stable release if possible.  Hopefully tomorrow morning I can assess 
how much work that will be and maybe delay tagging the release slightly so this 
can be worked through.  It would be nice to remove the Computer Modern fonts 
(in mathtext only), but they still serve a niche in that they match the LaTeX 
fonts for users who can't/won't use usetex.  So we're probably stuck with them 
for the long term even if STIX becomes a nicer/cleaner option.

Cheers,
Mike

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


Re: [matplotlib-devel] STIX fonts

2007-11-04 Thread Darren Dale
On Sunday 04 November 2007 9:04:15 am Michael Droettboom wrote:
> I should also add -- it would be really nice to have STIX fonts working in
> the upcoming stable release if possible.  Hopefully tomorrow morning I can
> assess how much work that will be and maybe delay tagging the release
> slightly so this can be worked through.  It would be nice to remove the
> Computer Modern fonts (in mathtext only), but they still serve a niche in
> that they match the LaTeX fonts for users who can't/won't use usetex.  So
> we're probably stuck with them for the long term even if STIX becomes a
> nicer/cleaner option.

I haven't found sans-serif or monospaced fonts in their distribution. Maybe I 
don't know where to look. I sent an email to the STIX website asking about 
them, but havent heard back from them. I tried opening the fonts in 
fontforge, and there are a lot of missing glyphs.

This is a beta release for the STIX fonts, and given how long it took to 
release and the number of self imposed deadlines that came and went, I 
wouldnt be surprised if there were some major issues that will need to be 
worked out. There is supposed to be a package for using STIX with latex, 
which they claim will be out by the end of the year, as will the final font 
release. Maybe we should start a pool!

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


Re: [matplotlib-devel] STIX fonts

2007-11-04 Thread Darren Dale
On Sunday 04 November 2007 8:50:48 am Michael Droettboom wrote:
> This is maybe another push in the direction of using fontconfig (which
> claims to support otf fonts already).  I'd really prefer to go in that
> direction rather than continue to tack on partial reimplementations of it
> in font_manager.py -- but it does complicate dependencies on non-X11
> platforms).

What are the dependency problems? I thought freetype was the only requirement. 
Incidentally, GIMP uses fontconfig on windows, and they comment at 
http://www.gimp.org/~tml/gimp/win32/downloads.html: "Contrary to what many 
seem to think, fontconfig is in no way dependent on X11, so it does make some 
sense to use it on Windows."

> There is experimental support for using fontconfig (through the commandline
> interface, not an API wrapper), that may work.  Just set the USE_FONTCONFIG
> variable to True in font_manager.py.  You will have to copy the MPL fonts
> to a system font directory (such as ~/.fonts) in order for fontconfig to
> find them.
>
> (I can also look into this myself when I return to the office on Monday...)

Same here, I'll have a look on Monday.

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


Re: [matplotlib-devel] OS X Leopard install, snag

2007-11-04 Thread Boyd Waters
As a general note, I built MatPlotlib-SVN on Leopard against the  
Apple Python, using the numpy, libz, freetype, and png that are  
included with Leopard.

It seems to work fine, superficially; I have not run extensive  
regressions with it yet.

I can send along a MacPorts portfile (including patches) tomorrow;  
(my Leopard problem is that SSH won't respond so I can't get to my  
office machine from  home).

I have some opinions about your other questions, the answers are to  
set specific environment variables.
However, my answers MIGHT BE WRONG because I can't test these at the  
moment (see ssh problem, above)

So take these responses with some skepticism. But perhaps they can  
point you in a helpful direction:

On Nov 4, 2007, at 6:29 AM, John Hunter wrote:

> Now for my next problem: I built zlib, libpng an freetype from source
> and I get a
>
> ld: warning in /Developer/SDKs/MacOSX10.4u.sdk/usr/local/lib/ 
> libpng.dylib,
> file is not of required architecture


Hmm, what about setting a MACOSX_DEPLOYMENT_TARGET=10.5


>
> error when building mpl.  Is there an easy way in the
> configure/make/make install cycle to tell the compiler to build
> universal binaries?

I believe that "generic" autoconf would pick up CFLAGS:

CFLAGS="-arch ppc -arch i386"


> Alternatively, can I instruct distutils to simply not provide the
> -arch ppc build?

Distutils uses ARCHFLAGS -- if you are using the Python from Apple  
Leopard:

ARCHFLAGS="-arch i386"

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


[matplotlib-devel] remove ipython hack?

2007-11-04 Thread Eric Firing
John, Fernando,

Is it OK to remove the hack now?  In pyplot.py:

# a hack to keep old versions of ipython working with mpl after bug
# fix #1209354
if 'IPython.Shell' in  sys.modules:
 from matplotlib.backends import new_figure_manager, 
draw_if_interactive, show
else:
 from matplotlib.backends import pylab_setup
 new_figure_manager, draw_if_interactive, show = pylab_setup()


It is not a big deal, but in the interests of simplification and cleanup 
I would like to remove this (and related lines in backends/__init__.py) 
if it is ancient and no longer needed.

Eric

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel