matplotlib-devel Mailing List for matplotlib

On Fri, Mar 23, 2012 at 12:55 PM, Russell E. Owen <ro...@uw...> wrote:

>
> I have uploaded the Mac builds (no Python 2.6 yet; do we really need
> that?). They pass all unit tests and the 32-bit version seems to work
> well with my software.
>
>
Might be nice to upload some python2.6 builds for the actual release, but I
don't see this as necessary for the testers since there are no important
differences between 2.6 and 2.7 as far as v1.1.x is concerned.

JDH

On Fri, Mar 23, 2012 at 12:55 PM, Russell E. Owen <ro...@uw...> wrote:

>
> The included pytz is outdated (and I did not bother to uprev it in the
> binaries I uploaded); would somebody be willing to update that before we
> cut the final releases, or is that considered too risky at this late
> date?
>
>
It feels too risky to me post-rc.  How critical do you think the updates
are?  We are planning on moving our attention to a master release 1.2.x as
soon as this is out, and we can update ahead of that.  And for people who
need the latest, they can always install their own.

JDH

On Fri, Mar 23, 2012 at 12:21 PM, Sandro Tosi <mo...@de...> wrote:

>
> I'll start testing debian packaging right away; for our package we
> also need the sampledata tarball: can I reuse the one for 1.1.0 or is
> a new one needed?
>
>
You can use the same one -- because this is a bugfix release, we have not
introduced any new features, examples or data.  Just bugfixes.

JDH

In article 
<CAG...@ma...>,
 John Hunter <jd...@gm...> wrote:

> On Mon, Mar 19, 2012 at 12:58 PM, John Hunter 
> <jd...@gm...> wrote:
> 
> > I think we are pretty close to cleaning up issues and PRs related to
> > v1.1.x, so I'd like to cut the release candidate this Thursday.  Let's
> > continue to hammer on closing open issues and pull requests, and flag
> > anything that needs to be addressed before the release as
> > "release_critical" in the issue tracker.  If there are show stoppers I am
> > not aware of, chime in.
> >
> >
> The tarballs for the v1.1.1 release candidate 1 (rc1) are uploaded to and
> are available for testing and building binaries
> 
> 
> https://sourceforge.net/projects/matplotlib/files/matplotlib/matplotlib-1.1.1/

I have uploaded the Mac builds (no Python 2.6 yet; do we really need 
that?). They pass all unit tests and the 32-bit version seems to work 
well with my software.

The included pytz is outdated (and I did not bother to uprev it in the 
binaries I uploaded); would somebody be willing to update that before we 
cut the final releases, or is that considered too risky at this late 
date?

-- Russell

Hi John,

On Fri, Mar 23, 2012 at 03:18, John Hunter <jd...@gm...> wrote:
> The tarballs for the v1.1.1 release candidate 1 (rc1) are uploaded to and
> are available for testing and building binaries
>
>  https://sourceforge.net/projects/matplotlib/files/matplotlib/matplotlib-1.1.1/
>
> After the binaries are up, I'll send out a notice to the users list
> requesting wider testing, but intrepid developers can begin now.

I'll start testing debian packaging right away; for our package we
also need the sampledata tarball: can I reuse the one for 1.1.0 or is
a new one needed?

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

On Thu, Mar 22, 2012 at 10:57 PM, Christoph Gohlke <cg...@uc...> wrote:

>
>
> Windows binaries, including the test files, are at <
> http://www.lfd.uci.edu/~**gohlke/pythonlibs/#matplotlib<http://www.lfd.uci.edu/~gohlke/pythonlibs/#matplotlib>
> >**.
>
> All my attempts to upload the files to SF failed (no error report).
>
> I'll run tests later.
>


Hey Christoph, not sure why you are unable to upload, since I have you
designated as a "release manager" on the sf site, but thanks for building
these and I've uploaded these and they are good to go.

I've included this in openSUSE's matplotlib packages, it seems to work great.

-Todd

On Mon, Mar 19, 2012 at 10:08 PM, Pierre Raybaut
<pie...@gm...> wrote:
> Hi all,
>
> Is anyone interested in including the Matplotlib QtDesigner plugin
> which I wrote for Python(x,y)?
>
> The code is quite simple and hasn't evolved for a while now (3 years)
> but apparently it is still appreciated by users even outside
> Python(x,y).
>
> Here are the two files which are necessary to make this plugin work:
> http://code.google.com/p/pythonxy/source/browse/src/python/matplotlib/QtDesigner_Plugins/matplotlibwidget.py
> http://code.google.com/p/pythonxy/source/browse/src/python/matplotlib/QtDesigner_Plugins/PyQt4/plugins/designer/python/matplotlibplugin.py
>
> The directory struture also has its importance:
> http://code.google.com/p/pythonxy/source/browse/#hg%2Fsrc%2Fpython%2Fmatplotlib%2FQtDesigner_Plugins
>
> Cheers,
> Pierre
>
> ---------- Message transféré ----------
> De : todd rme <tod...@gm...>
> Date : 11 mars 2012 12:14
> Objet : [python(x,y)] Upstream Matplotlib Qt Designer Plugin
> À : "python(x,y)" <pyt...@go...>
>
>
> I notice that python(x,y) has a matplotlib plugin for Qt Designer.  I
> think this would be very helpful for general users of matplotlib
> outside of python(x,y).  Is there any possibility of submitting this
> plugin upstream for inclusion with the official matplotlib release?
> That way people who aren't using python(x,y) (for instance Linux users
> who are using their official distribution python packages) could
> benefit from the plugin as well.  Thank you very much.
>
> -Todd
>
> --
> You received this message because you are subscribed to the Google
> Groups "python(x,y)" group.
> To post to this group, send email to pyt...@go....
> To unsubscribe from this group, send email to
> pyt...@go....
> For more options, visit this group at
> http://groups.google.com/group/pythonxy?hl=en.

