Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit 480bf6c

Browse filesBrowse files
authored
Merge pull request #7229 from NelleV/eyurstev_DOC_development
DOC: instructions on installing matplotlib for dev
2 parents de376dd + 6c2748b commit 480bf6c
Copy full SHA for 480bf6c

File tree

Expand file treeCollapse file tree

5 files changed

+48
-20
lines changed
Filter options
Expand file treeCollapse file tree

5 files changed

+48
-20
lines changed

‎doc/devel/gitwash/git_development.rst

Copy file name to clipboardExpand all lines: doc/devel/gitwash/git_development.rst
-16Lines changed: 0 additions & 16 deletions
This file was deleted.

‎doc/devel/gitwash/index.rst

Copy file name to clipboardExpand all lines: doc/devel/gitwash/index.rst
+1-1Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,6 @@ Contents:
1111
git_intro
1212
git_install
1313
following_latest
14-
git_development
14+
setting_up_for_development
1515
git_resources
1616
patching
+27Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
.. _matplotlib-for-dev:
2+
3+
=================================================
4+
Installing matplotlib from source for development
5+
=================================================
6+
7+
After obtaining a local copy of the matpotlib source code (:ref:`set-up-fork`),
8+
navigate to the matplotlib directory and run the following in the shell:
9+
10+
::
11+
12+
python setup.py develop
13+
14+
or::
15+
16+
pip install -v -e .
17+
18+
This installs matplotlib for development (i.e., builds everything and places
19+
the symbolic links back to the source code). This command has to be called
20+
everytime a `c` file is changed. Note that changing branches may change the
21+
`c`-code.
22+
23+
When working on bleeding edge packages, setting up a
24+
`virtual environment
25+
<http://docs.python-guide.org/en/latest/dev/virtualenvs/>`_ or a `conda
26+
environment <http://conda.pydata.org/docs/using/envs.html>`_ is recommended.
27+
+17Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
.. _setting_up_for_development:
2+
3+
==========================
4+
Setting up for development
5+
==========================
6+
7+
Contents:
8+
9+
.. toctree::
10+
:maxdepth: 2
11+
12+
forking_hell
13+
set_up_fork
14+
matplotlib_for_dev
15+
configure_git
16+
development_workflow
17+
dot2_dot3

‎doc/devel/release_guide.rst

Copy file name to clipboardExpand all lines: doc/devel/release_guide.rst
+3-3Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
.. _release-guide:
22

3-
**************************
4-
Doing a matplotlib release
5-
**************************
3+
*************
4+
Release Guide
5+
*************
66

77
A guide for developers who are doing a matplotlib release.
88

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.