Scheduled weekly dependency update for week 27

[pyup-bot]

Updates

Here's a list of all the updates bundled in this pull request. I've added some links to make it easier for you to find all the information you need.

numpy	1.12.1	»	1.13.0	PyPI | Changelog | Homepage
pandas	0.20.1	»	0.20.2	PyPI | Changelog | Homepage
dedupe	1.6.13	»	1.6.15	PyPI | Changelog | Repo
Sphinx	1.6.1	»	1.6.3	PyPI | Changelog | Homepage
cryptography	1.8.1	»	1.9	PyPI | Changelog | Repo
pytest	3.0.7	»	3.1.2	PyPI | Changelog | Repo | Homepage
Faker	0.7.12	»	0.7.17	PyPI | Changelog | Repo
tqdm	4.11.2	»	4.14.0	PyPI | Changelog | Repo

Changelogs

numpy 1.12.1 -> 1.13.0

1.13.0

==========================

This release supports Python 2.7 and 3.4 - 3.6.

Highlights

• Operations like a + b + c will reuse temporaries on some platforms,
  resulting in less memory use and faster execution.
• Inplace operations check if inputs overlap outputs and create temporaries
  to avoid problems.
• New __array_ufunc__ attribute provides improved ability for classes to
  override default ufunc behavior.
• New np.block function for creating blocked arrays.

New functions

• New np.positive ufunc.
• New np.divmod ufunc provides more efficient divmod.
• New np.isnat ufunc tests for NaT special values.
• New np.heaviside ufunc computes the Heaviside function.
• New np.isin function, improves on in1d.
• New np.block function for creating blocked arrays.
• New PyArray_MapIterArrayCopyIfOverlap added to NumPy C-API.

See below for details.

Deprecations

• Calling np.fix, np.isposinf, and np.isneginf with f(x, y=out)
  is deprecated - the argument should be passed as f(x, out=out), which
  matches other ufunc-like interfaces.
• Use of the C-API NPY_CHAR type number deprecated since version 1.7 will
  now raise deprecation warnings at runtime. Extensions built with older f2py
  versions need to be recompiled to remove the warning.
• np.ma.argsort, np.ma.minimum.reduce, and np.ma.maximum.reduce
  should be called with an explicit axis argument when applied to arrays with
  more than 2 dimensions, as the default value of this argument (None) is
  inconsistent with the rest of numpy (-1, 0, and 0, respectively).
• np.ma.MaskedArray.mini is deprecated, as it almost duplicates the
  functionality of np.MaskedArray.min. Exactly equivalent behaviour
  can be obtained with np.ma.minimum.reduce.
• The single-argument form of np.ma.minimum and np.ma.maximum is
  deprecated. np.maximum. np.ma.minimum(x) should now be spelt
  np.ma.minimum.reduce(x), which is consistent with how this would be done
  with np.minimum.
• Calling ndarray.conjugate on non-numeric dtypes is deprecated (it
  should match the behavior of np.conjugate, which throws an error).
• Calling expand_dims when the axis keyword does not satisfy
  -a.ndim - 1 <= axis <= a.ndim, where a is the array being reshaped,
  is deprecated.

Future Changes

• Assignment between structured arrays with different field names will change
  in NumPy 1.14. Previously, fields in the dst would be set to the value of the
  identically-named field in the src. In numpy 1.14 fields will instead be
  assigned 'by position': The n-th field of the dst will be set to the n-th
  field of the src array. Note that the FutureWarning raised in NumPy 1.12
  incorrectly reported this change as scheduled for NumPy 1.13 rather than
  NumPy 1.14.

Build System Changes

• numpy.distutils now automatically determines C-file dependencies with
  GCC compatible compilers.

Compatibility notes

Error type changes

• numpy.hstack() now throws ValueError instead of IndexError when
  input is empty.
• Functions taking an axis argument, when that argument is out of range, now
  throw np.AxisError instead of a mixture of IndexError and
  ValueError. For backwards compatibility, AxisError subclasses both of
  these.

Tuple object dtypes

Support has been removed for certain obscure dtypes that were unintentionally
allowed, of the form (old_dtype, new_dtype), where either of the dtypes
is or contains the object dtype. As an exception, dtypes of the form
(object, [('name', object)]) are still supported due to evidence of
existing use.

DeprecationWarning to error

See Changes section for more detail.

• partition, TypeError when non-integer partition index is used.
• NpyIter_AdvancedNew, ValueError when oa_ndim == 0 and op_axes is NULL
• negative(bool_), TypeError when negative applied to booleans.
• subtract(bool_, bool_), TypeError when subtracting boolean from boolean.
• np.equal, np.not_equal, object identity doesn't override failed comparison.
• np.equal, np.not_equal, object identity doesn't override non-boolean comparison.
• Deprecated boolean indexing behavior dropped. See Changes below for details.
• Deprecated np.alterdot() and np.restoredot() removed.

FutureWarning to changed behavior

See Changes section for more detail.

• numpy.average preserves subclasses
• array == None and array != None do element-wise comparison.
• np.equal, np.not_equal, object identity doesn't override comparison result.

dtypes are now always true

