Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DOC: comprehensive rewrite for OSX binary install #3287

Merged
merged 15 commits into from Aug 7, 2014

Conversation

matthew-brett
Copy link
Contributor

Katy's recent edits were a big improvement, but the faq install instructions
for OSX had also got horribly out of date. The main thing that has changed is
that wheels are now the default binary installation format, and, even if we are
going to provide eggs, no-one should be using easy_install now.

@tacaswell tacaswell added this to the v1.4.0 milestone Jul 22, 2014
@tacaswell tacaswell added the doc label Jul 22, 2014
where "2.7" is your installed Python version. If you see something like
``/usr/bin/python`` instead, first try restarting Terminal.app;, if that
doesn't work then try reinstalling Python.org Python. If the check still
fails, we would like to hear about it. Please have a look at
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we (matplotlib) want to deal with issues installing python.org python? I think we should direct these issues to who ever maintains those binaries.

@tacaswell
Copy link
Member

@efiring Can you take care of merging this if you are happy with it? I am not qualified to evaluate if the mac install directions make sense.

WeatherGod and others added 2 commits August 6, 2014 21:43
DOC : fixed links, un-nested artist API docs

AGG link changed. Also fix other doc warnings
of numpy, scipy and matplotlib means that these packages are difficult to
upgrade. For that reason we strongly suggest that you install a fresh version
of Python and use that as the basis for installing libraries such as numpy and
matplotlib. Once convenient way to install matplotlib with other useful
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

typo: "Once" -> "One" or "A"

@efiring
Copy link
Member

efiring commented Aug 7, 2014

Reading through the changeset, it looks fine--a big improvement, much needed. I don't have the direct experience to verify everything, but it looks right. I think there was already some discussion of the part where the advice upon compilation error was to report the error first, then try installing or updating XCode; I would put it the other way around, but I won't argue.
Last question: wouldn't it be cleaner to rebase this on 1.4.x and merge there? Just a question; I don't want to hold things up unnecessarily.

BUG : don't assign color or marker to flier props if None
@tacaswell
Copy link
Member

re-basing would be cleaner, merging + cherry pick is faster

Katy's recent edits were a big improvement, but the faq install
instructions for OSX had also got horribly out of date.  The main thing
that has changed is that wheels are now the default binary installation
format, and, even if we are going to provide eggs, no-one should be
using easy_install now.
Also - point to 'getting help' section in troubleshooting.
Remove debugging pip for Python.org Python.

De-escalate problem heading.
Thanks to Eric F for pointing it out.
Fix typo pointed out by Eric F; add link to wiki page on system Python
and Extras/lib.
OSX version in dmg name in fact refers to Python.org Python
compatibility - but not the version of OSX it was 'built for'.
@matthew-brett
Copy link
Contributor Author

I just did a rebase against current v1.4.x - is that what you meant?

@matthew-brett
Copy link
Contributor Author

Eric - tend to agree about xcode, help order - I pushed a change - OK?

@efiring efiring merged commit 0fe3f9e into matplotlib:master Aug 7, 2014
@efiring
Copy link
Member

efiring commented Aug 7, 2014

I pushed the changes directly to v1.4.x and merged v1.4.x into master.

@efiring
Copy link
Member

efiring commented Aug 7, 2014

@tacaswell, I hope the way I did that was right, or close enough. I was trying to avoid having to make a new PR against v1.4.x by achieving the same result manually.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants