DOC: Fix invalid Sphinx cross-references in older whatsnew RST files

doc/source/whatsnew/v0.13.0.rst

@@ -732,7 +732,7 @@ Enhancements
 
 - ``DatetimeIndex`` is now in the API documentation, see :ref:`the docs<api.datetimeindex>`
 
-- :meth:`~pandas.io.json.json_normalize` is a new method to allow you to create a flat table
+- :func:`pandas.json_normalize` is a new method to allow you to create a flat table
   from semi-structured JSON data. See :ref:`the docs<io.json_normalize>` (:issue:`1067`)
 
 - Added PySide support for the qtpandas DataFrameModel and DataFrameWidget.

doc/source/whatsnew/v0.13.1.rst

@@ -15,7 +15,7 @@ Highlights include:
 
 - Added ``infer_datetime_format`` keyword to ``read_csv/to_datetime`` to allow speedups for homogeneously formatted datetimes.
 - Will intelligently limit display precision for datetime/timedelta formats.
-- Enhanced Panel :meth:`~pandas.Panel.apply` method.
+- Enhanced Panel ``Panel.apply`` method.
 - Suggested tutorials in new :ref:`Tutorials<tutorials>` section.
 - Our pandas ecosystem is growing, We now feature related projects in a new `ecosystem page <https://pandas.pydata.org/community/ecosystem.html>`_ section.
 - Much work has been taking place on improving the docs, and a new :ref:`Contributing<contributing>` section has been added.
@@ -224,7 +224,7 @@ Enhancements
 
       pd.MultiIndex.from_product([shades, colors], names=["shade", "color"])
 
-- Panel :meth:`~pandas.Panel.apply` will work on non-ufuncs. See :ref:`the docs<basics.apply>`.
+- Panel ``Panel.apply`` will work on non-ufuncs. See :ref:`the docs<basics.apply>`.
 
   .. code-block:: ipython
 
@@ -322,7 +322,7 @@ Enhancements
 
       [5 rows x 4 columns]
 
-- Panel :meth:`~pandas.Panel.apply` operating on cross-sectional slabs. (:issue:`1148`)
+- Panel ``Panel.apply`` operating on cross-sectional slabs. (:issue:`1148`)
 
   .. code-block:: ipython
 

doc/source/whatsnew/v0.14.0.rst

@@ -313,7 +313,7 @@ Text parsing API changes
   options in :func:`read_csv`/:func:`read_table` (:issue:`6607`)
 - Raise ``ValueError`` when fallback to python parser causes options to be
   ignored (:issue:`6607`)
-- Produce :class:`~pandas.io.parsers.ParserWarning` on fallback to python
+- Produce :class:`pandas.errors.ParserWarning` on fallback to python
   parser when no options are ignored (:issue:`6607`)
 - Translate ``sep='\s+'`` to ``delim_whitespace=True`` in
   :func:`read_csv`/:func:`read_table` if no other C-unsupported options
@@ -439,7 +439,7 @@ wrapper around the other two and will delegate to specific function depending on
 the provided input (database table name or sql query).
 
 In practice, you have to provide a SQLAlchemy ``engine`` to the sql functions.
-To connect with SQLAlchemy you use the :func:`create_engine` function to create an engine
+To connect with SQLAlchemy you use the ``create_engine`` function to create an engine
 object from database URI. You only need to create the engine once per database you are
 connecting to. For an in-memory sqlite database:
 
@@ -626,11 +626,11 @@ Plotting
 
   Because of the default ``align`` value changes, coordinates of bar plots are now located on integer values (0.0, 1.0, 2.0 ...). This is intended to make bar plot be located on the same coordinates as line plot. However, bar plot may differs unexpectedly when you manually adjust the bar location or drawing area, such as using ``set_xlim``, ``set_ylim``, etc. In this cases, please modify your script to meet with new coordinates.
 
-- The :func:`parallel_coordinates` function now takes argument ``color``
+- The ``parallel_coordinates`` function now takes argument ``color``
   instead of ``colors``. A ``FutureWarning`` is raised to alert that
   the old ``colors`` argument will not be supported in a future release. (:issue:`6956`)
 
-- The :func:`parallel_coordinates` and :func:`andrews_curves` functions now take
+- The ``parallel_coordinates`` and ``andrews_curves`` functions now take
   positional argument ``frame`` instead of ``data``. A ``FutureWarning`` is
   raised if the old ``data`` argument is used by name. (:issue:`6956`)
 
