On Sat, Jul 10, 2010 at 4:18 PM, John Hunter <jdh2...@gmail.com> wrote: > On Sat, Jul 10, 2010 at 4:13 PM, Ryan May <rma...@gmail.com> wrote: >> both, specifically check_for_tk(). Here we catch the actual exception >> object and use it to print an error message. If anyone has a >> suggestion (not print the error? Look at the exception stack?), I'd >> love to be able to commit these so that at least setup.py runs. > > You might want to paste cbook.exception_to_str into setupext.py and > use that to get the error message.
That actually uses traceback.print_exc(), which prints out a whole traceback and looks ugly to me. Instead, I went with sys.exc_info(), which can get the value of the current exception. It's uglier than getting the exception object in the except statement, but until we can just support >= 2.6, we're pretty much stuck with it. Otherwise, I committed the change to setupext.py. Main changes were to redo some imports (things moved, renamed) and to make print at least look like a function. I've actually been running with this in place for quite a few months with no problems. The results at this point are that matplotlib installs and runs fine for me on Linux with Python 2.6. With Python 3.1, I get a compile failure with src/ft2font.cpp, which isn't surprising. So I guess we're on our way to Python 3! Ryan -- Ryan May Graduate Research Assistant School of Meteorology University of Oklahoma ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
