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
I want to rename the matplotlib wheel OSX wheel files on pypi so they
will also install into homebrew, macports and system python.
+1
matplotlib-1.3.1-cp27-none-macosx_10_6_intel.macosx_10_9_intel.macosx_10_9_x86_64.whl
what is this going to do on OS-X 10.7 and 10.8 systems running homebrew or
macports pythons? It seems this list could get pretty long!
-Chris
···
On Mon, Jun 2, 2014 at 11:48 AM, Matthew Brett <matthew.brett@...149...> wrote:
--
Christopher Barker, Ph.D.
Oceanographer
Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Chris.Barker@...236...
Hi,
I want to rename the matplotlib wheel OSX wheel files on pypi so they
will also install into homebrew, macports and system python.
+1
matplotlib-1.3.1-cp27-none-macosx_10_6_intel.macosx_10_9_intel.macosx_10_9_x86_64.whl
what is this going to do on OS-X 10.7 and 10.8 systems running homebrew or
macports pythons? It seems this list could get pretty long!
Yes, it could, but this list:
https://www.adium.im/sparkle/?year=2014&week=22&graph=bar#osVersion
suggests that 10.9 is the majority, and that 10.8 and 10.7 are only
about 14 percent combined. I guess a better case could be made for
10.6 (still 16 percent), but I wonder how many 10.6 hold-outs are
updating their homebrew / macports numpies regularly.
Cheers,
Matthew
···
On Mon, Jun 2, 2014 at 5:14 PM, Chris Barker <chris.barker@...236...> wrote:
On Mon, Jun 2, 2014 at 11:48 AM, Matthew Brett <matthew.brett@...149...> > wrote:
> what is this going to do on OS-X 10.7 and 10.8 systems running homebrew
or
> macports pythons? It seems this list could get pretty long!
Yes, it could, but this list:
so we would have to add all those if we wanted to support them...
https://www.adium.im/sparkle/?year=2014&week=22&graph=bar#osVersion
very interesting stats! I wonder how representative those are? Makes we
think we can drop 32 bit support, too. Maybe the newest 2.7 py.org binaries
could be 64 bit only. It would simplify things a bit.
suggests that 10.9 is the majority, and that 10.8 and 10.7 are only
about 14 percent combined. I guess a better case could be made for
10.6 (still 16 percent), but I wonder how many 10.6 hold-outs are
updating their homebrew / macports numpies regularly.
not many -- it can be a really a pain to do so -- macports and homebrew
really expect you to have a recent compiler, which I think is difficult or
impossible to install on 10.6...
-Chris
···
On Mon, Jun 2, 2014 at 5:28 PM, Matthew Brett <matthew.brett@...149...> wrote:
--
Christopher Barker, Ph.D.
Oceanographer
Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Chris.Barker@...236...