@@ -647,22 +647,22 @@ Prior version deprecations/changes
 
 There are prior version deprecations that are taking effect as of 0.14.0.
 
-- Remove :class:`DateRange` in favor of :class:`DatetimeIndex` (:issue:`6816`)
+- Remove ``DateRange`` in favor of :class:`DatetimeIndex` (:issue:`6816`)
 - Remove ``column`` keyword from ``DataFrame.sort`` (:issue:`4370`)
 - Remove ``precision`` keyword from :func:`set_eng_float_format` (:issue:`395`)
 - Remove ``force_unicode`` keyword from :meth:`DataFrame.to_string`,
   :meth:`DataFrame.to_latex`, and :meth:`DataFrame.to_html`; these function
   encode in unicode by default (:issue:`2224`, :issue:`2225`)
 - Remove ``nanRep`` keyword from :meth:`DataFrame.to_csv` and
   :meth:`DataFrame.to_string` (:issue:`275`)
-- Remove ``unique`` keyword from :meth:`HDFStore.select_column` (:issue:`3256`)
-- Remove ``inferTimeRule`` keyword from :func:`Timestamp.offset` (:issue:`391`)
-- Remove ``name`` keyword from :func:`get_data_yahoo` and
-  :func:`get_data_google` ( `commit b921d1a <https://github.com/pandas-dev/pandas/commit/b921d1a2>`__ )
+- Remove ``unique`` keyword from ``HDFStore.select_column`` (:issue:`3256`)
+- Remove ``inferTimeRule`` keyword from ``Timestamp.offset`` (:issue:`391`)
+- Remove ``name`` keyword from ``get_data_yahoo`` and
+  ``get_data_google`` ( `commit b921d1a <https://github.com/pandas-dev/pandas/commit/b921d1a2>`__ )
 - Remove ``offset`` keyword from :class:`DatetimeIndex` constructor
   ( `commit 3136390 <https://github.com/pandas-dev/pandas/commit/3136390>`__ )
 - Remove ``time_rule`` from several rolling-moment statistical functions, such
-  as :func:`rolling_sum` (:issue:`1042`)
+  as ``rolling_sum`` (:issue:`1042`)
 - Removed neg ``-`` boolean operations on numpy arrays in favor of inv ``~``, as this is going to
   be deprecated in numpy 1.9 (:issue:`6960`)
 
@@ -715,21 +715,21 @@ Deprecations
 
 - Numpy 1.9 compat w.r.t. deprecation warnings (:issue:`6960`)
 
-- :meth:`Panel.shift` now has a function signature that matches :meth:`DataFrame.shift`.
+- ``Panel.shift`` now has a function signature that matches :meth:`DataFrame.shift`.
   The old positional argument ``lags`` has been changed to a keyword argument
   ``periods`` with a default value of 1. A ``FutureWarning`` is raised if the
   old argument ``lags`` is used by name. (:issue:`6910`)
 - The ``order`` keyword argument of :func:`factorize` will be removed. (:issue:`6926`).
 
-- Remove the ``copy`` keyword from :meth:`DataFrame.xs`, :meth:`Panel.major_xs`, :meth:`Panel.minor_xs`. A view will be
+- Remove the ``copy`` keyword from :meth:`DataFrame.xs`, ``Panel.major_xs``, ``Panel.minor_xs``. A view will be
   returned if possible, otherwise a copy will be made. Previously the user could think that ``copy=False`` would
   ALWAYS return a view. (:issue:`6894`)
 
-- The :func:`parallel_coordinates` function now takes argument ``color``
+- The ``parallel_coordinates`` function now takes argument ``color``
   instead of ``colors``. A ``FutureWarning`` is raised to alert that
   the old ``colors`` argument will not be supported in a future release. (:issue:`6956`)
 
-- The :func:`parallel_coordinates` and :func:`andrews_curves` functions now take
+- The ``parallel_coordinates`` and ``andrews_curves`` functions now take
   positional argument ``frame`` instead of ``data``. A ``FutureWarning`` is
   raised if the old ``data`` argument is used by name. (:issue:`6956`)
 
@@ -742,7 +742,7 @@ Deprecations
   Use the ``percentiles`` keyword instead, which takes a list of percentiles to display. The
   default output is unchanged.
 
-- The default return type of :func:`boxplot` will change from a dict to a matplotlib Axes
+- The default return type of :func:`pandas.plotting.boxplot` will change from a dict to a matplotlib Axes
   in a future release. You can use the future behavior now by passing ``return_type='axes'``
   to boxplot.
 
@@ -831,8 +831,8 @@ Enhancements
 - ``Float64Index`` is now backed by a ``float64`` dtype ndarray instead of an
   ``object`` dtype array (:issue:`6471`).
 - Implemented ``Panel.pct_change`` (:issue:`6904`)
-- Added ``how`` option to rolling-moment functions to dictate how to handle resampling; :func:`rolling_max` defaults to max,
-  :func:`rolling_min` defaults to min, and all others default to mean (:issue:`6297`)
+- Added ``how`` option to rolling-moment functions to dictate how to handle resampling; ``rolling_max`` defaults to max,
+  ``rolling_min`` defaults to min, and all others default to mean (:issue:`6297`)
 - ``CustomBusinessMonthBegin`` and ``CustomBusinessMonthEnd`` are now available (:issue:`6866`)
 - :meth:`Series.quantile` and :meth:`DataFrame.quantile` now accept an array of
   quantiles.

doc/source/whatsnew/v0.15.0.rst

@@ -383,7 +383,7 @@ Timezone handling improvements
 Rolling/expanding moments improvements
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-- :func:`rolling_min`, :func:`rolling_max`, :func:`rolling_cov`, and :func:`rolling_corr`
+- ``rolling_min``, ``rolling_max``, ``rolling_cov``, and ``rolling_corr``
   now return objects with all ``NaN`` when ``len(arg) < min_periods <= window`` rather
   than raising. (This makes all rolling functions consistent in this behavior). (:issue:`7766`)
 
@@ -410,14 +410,14 @@ Rolling/expanding moments improvements
      3   NaN
      dtype: float64
 
-- :func:`rolling_max`, :func:`rolling_min`, :func:`rolling_sum`, :func:`rolling_mean`, :func:`rolling_median`,
-  :func:`rolling_std`, :func:`rolling_var`, :func:`rolling_skew`, :func:`rolling_kurt`, :func:`rolling_quantile`,
-  :func:`rolling_cov`, :func:`rolling_corr`, :func:`rolling_corr_pairwise`,
-  :func:`rolling_window`, and :func:`rolling_apply` with ``center=True`` previously would return a result of the same
+- ``rolling_max``, ``rolling_min``, ``rolling_sum``, ``rolling_mean``, ``rolling_median``,
+  ``rolling_std``, ``rolling_var``, ``rolling_skew``, ``rolling_kurt``, ``rolling_quantile``,
+  ``rolling_cov``, ``rolling_corr``, ``rolling_corr_pairwise``,
+  ``rolling_window``, and ``rolling_apply`` with ``center=True`` previously would return a result of the same
   structure as the input ``arg`` with ``NaN`` in the final ``(window-1)/2`` entries.
 
   Now the final ``(window-1)/2`` entries of the result are calculated as if the input ``arg`` were followed
-  by ``(window-1)/2`` ``NaN`` values (or with shrinking windows, in the case of :func:`rolling_apply`).
+  by ``(window-1)/2`` ``NaN`` values (or with shrinking windows, in the case of ``rolling_apply``).
   (:issue:`7925`, :issue:`8269`)
 
   Prior behavior (note final value is ``NaN``):
@@ -445,7 +445,7 @@ Rolling/expanding moments improvements
      3    5
      dtype: float64
 
-- :func:`rolling_window` now normalizes the weights properly in rolling mean mode (``mean=True``) so that
+- ``rolling_window`` now normalizes the weights properly in rolling mean mode (``mean=True``) so that
   the calculated weighted means (e.g. 'triang', 'gaussian') are distributed about the same means as those
   calculated without weighting (i.e. 'boxcar'). See :ref:`the note on normalization <window.weighted>` for further details. (:issue:`7618`)
 
@@ -479,18 +479,18 @@ Rolling/expanding moments improvements
      4       NaN
      dtype: float64
 
-- Removed ``center`` argument from all :func:`expanding_ <expanding_apply>` functions (see :ref:`list <api.functions_expanding>`),
+- Removed ``center`` argument from all ``expanding_*`` functions (see :ref:`list <api.functions_expanding>`),
   as the results produced when ``center=True`` did not make much sense. (:issue:`7925`)
 
