John and others,
I just committed a small patch that add gid(group id) as a property of
the Artist.
And also some small changes here and there, so that the svg backend
use this gid as the ID of each element. To do this, I slightly changed
the calling convention of the open_group() methods in Backe
Hello,
I'm thinking about slightly modifying the draw() method of the Axes
class, so that user can optionally
calculate the position of the axes at drawing time. It may be
considered as a general version of the apply_aspect() method.
For example, instead of "self.apply_aspect()" call in the draw
Dear all,
I have now implemented the draw_path_collection, draw_quad_mesh, and
draw_markers methods in the Mac OS X native backend (see patch 2179017 at
http://sourceforge.net/tracker/?func=detail&atid=560722&aid=2179017&group_id=80706).
Some timings are below. In terms of raw drawing speed, the
On Tue, Dec 16, 2008 at 10:57 PM, Sandro Tosi wrote:
> Hello Darren,
>
> On Tue, Dec 16, 2008 at 16:03, Darren Dale wrote:
>> It seems like the documentation should be a separately installable package
>> as far as package managers are concerned.
>
> We already have separate the doc from other mpl
On Tue, Dec 16, 2008 at 15:10, Michael Droettboom wrote:
> One question to ask is whether we need both the .pdf and .html manuals, or
> whether that could be broken up into two packages. That seems like an easy
> one if that fits Debian policies (which I know nothing about) -- and
> wouldn't degr
Hello Darren,
On Tue, Dec 16, 2008 at 16:03, Darren Dale wrote:
> It seems like the documentation should be a separately installable package
> as far as package managers are concerned.
We already have separate the doc from other mpl parts, to be precise
we have these pkgs:
python-matplotlib - t
On Tue, Dec 16, 2008 at 15:39, John Hunter wrote:
> On Tue, Dec 16, 2008 at 8:10 AM, Michael Droettboom wrote:
>
>> Another option would be to not generate the high-res png and pdf
>> examples. (Either or both). Just removing them after the fact won't
>> work, since one would end up with broken
Jeff,
Is it possible to install the basemap data into a different directory?
I'm trying to set up a tool delivery layout for our users that allows me to
rapidly update packages that tend to change. We have a core set of software
that our code is built on and it's a lot of work for us to update
On Tue, Dec 16, 2008 at 1:04 PM, Christopher Barker
wrote:
> for instance, I renamed:
> matplotlib-0.98.3-py2.5-macosx-10.3.egg
>
> to:
> matplotlib-0.98.3-py2.5.egg
>
> and easy_install installed it without a hitch on 10.4
>
> Indeed, that name may work for 10.5 too.
I've posted new eggs and a
On Tue, Dec 16, 2008 at 19:09, John Hunter wrote:
> On Tue, Dec 16, 2008 at 12:03 PM, Sandro Tosi wrote:
>> Hello,
>> I see API_CHANGES is removed from tarball. it's a nice-to-have file,
>> in order to allow a smooth transition from old to new version.
>>
>> Is it intentional? Is there another so
Charlie Moad wrote:
> Most people
> get a successful install, but then setuptools tries to go out and grab
> the source anyways. I can't say that I know a good solution for osx.
This may be moot due to what John H. has done, but I thought all you
need to do to stop setuptools from going and gra
On Tue, Dec 16, 2008 at 09:12:24AM -0800, Drain, Theodore R wrote:
> Continued from: requesting permission to remove traits and configobj...
> Gael,
> There might be ways to handle these problems. A lot of depends on what we're
> trying to test. I agree that if we take the example scripts, run
On Tue, Dec 16, 2008 at 12:03 PM, Sandro Tosi wrote:
> Hello,
> I see API_CHANGES is removed from tarball. it's a nice-to-have file,
> in order to allow a smooth transition from old to new version.
>
> Is it intentional? Is there another source from this information? is
> it not useful anymore?
d
Hello,
I see API_CHANGES is removed from tarball. it's a nice-to-have file,
in order to allow a smooth transition from old to new version.
Is it intentional? Is there another source from this information? is
it not useful anymore?
Cheers,
--
Sandro Tosi (aka morph, Morpheus, matrixhasu)
My websi
On Tue, Dec 16, 2008 at 11:12 AM, Drain, Theodore R
wrote:
> - Embed a font with the tests to eliminate font server differences (no
> experience with this so I'm not sure how hard this would be). We could even
> create a dummy font that just has black squares for each character - it still
> t
Continued from: requesting permission to remove traits and configobj...
Gael,
There might be ways to handle these problems. A lot of depends on what we're
trying to test. I agree that if we take the example scripts, run them, and
save the plots, we'll never get an automated test harness to fig
On Tue, Dec 16, 2008 at 8:42 AM, John Hunter wrote:
>> Yep, 0.5 it is
>
> Let me correct that -- I will test Darren's patch and if we can make
> it work with an earlier sphinx I'm happy to try. Stay tuned. Darren,
> can I assume you have tested this with 0.4.2 and the docs are building
> for yo
On Tue, Dec 16, 2008 at 4:20 AM, Sandro Tosi wrote:
> -shutil.copy('mpl_data/matplotlibrc', '_static/matplotlibrc')
> +shutil.copy('../lib/matplotlib/mpl-data/matplotlibrc',
> '_static/matplotlibrc')
>
This has already been committed to the 98.5 branch.
JDH
-
On Tue, Dec 16, 2008 at 9:39 AM, John Hunter wrote:
> On Tue, Dec 16, 2008 at 8:10 AM, Michael Droettboom
> wrote:
>
> > Another option would be to not generate the high-res png and pdf
> > examples. (Either or both). Just removing them after the fact won't
> > work, since one would end up wit
On Tue, Dec 16, 2008 at 9:48 AM, John Hunter wrote:
> On Mon, Dec 15, 2008 at 10:02 AM, Darren Dale wrote:
>
> > You're right, the error does not occur with sphinx-0.5. It looks like the
> > API for registering nodes has changed as of 0.5. The development branch
> of
> > sphinx was throwing erro
On Mon, Dec 15, 2008 at 10:02 AM, Darren Dale wrote:
> You're right, the error does not occur with sphinx-0.5. It looks like the
> API for registering nodes has changed as of 0.5. The development branch of
> sphinx was throwing errors when it got to latex, so I had a look and came up
> with some
On Tue, Dec 16, 2008 at 8:40 AM, John Hunter wrote:
> On Tue, Dec 16, 2008 at 6:12 AM, Sandro Tosi wrote:
>
>> So, should the doc be build using sphinx 0.5? Would it be the standard
>> version of sphinx used by mpl now on? Just to know what dependency to
>> throw in once building mpl for Debian :
On Tue, Dec 16, 2008 at 6:12 AM, Sandro Tosi wrote:
> So, should the doc be build using sphinx 0.5? Would it be the standard
> version of sphinx used by mpl now on? Just to know what dependency to
> throw in once building mpl for Debian :)
Yep, 0.5 it is.
---
On Tue, Dec 16, 2008 at 8:10 AM, Michael Droettboom wrote:
> Another option would be to not generate the high-res png and pdf
> examples. (Either or both). Just removing them after the fact won't
> work, since one would end up with broken links from the docs. We would
> also have to change the
One question to ask is whether we need both the .pdf and .html manuals,
or whether that could be broken up into two packages. That seems like
an easy one if that fits Debian policies (which I know nothing about) --
and wouldn't degrade the documentation experience at all.
Is there any way to t
Hello,
the problem is this:
$ ls -l python-matplotlib-doc_0.98.5-1_all.deb
-rw-r--r-- 1 morph morph 91141234 2008-12-16 10:39
python-matplotlib-doc_0.98.5-1_all.deb
90M of doc package is a "little bit"... and expanded it's
$ du . -hs
119M
In this package we install: doc/build/html/
doc/build/la
On Mon, Dec 15, 2008 at 17:02, Darren Dale wrote:
> (John suggested in a private email to try upgrading to sphinx-0.5.)
>
> You're right, the error does not occur with sphinx-0.5. It looks like the
> API for registering nodes has changed as of 0.5. The development branch of
> sphinx was throwing e
Hello John and Darren,
On Sun, Dec 14, 2008 at 22:05, John Hunter wrote:
> On Sun, Dec 14, 2008 at 7:46 PM, Sandro Tosi wrote:
>
>> Well, what I'm actually asking is: can I use any matplotlibrc file (be
>> it from any location in the tarball or forged during build process) or
>> the one in doc/m
28 matches
Mail list logo