Re: [matplotlib-devel] AttributeError: 'module' object has no attribute 'GraphicsContext'

2008-06-17 Thread Manuel Metz 
Chris Walker wrote:
> "John Hunter" <[EMAIL PROTECTED]> writes:
> 
>> On Fri, Jun 13, 2008 at 9:25 AM, Chris Walker
>> <[EMAIL PROTECTED]> wrote:
>>
 So if we want to support stable, *and*
 the latest releases, we've got a lot of ongoing compatibility work to
 do.  For backend maintainers willing to do it, I think that will be
 good.  But I am hesitant to target such a slow moving repository as a
 requirement.
>>> Would the next debian release (lenny) be a better target for
>>> development versions of matplotlib?
>>>
>>> What version of matplotlib do you want to go into the next debian release?
>> Hi Chris -- thanks for all the information.  
> 
> Pleasure, Hope it was useful, but please note I don't speak for the
> Debian Matplotlib maintainers.
> 
> There are some things I need to clarify though.
> 
> 
>> Since 0.98 requires numpy
>> 1.1, 0.98.1 (a bugfix release slated for next week or the week after)
>> should be in unstable and 0.91.4 (again a bugfix scheduled for next
>> week or the week after) should be in testing 
> 
> Ah, I think you may have misunderstood how debian
> stable/testing/unstable works.
> 
> A grossly oversimplified view[1] is as follows.
> 
> 1) A new version of the package is uploaded to sid (unstable) 
> 
> 2) When the package has been in sid (unstable) for 10 days, it is a
>candidate for moving to lenny (testing). when they can do so
>without breaking other packages lenny (testing).
> 
> 3) Eventually, lenny is released as the stable distribution, and you
>are stuck with it for a year or two (except security or dataloss
>bugs). 
> 
> so it sounds like 0.98.x should be what is uploaded to unstable (from
> where it will migrate to testing).
> 
>> and 0.91.2 should be in
>> stable.  
> 
> The version in etch (stable) is only likely to be upgraded (from
> 0.87.7-0.3) if there are major bugs (such as security problems or data
> loss issues). See http://www.debian.org/security/
> 
> 
>> I find this a bit conservative, since I think numpy 1.1
>> should be in testing 
> 
> It was only uploaded 3 days ago, so in theory could migrate in 7 days
> time.
> 
>> along with matplotlib 0.98.1, 
> 
> http://packages.qa.debian.org/m/matplotlib.html gives debian package
> information on matplotlib - including which versions are in
> stable,testing and unstable. Hopefully 0.98.0 or 0.98.1 packages will
> be uploaded soon. If not, then giving the maintainers a push to ensure
> they are in the next debian stable would be a good idea.

Hi,
   the debian maintainers are already aware of the new versions, see
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=486074

According to them, matplotlib 0.98.x will be uploaded to experimental 
first, before it migrates to unstable. Unstable has been updated to 
0.91.3 some days ago.

Manuel





-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Re: [matplotlib-devel] Number of points in legend

2008-06-17 Thread Stéfan van der Walt 
Hi John

2008/6/12 John Hunter <[EMAIL PROTECTED]>:
> On Thu, Jun 12, 2008 at 7:56 AM, Stéfan van der Walt <[EMAIL PROTECTED]> 
> wrote:
>
>> linestyle 'x' ---> legend  '   x   '
>> linestyle '-x' ---> legend '---x---'
>>
>> Has this been considered before?  If not, I'll write a patch.
>
> I think this is just something that has been overlooked.  The legend
> code is quite old, so don't be surprised if it looks a little crusty
> in there, as it was one of the early features, and it has been updated
> piecemeal with new features.  A patch would be great.

The idea I had was to plot two lines on top of each other: one for the
line-style, and one for the bullets.  Unfortunately, I can't get the
lines to co-incide.  Could you look at the attached toy-patch and tell
me where I am going wrong?  Note how the X is somewhat below the line.

Thanks
Stéfan


matplotlib_legend.patch
Description: Binary data
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Re: [matplotlib-devel] AttributeError: 'module' object has no attribute 'GraphicsContext'

