summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNikita Kartashov <snailandmail@gmail.com>2018-04-21 13:16:12 +0100
committerNikita Kartashov <snailandmail@gmail.com>2018-04-21 13:22:17 +0100
commitc3c52b276892c7c1d8eeb1c9067dc02178e48863 (patch)
treeefd0731142b0badc30e38a3840a7680e3577f0f0
parent67b9a768a7e6f373bbba02df302622773559ca4b (diff)
downloadnumpy-c3c52b276892c7c1d8eeb1c9067dc02178e48863.tar.gz
DOC: fix broken links for developer documentation
Some links in developer documentation and files had extraneous '-dev' in them, removing it restore the working state of the links. See: #10939
-rw-r--r--CONTRIBUTING.md6
-rw-r--r--INSTALL.rst.txt2
-rw-r--r--doc/neps/nep-0000.rst2
-rw-r--r--numpy/doc/misc.py2
4 files changed, 6 insertions, 6 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index ead627fb7..e70585d0c 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -16,12 +16,12 @@ Thanks for your interest in contributing code to numpy!
+ If this is your first time contributing to a project on GitHub, please read
through our
-[guide to contributing to numpy](http://docs.scipy.org/doc/numpy-dev/dev/index.html)
+[guide to contributing to numpy](http://docs.scipy.org/doc/numpy/dev/index.html)
+ If you have contributed to other projects on GitHub you can go straight to our
-[development workflow](http://docs.scipy.org/doc/numpy-dev/dev/gitwash/development_workflow.html)
+[development workflow](http://docs.scipy.org/doc/numpy/dev/gitwash/development_workflow.html)
Either way, please be sure to follow our
-[convention for commit messages](http://docs.scipy.org/doc/numpy-dev/dev/gitwash/development_workflow.html#writing-the-commit-message).
+[convention for commit messages](http://docs.scipy.org/doc/numpy/dev/gitwash/development_workflow.html#writing-the-commit-message).
If you are writing new C code, please follow the style described in
``doc/C_STYLE_GUIDE``.
diff --git a/INSTALL.rst.txt b/INSTALL.rst.txt
index 6f96daabf..d8ca80d92 100644
--- a/INSTALL.rst.txt
+++ b/INSTALL.rst.txt
@@ -41,7 +41,7 @@ nose__ http://nose.readthedocs.io
If you want to build NumPy in order to work on NumPy itself, use
``runtests.py``. For more details, see
- http://docs.scipy.org/doc/numpy-dev/dev/development_environment.html
+ http://docs.scipy.org/doc/numpy/dev/development_environment.html
.. note::
diff --git a/doc/neps/nep-0000.rst b/doc/neps/nep-0000.rst
index a7d6d7115..2eed19161 100644
--- a/doc/neps/nep-0000.rst
+++ b/doc/neps/nep-0000.rst
@@ -206,7 +206,7 @@ References and Footnotes
.. _issue tracker: https://github.com/numpy/numpy/issues
.. _NumPy Steering Council:
- https://docs.scipy.org/doc/numpy-dev/dev/governance/governance.html
+ https://docs.scipy.org/doc/numpy/dev/governance/governance.html
.. _`GitHub pull request`: https://github.com/numpy/numpy/pulls
diff --git a/numpy/doc/misc.py b/numpy/doc/misc.py
index 5d6708a0d..24369871c 100644
--- a/numpy/doc/misc.py
+++ b/numpy/doc/misc.py
@@ -209,7 +209,7 @@ Only a survey of the choices. Little detail on how each works.
Interfacing to Fortran:
-----------------------
The clear choice to wrap Fortran code is
-`f2py <http://docs.scipy.org/doc/numpy-dev/f2py/>`_.
+`f2py <http://docs.scipy.org/doc/numpy/f2py/>`_.
Pyfort is an older alternative, but not supported any longer.
Fwrap is a newer project that looked promising but isn't being developed any