On 3/22/2012 7:18 PM, John Hunter wrote:
>
>
> On Mon, Mar 19, 2012 at 12:58 PM, John Hunter <jd...@gm...
> <mailto:jd...@gm...>> wrote:
>
>     I think we are pretty close to cleaning up issues and PRs related to
>     v1.1.x, so I'd like to cut the release candidate this Thursday.
>       Let's continue to hammer on closing open issues and pull requests,
>     and flag anything that needs to be addressed before the release as
>     "release_critical" in the issue tracker.  If there are show stoppers
>     I am not aware of, chime in.
>
>
> The tarballs for the v1.1.1 release candidate 1 (rc1) are uploaded to
> and are available for testing and building binaries
>
> https://sourceforge.net/projects/matplotlib/files/matplotlib/matplotlib-1.1.1/
>
> After the binaries are up, I'll send out a notice to the users list
> requesting wider testing, but intrepid developers can begin now.
>
> The reference github commit for rc1 is
> https://github.com/matplotlib/matplotlib/commit/c5593eea91d82559c6e30e999635b93a35a13bc9
>
> There was a heroic effort by Michael Droetboom and Thomas Robitaille in
> the last two days to get past the freetype version and platform specific
> rendering issues, mainly revolving around anti-aliasing, and we are
> pretty close to there, so going forward we can expect almost all of the
> tests to pass for almost all of the developers, and have a mechanism for
> adding freetype version dependent known fails.  This will make our tests
> much more useful.  Thomas in particular did a crazy amount of testing on
> every conceivable combination of freetype settings and versions which
> really pushed the success of this effort, and Michael stayed right there
> with him committing fixes faster than any human could test.
>
> https://github.com/matplotlib/matplotlib/pull/779
>
> This will be the last release supporting python 2.4 and in all
> likelihood the last of the 1.1.x line, so I'd like to make it rock
> solid.  Testing will be appreciated.  For those of you who prefer the
> github interface/workflow, I'm opening up an "open thread" issue
>
> https://github.com/matplotlib/matplotlib/issues/791
>
> Thanks to all who've contributed -- I'll work up detailed notes for the
> real release, hopefully next week.  Russell and Christoph, you should be
> able to access to file manager interface directly on sf to upload your
> binaries, but let me know if you have any troubles.
>
> JDH
>

Hi John,

Windows binaries, including the test files, are at 
<http://www.lfd.uci.edu/~gohlke/pythonlibs/#matplotlib>.

All my attempts to upload the files to SF failed (no error report).

I'll run tests later.

Christoph

On Mon, Mar 19, 2012 at 12:58 PM, John Hunter <jd...@gm...> wrote:

> I think we are pretty close to cleaning up issues and PRs related to
> v1.1.x, so I'd like to cut the release candidate this Thursday.  Let's
> continue to hammer on closing open issues and pull requests, and flag
> anything that needs to be addressed before the release as
> "release_critical" in the issue tracker.  If there are show stoppers I am
> not aware of, chime in.
>
>
The tarballs for the v1.1.1 release candidate 1 (rc1) are uploaded to and
are available for testing and building binaries


https://sourceforge.net/projects/matplotlib/files/matplotlib/matplotlib-1.1.1/

After the binaries are up, I'll send out a notice to the users list
requesting wider testing, but intrepid developers can begin now.

The reference github commit for rc1 is
https://github.com/matplotlib/matplotlib/commit/c5593eea91d82559c6e30e999635b93a35a13bc9

There was a heroic effort by Michael Droetboom and Thomas Robitaille in the
last two days to get past the freetype version and platform specific
rendering issues, mainly revolving around anti-aliasing, and we are pretty
close to there, so going forward we can expect almost all of the tests to
pass for almost all of the developers, and have a mechanism for adding
freetype version dependent known fails.  This will make our tests much more
useful.  Thomas in particular did a crazy amount of testing on every
conceivable combination of freetype settings and versions which really
pushed the success of this effort, and Michael stayed right there with him
committing fixes faster than any human could test.

https://github.com/matplotlib/matplotlib/pull/779

This will be the last release supporting python 2.4 and in all likelihood
the last of the 1.1.x line, so I'd like to make it rock solid.  Testing
will be appreciated.  For those of you who prefer the github
interface/workflow, I'm opening up an "open thread" issue

https://github.com/matplotlib/matplotlib/issues/791

Thanks to all who've contributed -- I'll work up detailed notes for the
real release, hopefully next week.  Russell and Christoph, you should be
able to access to file manager interface directly on sf to upload your
binaries, but let me know if you have any troubles.

JDH