> Agreed. I know there are still some matplotlib users on python2.3, but > they'll have to move on eventually... ;)
Yes, we decided to drop support for python2.3, because we use decorators. But I am not going to drop support for 2.4, because Debian (my distribution) still uses it by default. :) > >> I generally don't like ctypes-based wrappers since changes in the > >> dependency can mean segfaults at runtime. I'm having a problem getting > >> pyglet to work on my particular version of OpenGL, for instance. But > >> perhaps freetype is stable enough for that not to be a problem. > > > > Could you please report it to http://groups.google.com/group/pyglet-users ? > > Sorry -- I should have mentioned I already did. Ah, so mdboom is you? I saw the headline, but I didn't look further. Nice bug report! > > So it's needed for path collections - what is that? > > A collection of a large number of paths (or polygons) that need to be > rendered quickly. > > > When I want to do > > regular plots, > > like plotting some set of points, is that needed too? If not, it > > should be optional imho. > > That's actually a tough one. On the transforms branch, by the time it > hits the rendering level, everything is a polycurve path. Determining > if something contains curves or not (which in the current implementation > would require running through the entire path, which may be quite large) > would probably be too slow. I see. In this case, it's probably not worthy to create pure python kernel. We do have some 2D plotting already, it's fast enough. But it doesn't contain so many nice features of matplotlib. > There are. But the multiple versions of the library must be > individually tested to have a hope of working -- whereas with the > compiled model, sometimes the changes between library versions will be > seamless, other times the compile will fail, both of which are > preferable to segfaulting at runtime (which admittedly is still possible > even when compiling.) I got it now. That's right. > >> Great! I'll start by looking at pyglet's freetype wrapper and see how > >> far I get. > > > > Awesome. Please ask on the list above, as I said, Alex is quite guru, so he > > will answer any technical questions. > > Thanks, Since you already asked, let's wait. :) > > Granted, this page is getting a little dated, but here's what you get > > with OpenGL: http://homepage.mac.com/arekkusu/bugs/invariance/HWAA.html > > Thanks, that's the link I was basically quoting from memory, which I'd > read when you posted it a while ago. Great reference on this topic. That's nice enough for me. Don't forget, that I am comparing no plotting, to some plotting. Well, definitely, we try to support good interaction with external packages, like numpy and matplotlib. But builtin is builtin. :) Ondrej Ondrej ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