-- Added optional ``ddof`` argument to :func:`expanding_cov` and :func:`rolling_cov`.
+- Added optional ``ddof`` argument to ``expanding_cov`` and ``rolling_cov``.
   The default value of ``1`` is backwards-compatible. (:issue:`8279`)
 
-- Documented the ``ddof`` argument to :func:`expanding_var`, :func:`expanding_std`,
-  :func:`rolling_var`, and :func:`rolling_std`. These functions' support of a
+- Documented the ``ddof`` argument to ``expanding_var``, ``expanding_std``,
+  ``rolling_var``, and ``rolling_std``. These functions' support of a
   ``ddof`` argument (with a default value of ``1``) was previously undocumented. (:issue:`8064`)
 
-- :func:`ewma`, :func:`ewmstd`, :func:`ewmvol`, :func:`ewmvar`, :func:`ewmcov`, and :func:`ewmcorr`
-  now interpret ``min_periods`` in the same manner that the :func:`rolling_*` and :func:`expanding_*` functions do:
+- ``ewma``, ``ewmstd``, ``ewmvol``, ``ewmvar``, ``ewmcov``, and ``ewmcorr``
+  now interpret ``min_periods`` in the same manner that the ``rolling_*`` and ``expanding_*`` functions do:
   a given result entry will be ``NaN`` if the (expanding, in this case) window does not contain
   at least ``min_periods`` values. The previous behavior was to set to ``NaN`` the ``min_periods`` entries
   starting with the first non- ``NaN`` value. (:issue:`7977`)
@@ -528,13 +528,13 @@ Rolling/expanding moments improvements
      5    2.383784
      dtype: float64
 
-- :func:`ewmstd`, :func:`ewmvol`, :func:`ewmvar`, :func:`ewmcov`, and :func:`ewmcorr`
-  now have an optional ``adjust`` argument, just like :func:`ewma` does,
+- ``ewmstd``, ``ewmvol``, ``ewmvar``, ``ewmcov``, and ``ewmcorr``
+  now have an optional ``adjust`` argument, just like ``ewma`` does,
   affecting how the weights are calculated.
   The default value of ``adjust`` is ``True``, which is backwards-compatible.
   See :ref:`Exponentially weighted moment functions <window.exponentially_weighted>` for details. (:issue:`7911`)
 
-- :func:`ewma`, :func:`ewmstd`, :func:`ewmvol`, :func:`ewmvar`, :func:`ewmcov`, and :func:`ewmcorr`
+- ``ewma``, ``ewmstd``, ``ewmvol``, ``ewmvar``, ``ewmcov``, and ``ewmcorr``
   now have an optional ``ignore_na`` argument.
   When ``ignore_na=False`` (the default), missing values are taken into account in the weights calculation.
   When ``ignore_na=True`` (which reproduces the pre-0.15.0 behavior), missing values are ignored in the weights calculation.
@@ -567,21 +567,21 @@ Rolling/expanding moments improvements
 
   .. warning::
 
-     By default (``ignore_na=False``) the :func:`ewm*` functions' weights calculation
+     By default (``ignore_na=False``) the ``ewm*`` functions' weights calculation
      in the presence of missing values is different than in pre-0.15.0 versions.
      To reproduce the pre-0.15.0 calculation of weights in the presence of missing values
      one must specify explicitly ``ignore_na=True``.
 
-- Bug in :func:`expanding_cov`, :func:`expanding_corr`, :func:`rolling_cov`, :func:`rolling_cor`, :func:`ewmcov`, and :func:`ewmcorr`
+- Bug in ``expanding_cov``, ``expanding_corr``, ``rolling_cov``, ``rolling_cor``, ``ewmcov``, and ``ewmcorr``
   returning results with columns sorted by name and producing an error for non-unique columns;
   now handles non-unique columns and returns columns in original order
   (except for the case of two DataFrames with ``pairwise=False``, where behavior is unchanged) (:issue:`7542`)
-- Bug in :func:`rolling_count` and :func:`expanding_*` functions unnecessarily producing error message for zero-length data (:issue:`8056`)
-- Bug in :func:`rolling_apply` and :func:`expanding_apply` interpreting ``min_periods=0`` as ``min_periods=1`` (:issue:`8080`)
-- Bug in :func:`expanding_std` and :func:`expanding_var` for a single value producing a confusing error message (:issue:`7900`)
-- Bug in :func:`rolling_std` and :func:`rolling_var` for a single value producing ``0`` rather than ``NaN`` (:issue:`7900`)
+- Bug in ``rolling_count`` and ``expanding_*`` functions unnecessarily producing error message for zero-length data (:issue:`8056`)
+- Bug in ``rolling_apply`` and ``expanding_apply`` interpreting ``min_periods=0`` as ``min_periods=1`` (:issue:`8080`)
+- Bug in ``expanding_std`` and ``expanding_var`` for a single value producing a confusing error message (:issue:`7900`)
+- Bug in ``rolling_std`` and ``rolling_var`` for a single value producing ``0`` rather than ``NaN`` (:issue:`7900`)
 
-- Bug in :func:`ewmstd`, :func:`ewmvol`, :func:`ewmvar`, and :func:`ewmcov`
+- Bug in ``ewmstd``, ``ewmvol``, ``ewmvar``, and ``ewmcov``
   calculation of de-biasing factors when ``bias=False`` (the default).
   Previously an incorrect constant factor was used, based on ``adjust=True``, ``ignore_na=True``,
   and an infinite number of observations.
@@ -1022,7 +1022,7 @@ Other:
 
 - Added ``searchsorted`` method to ``Series`` objects (:issue:`7447`)
 
-- :func:`describe` on mixed-types DataFrames is more flexible. Type-based column filtering is now possible via the ``include``/``exclude`` arguments.
+- ``describe`` on mixed-types DataFrames is more flexible. Type-based column filtering is now possible via the ``include``/``exclude`` arguments.
   See the :ref:`docs <basics.describe>` (:issue:`8164`).
 
   .. code-block:: python
@@ -1143,7 +1143,7 @@ Other:
   numbers are passed (:issue:`7660`). See
   :ref:`Reshaping by stacking and unstacking <reshaping.stack_multiple>`.
 
-- :func:`set_names`, :func:`set_labels`, and :func:`set_levels` methods now take an optional ``level`` keyword argument to all modification of specific level(s) of a MultiIndex. Additionally :func:`set_names` now accepts a scalar string value when operating on an ``Index`` or on a specific level of a ``MultiIndex`` (:issue:`7792`)
+- ``set_names``, ``set_labels``, and ``set_levels`` methods now take an optional ``level`` keyword argument to all modification of specific level(s) of a MultiIndex. Additionally ``set_names`` now accepts a scalar string value when operating on an ``Index`` or on a specific level of a ``MultiIndex`` (:issue:`7792`)
 
   .. ipython:: python
 

doc/source/whatsnew/v0.15.1.rst

@@ -263,7 +263,7 @@ Enhancements
 
 - Raise errors in certain aggregation cases where an argument such as ``numeric_only`` is not handled (:issue:`8592`).
 
-- Added support for 3-character ISO and non-standard country codes in :func:`io.wb.download` (:issue:`8482`)
+- Added support for 3-character ISO and non-standard country codes in ``io.wb.download`` (:issue:`8482`)
 
 - World Bank data requests now will warn/raise based
   on an ``errors`` argument, as well as a list of hard-coded country codes and

doc/source/whatsnew/v0.16.0.rst

@@ -89,7 +89,7 @@ See the :ref:`documentation <dsintro.chained_assignment>` for more. (:issue:`922
 Interaction with scipy.sparse
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-Added :meth:`SparseSeries.to_coo` and :meth:`SparseSeries.from_coo` methods (:issue:`8048`) for converting to and from ``scipy.sparse.coo_matrix`` instances (see :ref:`here <sparse.scipysparse>`). For example, given a SparseSeries with MultiIndex we can convert to a ``scipy.sparse.coo_matrix`` by specifying the row and column labels as index levels:
+Added ``SparseSeries.to_coo`` and ``SparseSeries.from_coo`` methods (:issue:`8048`) for converting to and from ``scipy.sparse.coo_matrix`` instances (see :ref:`here <sparse.scipysparse>`). For example, given a SparseSeries with MultiIndex we can convert to a ``scipy.sparse.coo_matrix`` by specifying the row and column labels as index levels:
 
 .. code-block:: python