2008-06-17 Thread Sandro Tosi 
Hi guys,
sorry to have spotted it out late (the thread subject don't help :)
and thanks to Manuel to have notified me about this thread.

>   the debian maintainers are already aware of the new versions, see
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=486074
>
> According to them, matplotlib 0.98.x will be uploaded to experimental
> first, before it migrates to unstable. Unstable has been updated to
> 0.91.3 some days ago.

My plan (as one of maintainers of matplotlib in Debian) is to keep
uploading 0.91.x in unstable, so it can migrate to testing (the
staging area to prepare the next stable release) when needed, and
prepare the 0.98.x package into experimental. I need this since 0.98
introduced API changes, and I need to let depending packages check if
they are compatible with this new version (if not, adapting them)
before uploading to unstable and break things.

Since numpy in unstable is already at 1.1.0 (scheduled to be migrated
in testing in few days), I try my best to have 0.98.x in unstable
asap, so to let lenny (the upcoming stable release) ship 0.98.x!

Cheers,
Sandro

-- 
Sandro Tosi (aka morph, Morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Re: [matplotlib-devel] AttributeError: 'module' object has no attribute 'GraphicsContext'

2008-06-17 Thread John Hunter 
On Tue, Jun 17, 2008 at 9:58 AM, Sandro Tosi <[EMAIL PROTECTED]> wrote:

> My plan (as one of maintainers of matplotlib in Debian) is to keep
> uploading 0.91.x in unstable, so it can migrate to testing (the
> staging area to prepare the next stable release) when needed, and
> prepare the 0.98.x package into experimental. I need this since 0.98
> introduced API changes, and I need to let depending packages check if
> they are compatible with this new version (if not, adapting them)
> before uploading to unstable and break things.
>
> Since numpy in unstable is already at 1.1.0 (scheduled to be migrated
> in testing in few days), I try my best to have 0.98.x in unstable
> asap, so to let lenny (the upcoming stable release) ship 0.98.x!

Hi Sandro, thanks for writing and all the work packaging matplotlib
for debian.

Just to be clear on the API changes: every release of matplotlib
pretty much has some API changes which are documented in the
API_CHANGES file).  They are usually quite minor, and 95% of our users
interact with matplotlib through the pylab/pyplot interface, which is
*extremely* stable, and pretty much hasn't changed since 0.1 and
probably will never change much.

The changes affect folks who use the matplotlib API directly, which
are probably 5% of our users, who are almost by definition the power
users.  0.98 introduced significantly more API changes (and features)
than a typical major release (hence the big bump in version number)
but nonetheless these have a very minor user facing impact.  We have
nearly 100 figure generating tests in our regression suite and all of
them are passing.  The major changes to the API occur for people
manipulating transformations directly, which is almost noone.

We are certainly discovering and fixing issues now that we are getting
some users on it with the 0.98.0 release, but the majority of these
are not API issues, but plain-ol-bugs or backend version issues,
etc...  We are trying to get a bug fix release out ASAP to address
these, but we want to balance getting as many bug reports in before we
do this since none of the bugs reported thus far have been critical.

Thanks again,
JDH

-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Re: [matplotlib-devel] matplotlib 0.98.0 colors problem LineCollection

2008-06-17 Thread Mátyás János 
Hi,

thank you for the fix. It works great now.


Mátyás János


On Mon, 16 Jun 2008 08:15:39 -0400
Michael Droettboom <[EMAIL PROTECTED]> wrote:

> Thanks.  mpl was applying the default alpha of 1.0 to the set of
> colors rather than ignoring it when an alpha is provided for each
> color.  This is now fixed in SVN r5554
> 
> Cheers,
> Mike
> 
> Mátyás János wrote:
> > Hi,
> >
> > setting colors with transparency no longer works for me in
> > 0.98.0, but worked before in 0.91.3:
> >
> > c = matplotlib.collections.LineCollection(lines, colors =
> > lineColors)
> >
> > This shows the lines only with the base colors without transparency.
> >
> > However, if I modify the code to the following, the colors shows
> > properly with transparency:
> >
> > c = matplotlib.collections.LineCollection(lines)
> > c.set_color(lineColors)
> >
> >
> > Mátyás János

-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

[matplotlib-devel] Showing base classes in autodoc

2008-06-17 Thread Michael Droettboom 
My patch to show the base classes of each class in Sphinx autodoc has 
been accepted.

http://groups.google.com/group/sphinx-dev/browse_thread/thread/cc9c3d80a4e483b9

I've updated our docs to use this feature (it requires adding the 
'show-inheritance' option to the autodoc directives).  This requires 
that everyone generating the docs does a "svn up" on Sphinx.  Our 
documentation instructions already say to use SVN Sphinx, so this isn't 
really a new requirement, and hopefully before long this will be part of 
a Sphinx release.