Previously bool(dtype) would fall back to the default python
implementation, which checked if len(dtype) > 0. Since dtype objects
implement __len__ as the number of record fields, bool of scalar dtypes
would evaluate to False, which was unintuitive. Now bool(dtype) == True
for all dtypes.

__getslice__ and __setslice__ are no longer needed in ndarray subclasses

When subclassing np.ndarray in Python 2.7, it is no longer necessary to
implement __*slice__ on the derived class, as __*item__ will intercept
these calls correctly.

Any code that did implement these will work exactly as before. Code that
invokesndarray.__getslice__ (e.g. through super(...).__getslice__) will
now issue a DeprecationWarning - .__getitem__(slice(start, end)) should be
used instead.

Indexing MaskedArrays/Constants with ... (ellipsis) now returns MaskedArray

This behavior mirrors that of np.ndarray, and accounts for nested arrays in
MaskedArrays of object dtype, and ellipsis combined with other forms of
indexing.

C API changes

GUfuncs on empty arrays and NpyIter axis removal

It is now allowed to remove a zero-sized axis from NpyIter. Which may mean
that code removing axes from NpyIter has to add an additional check when
accessing the removed dimensions later on.

The largest followup change is that gufuncs are now allowed to have zero-sized
inner dimensions. This means that a gufunc now has to anticipate an empty inner
dimension, while this was never possible and an error raised instead.

For most gufuncs no change should be necessary. However, it is now possible
for gufuncs with a signature such as (..., N, M) -> (..., M) to return
a valid result if N=0 without further wrapping code.

PyArray_MapIterArrayCopyIfOverlap added to NumPy C-API

Similar to PyArray_MapIterArray but with an additional copy_if_overlap
argument. If copy_if_overlap != 0, checks if input has memory overlap with
any of the other arrays and make copies as appropriate to avoid problems if the
input is modified during the iteration. See the documentation for more complete
documentation.

New Features

__array_ufunc__ added

This is the renamed and redesigned __numpy_ufunc__. Any class, ndarray
subclass or not, can define this method or set it to None in order to
override the behavior of NumPy's ufuncs. This works quite similarly to Python's
__mul__ and other binary operation routines. See the documentation for a
more detailed description of the implementation and behavior of this new
option. The API is provisional, we do not yet guarantee backward compatibility
as modifications may be made pending feedback. See the NEP_ and
documentation_ for more details.

.. _NEP: https://github.com/numpy/numpy/blob/master/doc/neps/ufunc-overrides.rst
.. _documentation: https://github.com/charris/numpy/blob/master/doc/source/reference/arrays.classes.rst

New positive ufunc

This ufunc corresponds to unary +, but unlike + on an ndarray it will raise
an error if array values do not support numeric operations.

New divmod ufunc

This ufunc corresponds to the Python builtin divmod, and is used to implement
divmod when called on numpy arrays. np.divmod(x, y) calculates a result
equivalent to (np.floor_divide(x, y), np.remainder(x, y)) but is
approximately twice as fast as calling the functions separately.

np.isnat ufunc tests for NaT special datetime and timedelta values

The new ufunc np.isnat finds the positions of special NaT values
within datetime and timedelta arrays. This is analogous to np.isnan.

np.heaviside ufunc computes the Heaviside function

