Repository navigation
DOC: fill out dev docs - #9378
Conversation
dstansby
left a comment
There was a problem hiding this comment.
Looks good overall, just a small change needed 👍
|
|
||
| We strongly recommend developing new features in a seperate virtualenv. | ||
|
|
||
| Install all the matplotlib dependencies_, and install matplotlib into the |
There was a problem hiding this comment.
"Matplotlib" should always be uppercase in the text.
| We strongly recommend developing new features in a seperate virtualenv. | ||
|
|
||
| Install all the matplotlib dependencies_, and install matplotlib into the | ||
| virtualenv with ``pip install -e matplotlib`` (but note the changes needed to |
There was a problem hiding this comment.
OK, this isn't really my workflow. If you are developing, you need to pull down master from GitHub and pip install -e . from the GitHub directory. I also think that @anntzer just had a PR like this, or at least one that explicitly said how to pip install.
| :file:`lib/matplotlib/tests`, and customizations to the pytest testing | ||
| infrastructure are in :mod:`matplotlib.testing`. | ||
|
|
||
| .. _dependencies: http://matplotlib.org/users/installing.html#dependencies |
There was a problem hiding this comment.
This should be a Sphinx cross-references and not http://matplotlib.org/...
There was a problem hiding this comment.
how do I do that to a particular anchor in the page, i.e. dependencies on the installing page?
There was a problem hiding this comment.
You'd need to add a tag before the heading, but fortunately, there's already one there: install_requirements. You can use that name in the cross-reference instead of dependencies.
(This may be a bit difficult to find because doc/users/installing.html actually comes from INSTALL.rst in the top-level.)
There was a problem hiding this comment.
So this change is not needed any more?
|
@mattip Thanks for doing this! Do you mind if I push some commits to your branch? |
|
@tacaswell please go ahead |
| Install all the Matplotlib dependencies_, and install matplotlib into the | ||
| virtualenv with ``pip install -e matplotlib`` (but note the changes needed to | ||
| ``setup.cfg`` below) which will allow you to edit the code without | ||
| reinstalling. |
There was a problem hiding this comment.
I still think this is repeating what's in devel/contributing.rst. I think we should avoid duplicating instructions. If you haven't already installed the development version of Matplotlib then testing doesn't make a lot of sense.
There was a problem hiding this comment.
I would just write "Install the latest version of Matplotlib as documented in http://matplotlib.org/devdocs/devel/contributing.html#retrieving-and-installing-the-latest-version-of-the-code. In particular, follow the instructions to use a local FreeType build." (fix the link, of course). And then remove the mention of localfreetype below.
(We also print a warning when tests are done on a nonlocal freetype version so I think that's enough.)
|
@dstansby can you please review/approve? |
|
There's still a couple of places where 'Matplotlib' doesn't have an uppercase "M"; could you change them? Otherwise this looks good to go. |
|
I pushed a changeset, but github is not responding? |
|
weird, I can see the changeset here on my fork but it is not triggering an update to the pull request |
jklymak
left a comment
There was a problem hiding this comment.
Still missing lots of "matplotlib" -> "Matplotlib". A couple of small edits
| value. | ||
|
|
||
|
|
||
| Install matplotlib in developer mode |
| Unfortunately, different versions of FreeType produce differently | ||
| formed characters, causing these image comparisons to fail. To make | ||
| them reproducible, matplotlib can be built with a special local copy | ||
| of FreeType. This is recommended for all matplotlib developers. |
| meaning the result of a plot is compared against a known good result. | ||
| Unfortunately, different versions of FreeType produce differently | ||
| formed characters, causing these image comparisons to fail. To make | ||
| them reproducible, matplotlib can be built with a special local copy |
| To make sure the tests run locally you must build against the correct version | ||
| of freetype. To configure the build system to fetch and build it either export | ||
| the env ``MPLLOCALFREETYPE`` as:: | ||
| Building matplotlib for image comparison tests |
|
Oh, I see, you are having issues uploading! I thought your ability to search/replace "matplotlib" should have been better ;-) Sorry about that. Still suggest changing "Install" to "Installing" The rest fo the headings are "-ing"... |
|
You need to make sure your underlines extend the length of the titles.... |
|
Looks like a nice improvement, thanks a lot! |
Backport PR #9378 on branch v2.1.0-doc
PR Summary
Trivial changeset to add more complete info for new devs getting started, fixes issue #9355