Cheers,
Mike

-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA


-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

[matplotlib-devel] pdf file path or other problem in docs?

2008-06-17 Thread Eric Firing 
I did svn up on sphinx(0.3dev-20080617) and mpl (r5583), reinstalled 
both, and tried to build the docs.

It got through the html and failed on the latex:

...

[4]
Chapter 2.
(/usr/share/texmf-texlive/tex/latex/txfonts/ot1txr.fd)
(/usr/share/texmf-texlive/tex/latex/txfonts/utxsya.fd)
(/usr/share/texmf-texlive/tex/latex/txfonts/utxsyb.fd)
(/usr/share/texmf-texlive/tex/latex/txfonts/utxmia.fd)
(/usr/share/texmf-texlive/tex/latex/txfonts/utxsyc.fd)

LaTeX Warning: File `../pyplots/pyplot_simple.pdf' not found on input 
line 209.



!pdfTeX error: pdflatex (file ../pyplots/pyplot_simple.pdf): cannot find 
image
file
  ==> Fatal error occurred, no output PDF file produced!
Rendering LaTeX failed.

The file it is complaining about exists in several places:

[EMAIL PROTECTED]:~/programs/py/mpl/mpl_trunk/doc$ find . -name 
'pyplot_simple*'
./build/html/_images/pyplot_simple.png
./build/html/_images/pyplot_simple.pdf
./build/html/pyplots/.svn/text-base/pyplot_simple.py.svn-base
./build/html/pyplots/pyplot_simple.py
./build/html/pyplots/pyplot_simple.png
./build/html/pyplots/pyplot_simple.pdf
./build/html/pyplots/pyplot_simple.hires.png
./build/latex/pyplot_simple.png
./build/latex/pyplot_simple.pdf
./pyplots/.svn/text-base/pyplot_simple.py.svn-base
./pyplots/pyplot_simple.py
./pyplots/pyplot_simple.png
./pyplots/pyplot_simple.pdf
./pyplots/pyplot_simple.hires.png
./users/figures/pyplot_simple.png


And it is indeed a pdf:

[EMAIL PROTECTED]:~/programs/py/mpl/mpl_trunk/doc$ find . -name 
'pyplot_simple.pdf' -exec file {} \;
./build/html/_images/pyplot_simple.pdf: PDF document, version 1.4
./build/html/pyplots/pyplot_simple.pdf: PDF document, version 1.4
./build/latex/pyplot_simple.pdf: PDF document, version 1.4
./pyplots/pyplot_simple.pdf: PDF document, version 1.4

Eric

-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Re: [matplotlib-devel] pdf file path or other problem in docs?

2008-06-17 Thread John Hunter 
On Tue, Jun 17, 2008 at 1:56 PM, Eric Firing <[EMAIL PROTECTED]> wrote:

> I did svn up on sphinx(0.3dev-20080617) and mpl (r5583), reinstalled
> both, and tried to build the docs.

I see this tool.  This looks like a sphinx change that we are not
accounting for (or a bug).  There is a sphinx log message:

r64295 | georg.brandl | 2008-06-15 07:31:16 -0700 (Sun, 15 Jun
2008) | 2 lines

   Add image format handling.

There are significant changes to image handling, how they are copied
etc, between the prior sphinx version and HEAD, so I suspect we need
to figure out if we need to do something different or if it is a
plain-ol-bug.  I suspect the latter.

I'll post on the sphinx list.

JDH

-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel