upcoming release

Sandro has been working hard packaging matplotlib 0.98.0 for debian
ahead of the next major debian feature freeze, and says he can get
0.98.1 in if we release it by June 24th. Charlie, can you do a
release on Monday? All developers, please take some time to fix any
bugs you are aware of and let's release 0.91.4 and 0.98.1 on Monday
pending Charlie's availability. These major debian releases only
happen once every couple of years so we want to get good versions in.

JDH

Can we shoot for Sunday night? It would be much more convenient for me at least.

  • Charlie
···

On Fri, Jun 20, 2008 at 10:20 AM, John Hunter <jdh2358@…149…> wrote:

Sandro has been working hard packaging matplotlib 0.98.0 for debian

ahead of the next major debian feature freeze, and says he can get

0.98.1 in if we release it by June 24th. Charlie, can you do a

release on Monday? All developers, please take some time to fix any

bugs you are aware of and let’s release 0.91.4 and 0.98.1 on Monday

pending Charlie’s availability. These major debian releases only

happen once every couple of years so we want to get good versions in.

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

Absolutely. I suggested Monday because I thought it would be better,
but Sunday works fine too. I'll do a round of testing Sunday morning.

JDH

···

On Fri, Jun 20, 2008 at 10:20 AM, Charlie Moad <cwmoad@...149...> wrote:

Can we shoot for Sunday night? It would be much more convenient for me at
least.

John Hunter wrote:

Sandro has been working hard packaging matplotlib 0.98.0 for debian
ahead of the next major debian feature freeze, and says he can get
0.98.1 in if we release it by June 24th. Charlie, can you do a
release on Monday? All developers, please take some time to fix any
bugs you are aware of and let's release 0.91.4 and 0.98.1 on Monday
pending Charlie's availability. These major debian releases only
happen once every couple of years so we want to get good versions in.

JDH

It is probably too late for this upcoming release, but I would like to raise a relevant question for discussion:

Can and should we rearrange the code, or install warnings and documentation, to make it absolutely clear what is supported and what is not? Ideally, if someone installs 0.98.x from any distribution, or from the tarball, the user should be able to expect *everything* to work, including all backends, examples, and plotting-related classes.

The simplest way to deal with this would be to leave everything where it is, if there is any hope that it will ever be fixed and maintained, but to put a warnings.warn and a docstring comment in any module or example that does not currently work. That way, if someone imports axes3d, they would (or at least might, unless it goes by too fast) see the warning and know that if they want it to work, they will simply have to take on its maintenance.

A second step would be to have one or more separate subdirectories to separate the maintained from the unmaintained. Doing this in a nice, consistent, easy-to-use way would take a little more work. For example, one would want to make it very easy for someone to restore a backend from broken and segregated to fully operational and available.

Eric

John, do you need anything from BIC? I'm out for a few hours (car
troubles) and will be in and out on Saturday, but likely with a laptop
in tow. So just call me on my cell if anything from bic is needed for
the release builds, I'll keep it turned on.

Cheers,

f

···

On Fri, Jun 20, 2008 at 8:22 AM, John Hunter <jdh2358@...149...> wrote:

On Fri, Jun 20, 2008 at 10:20 AM, Charlie Moad <cwmoad@...149...> wrote:

Can we shoot for Sunday night? It would be much more convenient for me at
least.

Absolutely. I suggested Monday because I thought it would be better,
but Sunday works fine too. I'll do a round of testing Sunday morning.

Nothing today -- Sunday I'll need access. I assumed bic was up more
or less all the time unless it was being maintained. Is this right?

Thanks for your help!
JDH

···

On Fri, Jun 20, 2008 at 12:54 PM, Fernando Perez <fperez.net@...149...> wrote:

John, do you need anything from BIC? I'm out for a few hours (car
troubles) and will be in and out on Saturday, but likely with a laptop
in tow. So just call me on my cell if anything from bic is needed for
the release builds, I'll keep it turned on.

Yes, it's meant to be up 24/7. The mess on Monday/Tuesday was because
I was adding backup drives, so I needed to reboot it multiple times.
That's done now and it should just work. I meant more if you needed
anything new installed for the release, or any other unusual request.
I don' want to cause a delay for you at the last minute, because I
really would like to see 0.98.1 in debian.

Cheers,

f

···

On Fri, Jun 20, 2008 at 11:13 AM, John Hunter <jdh2358@...149...> wrote:

On Fri, Jun 20, 2008 at 12:54 PM, Fernando Perez <fperez.net@...149...> wrote:

John, do you need anything from BIC? I'm out for a few hours (car
troubles) and will be in and out on Saturday, but likely with a laptop
in tow. So just call me on my cell if anything from bic is needed for
the release builds, I'll keep it turned on.

Nothing today -- Sunday I'll need access. I assumed bic was up more
or less all the time unless it was being maintained. Is this right?

Thanks for your help!

Oh I see. No, the docs stuff is a longer term project that will have
no impact on the release. Thanks, though.

JDH

···

On Fri, Jun 20, 2008 at 1:16 PM, Fernando Perez <fperez.net@...149...> wrote:

Yes, it's meant to be up 24/7. The mess on Monday/Tuesday was because
I was adding backup drives, so I needed to reboot it multiple times.
That's done now and it should just work. I meant more if you needed
anything new installed for the release, or any other unusual request.
I don' want to cause a delay for you at the last minute, because I
really would like to see 0.98.1 in debian.

I think we should do warnings, documentation, and consider removing
unmaintained code like axes3d. We talked a while back about adding separately
distributable toolkits for unmaintained and license-incompatible projects.
Maybe we could revisit that idea.

Darren

···

On Friday 20 June 2008 13:32:46 Eric Firing wrote:

John Hunter wrote:
> Sandro has been working hard packaging matplotlib 0.98.0 for debian
> ahead of the next major debian feature freeze, and says he can get
> 0.98.1 in if we release it by June 24th. Charlie, can you do a
> release on Monday? All developers, please take some time to fix any
> bugs you are aware of and let's release 0.91.4 and 0.98.1 on Monday
> pending Charlie's availability. These major debian releases only
> happen once every couple of years so we want to get good versions in.
>
> JDH

It is probably too late for this upcoming release, but I would like to
raise a relevant question for discussion:

Can and should we rearrange the code, or install warnings and
documentation, to make it absolutely clear what is supported and what is
not? Ideally, if someone installs 0.98.x from any distribution, or from
the tarball, the user should be able to expect *everything* to work,
including all backends, examples, and plotting-related classes.

The simplest way to deal with this would be to leave everything where it
is, if there is any hope that it will ever be fixed and maintained, but
to put a warnings.warn and a docstring comment in any module or example
that does not currently work. That way, if someone imports axes3d, they
would (or at least might, unless it goes by too fast) see the warning
and know that if they want it to work, they will simply have to take on
its maintenance.

A second step would be to have one or more separate subdirectories to
separate the maintained from the unmaintained. Doing this in a nice,
consistent, easy-to-use way would take a little more work. For example,
one would want to make it very easy for someone to restore a backend
from broken and segregated to fully operational and available.

I have a small program that displays a embeds a figure along with the navigation toolbar into a PyQt4 application. In version 0.91 it works fine, however, I get the following error when I try to run the program with 0.98 . An exception is raised at line 296 of the backend_qt4.py . I’ve attached the output from Eric4. Is there something I can do to my program or is this a more fundamental issue?

Thanks

Brian

–ps this issue only seems to be a problem if I’m using the navigation toolbar, a regular plot is ok.

The debugged program raised the exception unhandled AttributeError
“coordinates”
File: /usr/lib/python2.5/site-packages/matplotlib/backends/backend_qt4.py, Line: 296

StdErr: QLayout: Attempting to add QLayout “” to MyNavigationToolbar “”, which already has a layout

Hi Brian,

p, li { white-space: pre-wrap; }

I have a small program that displays a embeds a figure along with the
navigation toolbar into a PyQt4 application. In version 0.91 it works
fine, however, I get the following error when I try to run the program with
0.98 . An exception is raised at line 296 of the backend_qt4.py . I've
attached the output from Eric4. Is there something I can do to my program
or is this a more fundamental issue?ThanksBrian--ps this issue only seems
to be a problem if I'm using the navigation toolbar, a regular plot is ok.
The debugged program raised the exception unhandled AttributeError
"coordinates"
File: /usr/lib/python2.5/site-packages/matplotlib/backends/backend_qt4.py,
Line: 296StdErr: QLayout: Attempting to add QLayout "" to
MyNavigationToolbar "", which already has a layout

Version 98 changed the backend_qt4 toolbar so it is a true Qt toolbar, which
already has a layout. I guess you need to use the existing layout, rather than
adding a new one.

If that doesn't help you, please post a *short* standalone script that
reproduces the problem. Its hard to diagnose these things based on so little
information.

Darren

···

On Sunday 22 June 2008 11:01:36 B Clowers wrote:

I'll be traveling most of the day so I will be mostly out of
touch(some blackberry access), but I did a round of testing on the
branch and the trunk and things look good to go from my end.

JDH

···

On Fri, Jun 20, 2008 at 10:20 AM, Charlie Moad <cwmoad@...149...> wrote:

Can we shoot for Sunday night? It would be much more convenient for me at
least.

The releases and builds are up. Please test them out, and I’ll leave the announcements to you, John.

  • Charlie
···

On Jun 22, 2008, at 12:43 PM, John Hunter wrote:

On Fri, Jun 20, 2008 at 10:20 AM, Charlie Moad <cwmoad@…149…> wrote:

Can we shoot for Sunday night? It would be much more convenient for me at
least.

I’ll be traveling most of the day so I will be mostly out of
touch(some blackberry access), but I did a round of testing on the
branch and the trunk and things look good to go from my end.

JDH

I just downloaded it (MD5Sum: 1f673f82eb4f7422c1e45545f8e083d4) and I
plan to upgrade the package in Debian this evening.

Thanks a lot for the huge work you've done to fulfill Debian requirements!

Cheers,
Sandro

···

On Mon, Jun 23, 2008 at 04:43, Charles Moad <cwmoad@...149...> wrote:

The releases and builds are up. Please test them out, and I'll leave the
announcements to you, John.

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

mpl 0.98.1 has just been uploaded in unstable (tomorrow will be
available on debian mirrors hosts).

Thanks for the support,
Sandro

···

On Mon, Jun 23, 2008 at 13:48, Sandro Tosi <matrixhasu@...149...> wrote:

On Mon, Jun 23, 2008 at 04:43, Charles Moad <cwmoad@...149...> wrote:

The releases and builds are up. Please test them out, and I'll leave the
announcements to you, John.

I just downloaded it (MD5Sum: 1f673f82eb4f7422c1e45545f8e083d4) and I
plan to upgrade the package in Debian this evening.

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

Thank you -- that was really fast. So far no bug reports -- crossing
fingers :slight_smile:

JDH

···

On Mon, Jun 23, 2008 at 5:03 PM, Sandro Tosi <matrixhasu@...149...> wrote:

mpl 0.98.1 has just been uploaded in unstable (tomorrow will be
available on debian mirrors hosts).

"Sandro Tosi" <matrixhasu@...149...> writes:

>> The releases and builds are up. Please test them out, and I'll leave the
>> announcements to you, John.
>
> I just downloaded it (MD5Sum: 1f673f82eb4f7422c1e45545f8e083d4) and I
> plan to upgrade the package in Debian this evening.

mpl 0.98.1 has just been uploaded in unstable (tomorrow will be
available on debian mirrors hosts).

I've installed this (in a chroot).

All the wx examples I've tried seem fail at the line:

from wx import *

eg:

cjtest@...612...:/usr/share/doc/python-matplotlib-doc/examples/user_interfaces$ ./embedding_in_wx.py
Traceback (most recent call last):
  File "./embedding_in_wx.py", line 45, in <module>
    from wx import *
AttributeError: 'module' object has no attribute '__DocFilter'

This must be a bug in the Debian package providing wx (which I ought
to report). Is it good practice though?

Thanks for the support,

Indeed - and thanks for packaging it so rapidly.

Chris

···

On Mon, Jun 23, 2008 at 13:48, Sandro Tosi <matrixhasu@...149...> wrote:
> On Mon, Jun 23, 2008 at 04:43, Charles Moad <cwmoad@...149...> wrote: