matplotlib-devel Mailing List for matplotlib

That is unfortunate that we can't have a summit before/after SciPy 2014. I
have also booked my flights and hotel, and the only time I would have to
fit a "summit" outside of SciPy 2014 would be Saturday, July 5th in the
evening.
I will be there, though, for the entire conference (including both sprint
days). Perhaps we can have a somewhat formalized Birds-of-a-feather
session? Maybe with a discussion panel and some short presentations on our
visions for future matplotlib development?
Ben Root
On Fri, May 30, 2014 at 9:35 AM, Michael Droettboom <md...@st...> wrote:
> Hello all,
>
> Sorry to be writing this at this late point, but I've been hoping I
> could find a way around it. I won't be able to attend an extra day at
> either end of Scipy year, both due to personal commitments and new
> funding constraints at NASA. I do plan to attend/host the matplotlib
> sprint again, however, which is not a bad opportunity to catch up on
> some of these issues.
>
> So, an extra developer summit day is still possible if someone else is
> able to organize it -- I just, unfortunately, won't be able to attend.
> We can still use the matplotlib donated funds to cover the cost of the
> extra hotel night (assuming the numbers of people wanting to do that is
> not too large) and meeting space (if the cost is not too high, though
> maybe locals like Damon have a connection for free and/or cheap space).
> For reimbursement, I would need a receipt for that hotel night (ideally
> with that one night broken out individually), which will then be
> submitted to numfocus, who will reimburse you directly.
>
> Sorry to be uncommunicative on this (and uncommunicative in general
> lately). I hope something can still work out at this late date!
>
> Mike
>
> On 02/27/2014 11:28 AM, Michael Droettboom wrote:
> > How many matplotlib developers are planning to attend SciPy this year?
> >
> > If we used some of our funds to support an extra hotel night, would any
> > of you be interested in spending an extra day for a "matplotlib
> > developer summit" to discuss matplotlib projects? This would be in
> > addition to the sprints, which I see probably being a larger group. Your
> > response isn't a committment at this point, I'm just trying to gauge how
> > much interest there might be.
> >
> > Mike
> >
>
>
> --
> Michael Droettboom
> Science Software Branch
> Space Telescope Science Institute
>
> http://www.droettboom.com
>
>
>
> ------------------------------------------------------------------------------
> Time is money. Stop wasting it! Get your web API in 5 minutes.
> www.restlet.com/download
> http://p.sf.net/sfu/restlet
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

Hi,
Sorry for those of you on the numpy mailing list - this email will
seem a bit familiar.
I want to rename the matplotlib wheel OSX wheel files on pypi so they
will also install into homebrew, macports and system python.
I'm just doing this now for numpy and scipy, but I wanted to make sure
y'all had no objections for matplotlib.
The logic of the renaming is explained here:
https://github.com/MacPython/wiki/wiki/Spinning-wheels
Basically, by adding extra 'platform tags' to the wheel filename, we
can signal to pip that the wheel is compatible with these other
systems.
The page above explains why the wheels I built are compatible with the
other Pythons, and this test grid:
https://travis-ci.org/matthew-brett/scipy-stack-osx-testing/builds/26482436
confirms that the renamed wheels install and test OK on homebrew,
macports, system python.
So, I propose to rename the current matplotlib python 2.7 wheel from:
matplotlib-1.3.1-cp27-none-macosx_10_6_intel.whl
to
matplotlib-1.3.1-cp27-none-macosx_10_6_intel.macosx_10_9_intel.macosx_10_9_x86_64.whl
and so on for python 3.3, 3.4.
I don't think this has a downside, but I'm happy for any feedback,
Cheers,
Matthew