Thanks Chris, From earlier in the thread the statement was made:
i.e would the same binary wheel work for both?
It should, and we will fix issues if they come up.
in reference to Windows builds against MSVC 2008.
I was asking if this "binary compatibility with python.org python" also applied to mac builds of canopy.
Anyway, I'll check the repo! I'd love it it we could get vpython install strategies that worked with all the major distributions.
thanks for the help!
-steve
On Jan 10, 2014, at 4:37 PM, Chris Barker
Not sure what "also" is respect to, but the pyton.org builds are a good common denominator:
The Apple builds have their issues: - Apple never upgrades them - You can't re-distribute them (build stuff with Py2app) .. at least without violating copyright.
While it's appealing for people to not have to install anything, if they are installing 3rd party packages they are installing stuff, son one extra install at the start is not a big deal.
So: if you are going to support one binary -- it should be the python.org one.
It is a bit of a pain to build binaries for the Python.org builds, as they are universal and support older OS versions.
Personally, I think we should address this by:
1) having a centralized project for building varios binary dependencies that are compatible with the python.org builds -- why should multiple package distributors all have to figure out how to build, e.g. freetype correctly?
I've created a repo for this, but haven't gotten far:
https://github.com/MacPython/osxinst
let me know if you are interested in contributing.
2) Maybe it's time to put out an "official" python.org build that's simpler: perhaps 10.7+ 64bit Intel only. But I'm not sure how many folks still need 32 bit.
-Chris
--
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@noaa.gov