The new function np.heaviside(x, h0) (a ufunc) computes the Heaviside
function:
.. code::
{ 0 if x < 0,
heaviside(x, h0) = { h0 if x == 0,
{ 1 if x > 0.

np.block function for creating blocked arrays

Add a new block function to the current stacking functions vstack,
hstack, and stack. This allows concatenation across multiple axes
simultaneously, with a similar syntax to array creation, but where elements
can themselves be arrays. For instance::

>>> A = np.eye(2) * 2
>>> B = np.eye(3) * 3
>>> np.block([
... [A, np.zeros((2, 3))],
... [np.ones((3, 2)), B ]
... ])
array([[ 2., 0., 0., 0., 0.],
[ 0., 2., 0., 0., 0.],
[ 1., 1., 3., 0., 0.],
[ 1., 1., 0., 3., 0.],
[ 1., 1., 0., 0., 3.]])

While primarily useful for block matrices, this works for arbitrary dimensions
of arrays.

It is similar to Matlab's square bracket notation for creating block matrices.

isin function, improving on in1d

The new function isin tests whether each element of an N-dimensonal
array is present anywhere within a second array. It is an enhancement
of in1d that preserves the shape of the first array.

Temporary elision

On platforms providing the backtrace function NumPy will try to avoid
creating temporaries in expression involving basic numeric types.
For example d = a + b + c is transformed to d = a + b; d += c which can
improve performance for large arrays as less memory bandwidth is required to
perform the operation.

axes argument for unique

In an N-dimensional array, the user can now choose the axis along which to look
for duplicate N-1-dimensional elements using numpy.unique. The original
behaviour is recovered if axis=None (default).

np.gradient now supports unevenly spaced data

Users can now specify a not-constant spacing for data.
In particular np.gradient can now take:

1. A single scalar to specify a sample distance for all dimensions.
2. N scalars to specify a constant sample distance for each dimension.
   i.e. dx, dy, dz, ...
3. N arrays to specify the coordinates of the values along each dimension of F.
   The length of the array must match the size of the corresponding dimension
4. Any combination of N scalars/arrays with the meaning of 2. and 3.

This means that, e.g., it is now possible to do the following::

>>> f = np.array([[1, 2, 6], [3, 4, 5]], dtype=np.float)
>>> dx = 2.
>>> y = [1., 1.5, 3.5]
>>> np.gradient(f, dx, y)
[array([[ 1. , 1. , -0.5], [ 1. , 1. , -0.5]]),
array([[ 2. , 2. , 2. ], [ 2. , 1.7, 0.5]])]

Support for returning arrays of arbitrary dimensions in apply_along_axis

Previously, only scalars or 1D arrays could be returned by the function passed
to apply_along_axis. Now, it can return an array of any dimensionality
(including 0D), and the shape of this array replaces the axis of the array
being iterated over.

.ndim property added to dtype to complement .shape

For consistency with ndarray and broadcast, d.ndim is a shorthand
for len(d.shape).

Support for tracemalloc in Python 3.6

NumPy now supports memory tracing with tracemalloc_ module of Python 3.6 or
newer. Memory allocations from NumPy are placed into the domain defined by
numpy.lib.tracemalloc_domain.
Note that NumPy allocation will not show up in tracemalloc_ of earlier Python
versions.

.. _tracemalloc: https://docs.python.org/3/library/tracemalloc.html

NumPy may be built with relaxed stride checking debugging

Setting NPY_RELAXED_STRIDES_DEBUG=1 in the environment when relaxed stride
checking is enabled will cause NumPy to be compiled with the affected strides
set to the maximum value of npy_intp in order to help detect invalid usage of
the strides in downstream projects. When enabled, invalid usage often results
in an error being raised, but the exact type of error depends on the details of
the code. TypeError and OverflowError have been observed in the wild.

It was previously the case that this option was disabled for releases and
enabled in master and changing between the two required editing the code. It is
now disabled by default but can be enabled for test builds.

Improvements

Ufunc behavior for overlapping inputs

Operations where ufunc input and output operands have memory overlap
produced undefined results in previous NumPy versions, due to data
dependency issues. In NumPy 1.13.0, results from such operations are
now defined to be the same as for equivalent operations where there is
no memory overlap.

Operations affected now make temporary copies, as needed to eliminate
data dependency. As detecting these cases is computationally
expensive, a heuristic is used, which may in rare cases result to
needless temporary copies. For operations where the data dependency
is simple enough for the heuristic to analyze, temporary copies will
not be made even if the arrays overlap, if it can be deduced copies
are not necessary. As an example,np.add(a, b, out=a) will not
involve copies.

To illustrate a previously undefined operation::

>>> x = np.arange(16).astype(float)
>>> np.add(x[1:], x[:-1], out=x[1:])

In NumPy 1.13.0 the last line is guaranteed to be equivalent to::

>>> np.add(x[1:].copy(), x[:-1].copy(), out=x[1:])

A similar operation with simple non-problematic data dependence is::

>>> x = np.arange(16).astype(float)
>>> np.add(x[1:], x[:-1], out=x[:-1])

It will continue to produce the same results as in previous NumPy
versions, and will not involve unnecessary temporary copies.

The change applies also to in-place binary operations, for example::

>>> x = np.random.rand(500, 500)
>>> x += x.T

This statement is now guaranteed to be equivalent to x[...] = x + x.T,
whereas in previous NumPy versions the results were undefined.

Partial support for 64-bit f2py extensions with MinGW

Extensions that incorporate Fortran libraries can now be built using the free
MinGW_ toolset, also under Python 3.5. This works best for extensions that only
do calculations and uses the runtime modestly (reading and writing from files,
for instance). Note that this does not remove the need for Mingwpy; if you make
extensive use of the runtime, you will most likely run into issues_. Instead,
it should be regarded as a band-aid until Mingwpy is fully functional.

Extensions can also be compiled using the MinGW toolset using the runtime
library from the (moveable) WinPython 3.4 distribution, which can be useful for
programs with a PySide1/Qt4 front-end.

.. _MinGW: https://sf.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/6.2.0/threads-win32/seh/

.. _issues: https://mingwpy.github.io/issues.html

Performance improvements for packbits and unpackbits

The functions numpy.packbits with boolean input and numpy.unpackbits have
been optimized to be a significantly faster for contiguous data.

Fix for PPC long double floating point information

In previous versions of NumPy, the finfo function returned invalid
information about the double double_ format of the longdouble float type
on Power PC (PPC). The invalid values resulted from the failure of the NumPy
algorithm to deal with the variable number of digits in the significand
that are a feature of PPC long doubles. This release by-passes the failing
algorithm by using heuristics to detect the presence of the PPC double double
format. A side-effect of using these heuristics is that the finfo
function is faster than previous releases.

.. _PPC long doubles: https://www.ibm.com/support/knowledgecenter/en/ssw_aix_71/com.ibm.aix.genprogc/128bit_long_double_floating-point_datatype.htm

.. _double double: https://en.wikipedia.org/wiki/Quadruple-precision_floating-point_formatDouble-double_arithmetic

Better default repr for ndarray subclasses

Subclasses of ndarray with no repr specialization now correctly indent
their data and type lines.

More reliable comparisons of masked arrays

Comparisons of masked arrays were buggy for masked scalars and failed for
structured arrays with dimension higher than one. Both problems are now
solved. In the process, it was ensured that in getting the result for a
structured array, masked fields are properly ignored, i.e., the result is equal
if all fields that are non-masked in both are equal, thus making the behaviour
identical to what one gets by comparing an unstructured masked array and then
doing .all() over some axis.

np.matrix with booleans elements can now be created using the string syntax

np.matrix failed whenever one attempts to use it with booleans, e.g.,
np.matrix('True'). Now, this works as expected.

More linalg operations now accept empty vectors and matrices

All of the following functions in np.linalg now work when given input
arrays with a 0 in the last two dimensions: det, slogdet, pinv,
eigvals, eigvalsh, eig, eigh.

Bundled version of LAPACK is now 3.2.2

NumPy comes bundled with a minimal implementation of lapack for systems without
a lapack library installed, under the name of lapack_lite. This has been
upgraded from LAPACK 3.0.0 (June 30, 1999) to LAPACK 3.2.2 (June 30, 2010). See
the LAPACK changelogs_ for details on the all the changes this entails.

While no new features are exposed through numpy, this fixes some bugs
regarding "workspace" sizes, and in some places may use faster algorithms.

.. _LAPACK changelogs: http://www.netlib.org/lapack/release_notes.html_4_history_of_lapack_releases

reduce of np.hypot.reduce and np.logical_xor allowed in more cases

This now works on empty arrays, returning 0, and can reduce over multiple axes.
Previously, a ValueError was thrown in these cases.

Better repr of object arrays

Object arrays that contain themselves no longer cause a recursion error.

Object arrays that contain list objects are now printed in a way that makes
clear the difference between a 2d object array, and a 1d object array of lists.

Changes

argsort on masked arrays takes the same default arguments as sort

By default, argsort now places the masked values at the end of the sorted
array, in the same way that sort already did. Additionally, the
end_with argument is added to argsort, for consistency with sort.
Note that this argument is not added at the end, so breaks any code that
passed fill_value as a positional argument.

average now preserves subclasses

For ndarray subclasses, numpy.average will now return an instance of the
subclass, matching the behavior of most other NumPy functions such as mean.
As a consequence, also calls that returned a scalar may now return a subclass
array scalar.

array == None and array != None do element-wise comparison

Previously these operations returned scalars False and True respectively.

np.equal, np.not_equal for object arrays ignores object identity

Previously, these functions always treated identical objects as equal. This had
the effect of overriding comparison failures, comparison of objects that did
not return booleans, such as np.arrays, and comparison of objects where the
results differed from object identity, such as NaNs.

Boolean indexing changes

• Boolean array-likes (such as lists of python bools) are always treated as
  boolean indexes.

• Boolean scalars (including python True) are legal boolean indexes and
  never treated as integers.

• Boolean indexes must match the dimension of the axis that they index.

• Boolean indexes used on the lhs of an assignment must match the dimensions of
  the rhs.

• Boolean indexing into scalar arrays return a new 1-d array. This means that
  array(1)[array(True)] gives array([1]) and not the original array.

np.random.multivariate_normal behavior with bad covariance matrix

It is now possible to adjust the behavior the function will have when dealing
with the covariance matrix by using two new keyword arguments:

• tol can be used to specify a tolerance to use when checking that
  the covariance matrix is positive semidefinite.

• check_valid can be used to configure what the function will do in the
  presence of a matrix that is not positive semidefinite. Valid options are
  ignore, warn and raise. The default value, warn keeps the
  the behavior used on previous releases.

assert_array_less compares np.inf and -np.inf now

Previously, np.testing.assert_array_less ignored all infinite values. This
is not the expected behavior both according to documentation and intuitively.
Now, -inf < x < inf is considered True for any real number x and all
other cases fail.

assert_array_ and masked arrays assert_equal hide less warnings

Some warnings that were previously hidden by the assert_array_
functions are not hidden anymore. In most cases the warnings should be
correct and, should they occur, will require changes to the tests using
these functions.
For the masked array assert_equal version, warnings may occur when
comparing NaT. The function presently does not handle NaT or NaN
specifically and it may be best to avoid it at this time should a warning
show up due to this change.

offset attribute value in memmap objects

The offset attribute in a memmap object is now set to the
offset into the file. This is a behaviour change only for offsets
greater than mmap.ALLOCATIONGRANULARITY.

np.real and np.imag return scalars for scalar inputs

Previously, np.real and np.imag used to return array objects when
provided a scalar input, which was inconsistent with other functions like
np.angle and np.conj.

The polynomial convenience classes cannot be passed to ufuncs

The ABCPolyBase class, from which the convenience classes are derived, sets
__array_ufun__ = None in order of opt out of ufuncs. If a polynomial
convenience class instance is passed as an argument to a ufunc, a TypeError
will now be raised.

Output arguments to ufuncs can be tuples also for ufunc methods

For calls to ufuncs, it was already possible, and recommended, to use an
out argument with a tuple for ufuncs with multiple outputs. This has now
been extended to output arguments in the reduce, accumulate, and
reduceat methods. This is mostly for compatibility with __array_ufunc;
there are no ufuncs yet that have more than one output.

pandas 0.20.1 -> 0.20.2

0.20.2

---

This is a minor bug-fix release in the 0.20.x series and includes some small regression fixes,
bug fixes and performance improvements.
We recommend that all users upgrade to this version.

.. contents:: What's new in v0.20.2
:local:
:backlinks: none

.. _whatsnew_0202.enhancements:

Enhancements

• Unblocked access to additional compression types supported in pytables: 'blosc:blosclz, 'blosc:lz4', 'blosc:lz4hc', 'blosc:snappy', 'blosc:zlib', 'blosc:zstd' (:issue:14478)
• Series provides a to_latex method (:issue:16180)

• A new groupby method :meth:~pandas.core.groupby.GroupBy.ngroup,
  parallel to the existing :meth:~pandas.core.groupby.GroupBy.cumcount,
  has been added to return the group order (:issue:11642); see
  :ref:here <groupby.ngroup>.

.. _whatsnew_0202.performance:

Performance Improvements

• Performance regression fix when indexing with a list-like (:issue:16285)
• Performance regression fix for MultiIndexes (:issue:16319, :issue:16346)
• Improved performance of .clip() with scalar arguments (:issue:15400)
• Improved performance of groupby with categorical groupers (:issue:16413)
• Improved performance of MultiIndex.remove_unused_levels() (:issue:16556)

.. _whatsnew_0202.bug_fixes:

Bug Fixes

• Silenced a warning on some Windows environments about "tput: terminal attributes: No such device or address" when
  detecting the terminal size. This fix only applies to python 3 (:issue:16496)
• Bug in using pathlib.Path or py.path.local objects with io functions (:issue:16291)
• Bug in Index.symmetric_difference() on two equal MultiIndex's, results in a TypeError (:issue 13490)
• Bug in DataFrame.update() with overwrite=False and NaN values (:issue:15593)
• Passing an invalid engine to :func:read_csv now raises an informative
  ValueError rather than UnboundLocalError. (:issue:16511)
• Bug in :func:unique on an array of tuples (:issue:16519)
• Bug in :func:cut when labels are set, resulting in incorrect label ordering (:issue:16459)
• Fixed a compatibility issue with IPython 6.0's tab completion showing deprecation warnings on Categoricals (:issue:16409)

Conversion
^^^^^^^^^^

• Bug in :func:to_numeric in which empty data inputs were causing a segfault of the interpreter (:issue:16302)
• Silence numpy warnings when broadcasting DataFrame to Series with comparison ops (:issue:16378, :issue:16306)

Indexing
^^^^^^^^

• Bug in DataFrame.reset_index(level=) with single level index (:issue:16263)
• Bug in partial string indexing with a monotonic, but not strictly-monotonic, index incorrectly reversing the slice bounds (:issue:16515)
• Bug in MultiIndex.remove_unused_levels() that would not return a MultiIndex equal to the original. (:issue:16556)

I/O
^^^

• Bug in :func:read_csv when comment is passed in a space delimited text file (:issue:16472)
• Bug in :func:read_csv not raising an exception with nonexistent columns in usecols when it had the correct length (:issue:14671)
• Bug that would force importing of the clipboard routines unnecessarily, potentially causing an import error on startup (:issue:16288)
• Bug that raised IndexError when HTML-rendering an empty DataFrame (:issue:15953)
• Bug in :func:read_csv in which tarfile object inputs were raising an error in Python 2.x for the C engine (:issue:16530)
• Bug where DataFrame.to_html() ignored the index_names parameter (:issue:16493)
• Bug where pd.read_hdf() returns numpy strings for index names (:issue:13492)

• Bug in HDFStore.select_as_multiple() where start/stop arguments were not respected (:issue:16209)

Plotting
^^^^^^^^

• Bug in DataFrame.plot with a single column and a list-like color (:issue:3486)
• Bug in plot where NaT in DatetimeIndex results in Timestamp.min (:issue: 12405)
• Bug in DataFrame.boxplot where figsize keyword was not respected for non-grouped boxplots (:issue:11959)

Groupby/Resample/Rolling
^^^^^^^^^^^^^^^^^^^^^^^^

• Bug in creating a time-based rolling window on an empty DataFrame (:issue:15819)
• Bug in rolling.cov() with offset window (:issue:16058)
• Bug in .resample() and .groupby() when aggregating on integers (:issue:16361)

Sparse
^^^^^^

• Bug in construction of SparseDataFrame from scipy.sparse.dok_matrix (:issue:16179)

Reshaping
^^^^^^^^^

• Bug in DataFrame.stack with unsorted levels in MultiIndex columns (:issue:16323)
• Bug in pd.wide_to_long() where no error was raised when i was not a unique identifier (:issue:16382)
• Bug in Series.isin(..) with a list of tuples (:issue:16394)
• Bug in construction of a DataFrame with mixed dtypes including an all-NaT column. (:issue:16395)
• Bug in DataFrame.agg() and Series.agg() with aggregating on non-callable attributes (:issue:16405)

Numeric
^^^^^^^

• Bug in .interpolate(), where limit_direction was not respected when limit=None (default) was passed (:issue:16282)

Categorical
^^^^^^^^^^^

• Fixed comparison operations considering the order of the categories when both categoricals are unordered (:issue:16014)

Other
^^^^^

• Bug in DataFrame.drop() with an empty-list with non-unique indices (:issue:16270)

.. _whatsnew_0131:

Sphinx 1.6.1 -> 1.6.3

1.6.3

=====================================

Features added

• latex: hint that code-block continues on next page (refs: 3764, 3792)

Bugs fixed

• 3821: Failed to import sphinx.util.compat with docutils-0.14rc1
• 3829: sphinx-quickstart template is incomplete regarding use of alabaster
• 3772: 'str object' has no attribute 'filename'
• Emit wrong warnings if citation label includes hyphens (refs: 3565)
• 3858: Some warnings are not colored when using --color option
• 3775: Remove unwanted whitespace in default template
• 3835: sphinx.ext.imgmath fails to convert SVG images if project directory
  name contains spaces
• 3850: Fix color handling in make mode's help command
• 3865: use of self.env.warn in sphinx extension fails
• 3824: production lists apply smart quotes transform since Sphinx 1.6.1
• latex: fix \sphinxbfcode swallows initial space of argument
• 3878: Quotes in auto-documented class attributes should be straight quotes
  in PDF output
• 3881: LaTeX figure floated to next page sometimes leaves extra vertical
  whitespace
• 3885: duplicated footnotes raises IndexError
• 3873: Failure of deprecation warning mechanism of
  sphinx.util.compat.Directive
• 3874: Bogus warnings for "citation not referenced" for cross-file citations
• 3860: Don't download images when builders not supported images
• 3860: Remote image URIs without filename break builders not supported remote
  images
• 3833: command line messages are translated unintentionally with language
  setting.
• 3840: make checking epub_uid strict
• 3851, 3706: Fix about box drawing characters for PDF output
• 3900: autosummary could not find methods
• 3902: Emit error if latex_documents contains non-unicode string in py2

1.6.2

=====================================

Incompatible changes

• 3789: Do not require typing module for python>=3.5

Bugs fixed

• 3754: HTML builder crashes if HTML theme appends own stylesheets
• 3756: epub: Entity 'mdash' not defined
• 3758: Sphinx crashed if logs are emitted in conf.py
• 3755: incorrectly warns about dedent with literalinclude
• 3742: RTD <https://readthedocs.org/>_ PDF builds of Sphinx own docs are
  missing an index entry in the bookmarks and table of contents. This is
  rtfd/readthedocs.org2857 <https://github.com/rtfd/readthedocs.org/issues/2857>_ issue, a workaround
  is obtained using some extra LaTeX code in Sphinx's own :file:conf.py
• 3770: Build fails when a "code-block" has the option emphasize-lines and the
  number indicated is higher than the number of lines
• 3774: Incremental HTML building broken when using citations
• 3763: got epubcheck validations error if epub_cover is set
• 3779: 'ImportError' in sphinx.ext.autodoc due to broken 'sys.meta_path'.
  Thanks to Tatiana Tereshchenko.
• 3796: env.resolve_references() crashes when non-document node given
• 3803: Sphinx crashes with invalid PO files
• 3791: PDF "continued on next page" for long tables isn't internationalized
• 3788: smartquotes emits warnings for unsupported languages
• 3807: latex Makefile for make latexpdf is only for unixen
• 3781: double hyphens in option directive are compiled as endashes
• 3817: latex builder raises AttributeError

cryptography 1.8.1 -> 1.9

1.9

• BACKWARDS INCOMPATIBLE: Elliptic Curve signature verification no longer
  returns True on success. This brings it in line with the interface's
  documentation, and our intent. The correct way to use
  :meth:~cryptography.hazmat.primitives.asymmetric.ec.EllipticCurvePublicKey.verify
  has always been to check whether or not
  :class:~cryptography.exceptions.InvalidSignature was raised.
• BACKWARDS INCOMPATIBLE: Dropped support for macOS 10.7 and 10.8.
• BACKWARDS INCOMPATIBLE: The minimum supported PyPy version is now 5.3.
• Python 3.3 support has been deprecated, and will be removed in the next
  cryptography release.
• Add support for providing tag during
  :class:~cryptography.hazmat.primitives.ciphers.modes.GCM finalization via
  :meth:~cryptography.hazmat.primitives.ciphers.AEADDecryptionContext.finalize_with_tag.
• Fixed an issue preventing cryptography from compiling against
  LibreSSL 2.5.x.
• Added
  :meth:~cryptography.hazmat.primitives.asymmetric.ec.EllipticCurvePublicKey.key_size
  and
  :meth:~cryptography.hazmat.primitives.asymmetric.ec.EllipticCurvePrivateKey.key_size
  as convenience methods for determining the bit size of a secret scalar for
  the curve.
• Accessing an unrecognized extension marked critical on an X.509 object will
  no longer raise an UnsupportedExtension exception, instead an
  :class:~cryptography.x509.UnrecognizedExtension object will be returned.
  This behavior was based on a poor reading of the RFC, unknown critical
  extensions only need to be rejected on certificate verification.
• The CommonCrypto backend has been removed.
• MultiBackend has been removed.
• Whirlpool and RIPEMD160 have been deprecated.

1.8.2

• Fixed a compilation bug affecting OpenSSL 1.1.0f.
• Updated Windows and macOS wheels to be compiled against OpenSSL 1.1.0f.

pytest 3.0.7 -> 3.1.2

3.1.2

=========================

Bug Fixes

• Required options added via pytest_addoption will no longer prevent using
  --help without passing them. (1999)

• Respect python_files in assertion rewriting. (2121)

• Fix recursion error detection when frames in the traceback contain objects
  that can't be compared (like numpy arrays). (2459)

• UnicodeWarning is issued from the internal pytest warnings plugin only
  when the message contains non-ascii unicode (Python 2 only). (2463)

• Added a workaround for Python 3.6 WindowsConsoleIO breaking due to Pytests's
  FDCapture. Other code using console handles might still be affected by the
  very same issue and might require further workarounds/fixes, i.e. colorama.
  (2467)

Improved Documentation

• Fix internal API links to pluggy objects. (2331)

• Make it clear that pytest.xfail stops test execution at the calling point
  and improve overall flow of the skipping docs. (810)

3.1.1

=========================

Bug Fixes

• pytest warning capture no longer overrides existing warning filters. The
  previous behaviour would override all filters and caused regressions in test
  suites which configure warning filters to match their needs. Note that as a
  side-effect of this is that DeprecationWarning and
  PendingDeprecationWarning are no longer shown by default. (2430)

• Fix issue with non-ascii contents in doctest text files. (2434)

• Fix encoding errors for unicode warnings in Python 2. (2436)

• pytest.deprecated_call now captures PendingDeprecationWarning in
  context manager form. (2441)

Improved Documentation

• Addition of towncrier for changelog management. (2390)

3.1.0

==================

New Features

• The pytest-warnings plugin has been integrated into the core and now pytest automatically
  captures and displays warnings at the end of the test session.

.. warning::

This feature may disrupt test suites which apply and treat warnings themselves, and can be
disabled in your pytest.ini:

.. code-block:: ini

 [pytest]
 addopts = -p no:warnings

See the warnings documentation page <https://docs.pytest.org/en/latest/warnings.html>_ for more
information.

Thanks nicoddemus_ for the PR.

• Added junit_suite_name ini option to specify root <testsuite> name for JUnit XML reports (533_).

• Added an ini option doctest_encoding to specify which encoding to use for doctest files.
  Thanks wheerd_ for the PR (2101_).

• pytest.warns now checks for subclass relationship rather than
  class equality. Thanks lesteve_ for the PR (2166_)

• pytest.raises now asserts that the error message matches a text or regex
  with the match keyword argument. Thanks Kriechi_ for the PR.

• pytest.param can be used to declare test parameter sets with marks and test ids.
  Thanks RonnyPfannschmidt_ for the PR.

Changes

• remove all internal uses of pytest_namespace hooks,
  this is to prepare the removal of preloadconfig in pytest 4.0
  Thanks to RonnyPfannschmidt_ for the PR.

• pytest now warns when a callable ids raises in a parametrized test. Thanks fogo_ for the PR.

• It is now possible to skip test classes from being collected by setting a
  __test__ attribute to False in the class body (2007). Thanks
  to syre for the report and lwm_ for the PR.

• Change junitxml.py to produce reports that comply with Junitxml schema.
  If the same test fails with failure in call and then errors in teardown
  we split testcase element into two, one containing the error and the other
  the failure. (2228) Thanks to kkoukiou for the PR.

• Testcase reports with a url attribute will now properly write this to junitxml.
  Thanks fushi_ for the PR (1874_).

• Remove common items from dict comparision output when verbosity=1. Also update
  the truncation message to make it clearer that pytest truncates all
  assertion messages if verbosity < 2 (1512).
  Thanks mattduck for the PR

• --pdbcls no longer implies --pdb. This makes it possible to use
  addopts=--pdbcls=module.SomeClass on pytest.ini. Thanks davidszotten_ for
  the PR (1952_).

• fix 2013_: turn RecordedWarning into namedtuple,
  to give it a comprehensible repr while preventing unwarranted modification.

• fix 2208_: ensure a iteration limit for pytest.compat.get_real_func.
  Thanks RonnyPfannschmidt for the report and PR.

• Hooks are now verified after collection is complete, rather than right after loading installed plugins. This
  makes it easy to write hooks for plugins which will be loaded during collection, for example using the
  pytest_plugins special variable (1821).
  Thanks nicoddemus for the PR.

• Modify pytest_make_parametrize_id() hook to accept argname as an
  additional parameter.
  Thanks unsignedint_ for the PR.

• Add venv to the default norecursedirs setting.
  Thanks The-Compiler_ for the PR.

• PluginManager.import_plugin now accepts unicode plugin names in Python 2.
  Thanks reutsharabani_ for the PR.

• fix 2308: When using both --lf and --ff, only the last failed tests are run.
  Thanks ojii for the PR.

• Replace minor/patch level version numbers in the documentation with placeholders.
  This significantly reduces change-noise as different contributors regnerate
  the documentation on different platforms.
  Thanks RonnyPfannschmidt_ for the PR.

• fix 2391: consider pytest_plugins on all plugin modules
  Thanks RonnyPfannschmidt for the PR.

Bug Fixes

• Fix AttributeError on sys.stdout.buffer / sys.stderr.buffer
  while using capsys fixture in python 3. (1407).
  Thanks to asottile.

• Change capture.py's DontReadFromInput class to throw io.UnsupportedOperation errors rather
  than ValueErrors in the fileno method (2276).
  Thanks metasyn and vlad-dragos_ for the PR.

• Fix exception formatting while importing modules when the exception message
  contains non-ascii characters (2336).
  Thanks fabioz for the report and nicoddemus_ for the PR.

• Added documentation related to issue (1937)
  Thanks skylarjhdownes for the PR.

• Allow collecting files with any file extension as Python modules (2369).
  Thanks Kodiologist for the PR.

• Show the correct error message when collect "parametrize" func with wrong args (2383).
  Thanks The-Compiler for the report and robin0371_ for the PR.

.. _davidszotten: https://github.com/davidszotten
.. _fabioz: https://github.com/fabioz
.. _fogo: https://github.com/fogo
.. _fushi: https://github.com/fushi
.. _Kodiologist: https://github.com/Kodiologist
.. _Kriechi: https://github.com/Kriechi
.. _mandeep: https://github.com/mandeep
.. _mattduck: https://github.com/mattduck
.. _metasyn: https://github.com/metasyn
.. _MichalTHEDUDE: https://github.com/MichalTHEDUDE
.. _ojii: https://github.com/ojii
.. _reutsharabani: https://github.com/reutsharabani
.. _robin0371: https://github.com/robin0371
.. _skylarjhdownes: https://github.com/skylarjhdownes
.. _unsignedint: https://github.com/unsignedint
.. _wheerd: https://github.com/wheerd

.. _1407: pytest-dev/pytest#1407
.. _1512: pytest-dev/pytest#1512
.. _1821: pytest-dev/pytest#1821
.. _1874: pytest-dev/pytest#1874
.. _1937: pytest-dev/pytest#1937
.. _1952: pytest-dev/pytest#1952
.. _2007: pytest-dev/pytest#2007
.. _2013: pytest-dev/pytest#2013
.. _2101: pytest-dev/pytest#2101
.. _2166: pytest-dev/pytest#2166
.. _2208: pytest-dev/pytest#2208
.. _2228: pytest-dev/pytest#2228
.. _2276: pytest-dev/pytest#2276
.. _2308: pytest-dev/pytest#2308
.. _2336: pytest-dev/pytest#2336
.. _2369: pytest-dev/pytest#2369
.. _2383: pytest-dev/pytest#2383
.. _2391: pytest-dev/pytest#2391
.. _533: pytest-dev/pytest#533

Faker 0.7.12 -> 0.7.17

0.7.17

---

• Fix a timezone issue with the date_time_between_dates provider.

0.7.16

---

• fix timezone issues with date_time_between provider.
• Add ext_word_list parameter to methods in the Lorem generator. Thanks guinslym.

0.7.15

---

• fix start and end date for datetime provider methods.

0.7.14

---

• fix future_date, `and past_date bounds.

0.7.13

---

• Remove capitalisation from hu_HU addresses. Thanks Newman101.
• Add et_EE (Estonian) provider: names and ssn. Thanks trtd.
• Proper prefix for gender in pl_PL names. Thanks zgoda.
• Add DateTime provider for pl_PL. Thanks zgoda.
• Add pl_PL internet data provider. Thanks zgoda.
• Fix diacritics in pl_PL street names. Thanks zgoda.
• Add future_date, future_datetime, past_date and past_datetime to DateTime Provider

tqdm 4.11.2 -> 4.14.0

4.13.0

• support unknown systems tqdm has no attribute 'disable' magic-wormhole/magic-wormhole#158, 76, 344 -> 390
• support nested/multi-bars better 384, 285, 329 -> 385
• ease redirection of output (default: sys.stderr -> None) tqdm-based CLI completely breaks xonsh/xonsh#2058, 329, 275 -> 293
  • add examples/redirect_print.py
• minor documentation updates

4.12.0

• fix monitor race condition 338 -> 339
• add explicit NetBSD support 344
• documentation tidy

That's it for now!

Happy merging! 🤖

[codecov-io]

Codecov Report

Merging #46 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #46   +/-   ##
=======================================
  Coverage   93.23%   93.23%           
=======================================
  Files           3        3           
  Lines         281      281           
=======================================
  Hits          262      262           
  Misses         19       19

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 76f0511...aa82786. Read the comment docs.

[pyup-bot]

Closing this in favor of #47