In article <C2C52FB1-9277-476A-886E-41A4003A845B@...755...>,
"Samuel M. Smith" <smithsm@...755...>
wrote:
>
>> which versions of wxPython are supported?
>
> I haven't tried the new one, but the last release worked well with
> wxPython2.6.3, but had some issues with 2.8.* -- I don't think anyone
> has addressed those yet.
>
Just to confirm, the binary posted at the following
matplotlib - Browse Files at SourceForge.net
macosx-10.4-fat.egg?modtime=1171118530&big_mirror=0
was compiled to work with wxPython 2.6 but may work with wxPython 2.8?
It was compiled with wxPython 2.6. It will NOT work with wxPython 2.8.
What Chris is referring to is that when I built matplotlib against
wxPython 2.8 (in hopes of serving that at pythonmac.org) I ran into
several problems:
- there appears to be broken code in matplotlib's wx support (making us
wonder how and why it works with wxPython 2.6 at all)
- fixing that left something that ran but had some odd problems
Shouldn't the version of wxPython also get included in the name along
with the python version and os version?
That information is in the ReadMe file in the installer.
Keep in mind that we have:
- which back ends are supported
- which numeric packages are support
I don't want to try to fit all that into a file name.
-- Russell
Shouldn't the version of wxPython also get included in the name along
with the python version and os version?
That information is in the ReadMe file in the installer.
I will try to remember to look there in the future to know which wx is supported, thanks.
The matplotlib on sourceforge
http://downloads.sourceforge.net/matplotlib/matplotlib-0.90.0-py2.5-macosx-10.4-fat.egg?modtime=1171118530&big_mirror=0
is an egg but doesn't install with easy_install. Complains there is no setup.py file.
I copied the .egg directory into ....site-packages but it is not automatically included in sys.path
when I run the python interpreter.
I have to manually do this:
>>> from pkg_resources import require
>>> require("matplotlib")
[matplotlib 0.90.0 (/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/matplotlib-0.90.0-py2.5-macosx-10.4-fat.egg)]
for it to be accessible.
I guess I have to add it manually to my PYTHONPATH or else generate a .pth file and put it in site-packages
to get it automatically added to sys.path?
In the past the distributions were a little more user friendly for installing.
I know I can't complain too much since you are doing all the work.
Just wondering if I missed something when I tried to install it.
Oops, I just realized how misleading my earlier message was. I do NOT build the official matplotlib Mac packages. I have been building the packages at pythonmac.org. I started that because an earlier Python 2.4 matplotlib package crashed when using a user-installed Tcl/Tk* and just never got out of the habit.
So I don't have anything to do with the official matplotlib Mac binaries and I have no idea what's in their ReadMe files. I *hope* they include the necessary info about what version of wxPython is required and all that, but I don't know.
I can't help you with easy_install either. Sorry.
-- Russell
* The crash stems from a limitation of the Mac build of Python 2.4 that was fixed in 2.5. By default MacPython 2.4 does not find a 3rd party Tcl/Tk. There's a simple patch to fix this but it appears that binary packages that use Tkinter may not work with 3rd party Tcl/Tk unless the patch was applied by the person doing the build.
···
At 2:33 PM -0700 2007-02-20, Samuel M. Smith wrote:
Shouldn't the version of wxPython also get included in the name along
with the python version and os version?
That information is in the ReadMe file in the installer.
I will try to remember to look there in the future to know which wx is supported, thanks.
The matplotlib on sourceforge
Download matplotlib-0.90.0-py2.5-macosx-10.4-fat.egg (matplotlib)
is an egg but doesn't install with easy_install. Complains there is no setup.py file.
I copied the .egg directory into ....site-packages but it is not automatically included in sys.path
when I run the python interpreter.
I have to manually do this:
from pkg_resources import require
require("matplotlib")
[matplotlib 0.90.0 (/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/matplotlib-0.90.0-py2.5-macosx-10.4-fat.egg)]
for it to be accessible.
I guess I have to add it manually to my PYTHONPATH or else generate a .pth file and put it in site-packages
to get it automatically added to sys.path?
In the past the distributions were a little more user friendly for installing.
I know I can't complain too much since you are doing all the work.
Just wondering if I missed something when I tried to install it.
If I go to the matplotlib download page:
<http://sourceforge.net/project/showfiles.php?group_id=80706>
then there is a table showing "matplotlib" and "matplotlib-toolkits". Clicking on "Download" or "matplotlib-0.90.0" results in a page with no files.
On the other hand, clicking on "matplotlib" (the upper-left link of the table) does the right thing. So does scrolling down, but that may be not be obvious unless one has a really big window.
-- Russell
Well that explains why there is no readme in the distribution on source forge.
Any chance you will build a distribution of matplotlib 0.90 for pythonmac soon?
···
On Feb 20, 2007, at 14:47 , Russell E Owen wrote:
In the past the distributions were a little more user friendly for installing.
I know I can't complain too much since you are doing all the work.
Just wondering if I missed something when I tried to install it.
Oops, I just realized how misleading my earlier message was. I do NOT
build the official matplotlib Mac packages. I have been building the
packages at pythonmac.org. I started that because an earlier Python
2.4 matplotlib package crashed when using a user-installed Tcl/Tk*
and just never got out of the habit.
So I don't have anything to do with the official matplotlib Mac
binaries and I have no idea what's in their ReadMe files. I *hope*
they include the necessary info about what version of wxPython is
required and all that, but I don't know.
I can't help you with easy_install either. Sorry.
I did earlier today; I'm hoping it will go up in the next day or so.
WXAgg is built against wxPython 2.6.x because last I heard the 2.8.x issues weren't resolved.
-- Russell
···
At 4:48 PM -0700 2007-02-20, Samuel M. Smith wrote:
On Feb 20, 2007, at 14:47 , Russell E Owen wrote:
In the past the distributions were a little more user friendly for installing.
I know I can't complain too much since you are doing all the work.
Just wondering if I missed something when I tried to install it.
Oops, I just realized how misleading my earlier message was. I do NOT
build the official matplotlib Mac packages. I have been building the
packages at pythonmac.org. I started that because an earlier Python
2.4 matplotlib package crashed when using a user-installed Tcl/Tk*
and just never got out of the habit.
So I don't have anything to do with the official matplotlib Mac
binaries and I have no idea what's in their ReadMe files. I *hope*
they include the necessary info about what version of wxPython is
required and all that, but I don't know.
I can't help you with easy_install either. Sorry.
Well that explains why there is no readme in the distribution on source forge.
Any chance you will build a distribution of matplotlib 0.90 for pythonmac soon?
Russell E Owen wrote:
I did earlier today; I'm hoping it will go up in the next day or so.
WXAgg is built against wxPython 2.6.x because last I heard the 2.8.x issues weren't resolved.
Correct. I'm still not sure how well MPL works with wxPython2.8 on other platforms, but no one has fixed the issues on OS-X yet. There is something weird with toolbars with wxPython2.8, I've run into that with some other code, so it may even take a new release of wxPython to get it all right. Of course, that wont' do it if I dont' get around to fiing a bug report!
wxPython includes a wxversion module that lets one select whihc version of wxPython you want run, if more than one is installed. It might be nice if those calls could get put into MPL somewhere, so that when MPL is built against a given version, that version will be run.
-Chris
···
--
Christopher Barker, Ph.D.
Oceanographer
Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Chris.Barker@...259...
Thank you for the update.
FYI: matplotlib 0.90.0 for Python 2.5 is now available at <http://pythonmac.org/packages>\. I did not build a version for Python 2.4.
Regards,
-- Russell
···
At 9:42 AM -0800 2007-02-21, Chris Barker wrote:
Russell E Owen wrote:
I did earlier today; I'm hoping it will go up in the next day or so.
WXAgg is built against wxPython 2.6.x because last I heard the 2.8.x issues weren't resolved.
Correct. I'm still not sure how well MPL works with wxPython2.8 on other platforms, but no one has fixed the issues on OS-X yet. There is something weird with toolbars with wxPython2.8, I've run into that with some other code, so it may even take a new release of wxPython to get it all right...
Chris Barker wrote:
Russell E Owen wrote:
I did earlier today; I'm hoping it will go up in the next day or so.
WXAgg is built against wxPython 2.6.x because last I heard the 2.8.x issues weren't resolved.
Correct. I'm still not sure how well MPL works with wxPython2.8 on other platforms, but no one has fixed the issues on OS-X yet. There is something weird with toolbars with wxPython2.8, I've run into that with some other code, so it may even take a new release of wxPython to get it all right. Of course, that wont' do it if I dont' get around to fiing a bug report!
wxPython includes a wxversion module that lets one select whihc version of wxPython you want run, if more than one is installed. It might be nice if those calls could get put into MPL somewhere, so that when MPL is built against a given version, that version will be run.
If someone can do a Windows build against a wxPython 2.8 version (and
Python 2.5) I could do some testing.
Is there a list of what the problems are?
Werner
Werner F. Bruhin wrote:
If someone can do a Windows build against a wxPython 2.8 version (and Python 2.5) I could do some testing.
Is there a list of what the problems are?
no.
One is that it won't build, due to a code error in the extension -- I don't know why that same error didn't cause a problem with earlier versions of wxPython.
The other I know about is some oddities with the toolbar on OS-X -- I think those are OS-X only issues.
-Chris
···
--
Christopher Barker, Ph.D.
Oceanographer
Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Chris.Barker@...259...
Werner F. Bruhin wrote:
Is there a list of what the problems are?
One is that it won't build, due to a code error in the extension -- I
don't know why that same error didn't cause a problem with earlier
versions of wxPython.
The WXAgg backend itself should still function without _wxagg.so, which exists slowly to speed up the Agg/wx.Image/wx.Bitmap tango. I tried to get it up and running on OSX with wxPython 2.8 earlier today but was quickly stymied by an inscrutable problem with wxPyConstructObject(). Since I'd like to start moving away from using a C++ extension in the backend, I'm going to try to re-implement its functionality using the new wx.BitmapFromBufferRGBA().
The other I know about is some oddities with the toolbar on OS-X -- I
think those are OS-X only issues.
Once I have the WXAgg accelerator straightened out, I'll see if I can reproduce and fix this problem.
Ken
···
On Feb 21, 2007, at 1:58 PM, Christopher Barker wrote:
FYI: matplotlib 0.90.0 for Python 2.5 is now available at
<http://pythonmac.org/packages>\. I did not build a version for Python
2.4.
Thanks, downloading as I type.