Scheduled weekly dependency update for week 02

[pyup-bot]

Update boto3 from 1.9.74 to 1.9.78.

Changelog

1.9.78

======

* api-change:``rds-data``: [``botocore``] Update rds-data client to latest version
* api-change:``emr``: [``botocore``] Update emr client to latest version

1.9.77

======

* api-change:``iot``: [``botocore``] Update iot client to latest version
* api-change:``ec2``: [``botocore``] Update ec2 client to latest version
* api-change:``codedeploy``: [``botocore``] Update codedeploy client to latest version
* api-change:``sagemaker``: [``botocore``] Update sagemaker client to latest version

1.9.76

======

* api-change:``docdb``: [``botocore``] Update docdb client to latest version
* api-change:``redshift``: [``botocore``] Update redshift client to latest version

1.9.75

======

* api-change:``appmesh``: [``botocore``] Update appmesh client to latest version

Links

• PyPI: https://pypi.org/project/boto3
• Changelog: https://pyup.io/changelogs/boto3/
• Repo: https://github.com/boto/boto3

Update botocore from 1.12.74 to 1.12.78.

Changelog

1.12.78

=======

* api-change:``rds-data``: Update rds-data client to latest version
* api-change:``emr``: Update emr client to latest version

1.12.77

=======

* api-change:``iot``: Update iot client to latest version
* api-change:``ec2``: Update ec2 client to latest version
* api-change:``codedeploy``: Update codedeploy client to latest version
* api-change:``sagemaker``: Update sagemaker client to latest version

1.12.76

=======

* api-change:``docdb``: Update docdb client to latest version
* api-change:``redshift``: Update redshift client to latest version

1.12.75

=======

* api-change:``appmesh``: Update appmesh client to latest version

Links

• PyPI: https://pypi.org/project/botocore
• Changelog: https://pyup.io/changelogs/botocore/
• Repo: https://github.com/boto/botocore

Update pint from 0.8.1 to 0.9.

Changelog

0.9

----------------

- Add support for registering with matplotlib's unit handling
(Issue 317, thanks dopplershift)
- Add converters for matplotlib's unit support.
(Issue 317, thanks Ryan May)
- Fix unwanted side effects in auto dimensionality reduction.
(Issue 516, thanks Ben Loer)
- Allow dimensionality check for non Quantity arguments.
- Make Quantity and UnitContainer objects hashable.
(Issue 286, thanks Nevada Sanchez)
- Fix unit tests errors with numpy >=1.13.
(Issue 577, thanks cpascual)
- Avoid error in in-place exponentiation with numpy > 1.11.
(Issue 577, thanks cpascual)
- fix compatible units in context.
(thanks enrico)
- Added warning for unsupported ufunc.
(Issue 626, thanks kanhua)
- Improve IPython pretty printers.
(Issue 590, thanks tecki)
- Drop Support for Python 2.6, 3.0, 3.1 and 3.2.
(Issue 567)
- Prepare for deprecation announced in Python 3.7
(Issue 747, thanks Simon Willison)
- Added several new units and Systems
(Issues 749, 737, )
- Started experimental pandas support
(Issue 746 and others. Thanks andrewgsavage, znicholls and others)  
- wraps and checks now supports kwargs and defaults.
(Issue 660, thanks jondoesntgit)

Links

• PyPI: https://pypi.org/project/pint
• Changelog: https://pyup.io/changelogs/pint/
• Repo: https://github.com/hgrecco/pint

Update pluggy from 0.8.0 to 0.8.1.

Changelog

0.8.1

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

Trivial/Internal Changes
------------------------

- `166 <https://github.com/pytest-dev/pluggy/issues/166>`_: Add ``stacklevel=2`` to implprefix warning so that the reported location of warning is the caller of PluginManager.

Links

• PyPI: https://pypi.org/project/pluggy
• Changelog: https://pyup.io/changelogs/pluggy/
• Repo: https://github.com/pytest-dev/pluggy

Update pyparsing from 2.3.0 to 2.3.1.

Changelog

2.3.1

-----------------------------
- POSSIBLE API CHANGE: this release fixes a bug when results names were
attached to a MatchFirst or Or object containing an And object.
Previously, a results name on an And object within an enclosing MatchFirst
or Or could return just the first token in the And. Now, all the tokens
matched by the And are correctly returned. This may result in subtle
changes in the tokens returned if you have this condition in your pyparsing
scripts.

- New staticmethod ParseException.explain() to help diagnose parse exceptions
by showing the failing input line and the trace of ParserElements in
the parser leading up to the exception. explain() returns a multiline
string listing each element by name. (This is still an experimental
method, and the method signature and format of the returned string may
evolve over the next few releases.)

Example:
      define a parser to parse an integer followed by an
      alphabetic word
     expr = pp.Word(pp.nums).setName("int")
            + pp.Word(pp.alphas).setName("word")
     try:
          parse a string with a numeric second value instead of alpha
         expr.parseString("123 355")
     except pp.ParseException as pe:
         print_(pp.ParseException.explain(pe))

Prints:
     123 355
         ^
     ParseException: Expected word (at char 4), (line:1, col:5)
     __main__.ExplainExceptionTest
     pyparsing.And - {int word}
     pyparsing.Word - word

explain() will accept any exception type and will list the function
names and parse expressions in the stack trace. This is especially
useful when an exception is raised in a parse action.

Note: explain() is only supported under Python 3.

- Fix bug in dictOf which could match an empty sequence, making it
infinitely loop if wrapped in a OneOrMore.

- Added unicode sets to pyparsing_unicode for Latin-A and Latin-B ranges.

- Added ability to define custom unicode sets as combinations of other sets
using multiple inheritance.

 class Turkish_set(pp.pyparsing_unicode.Latin1, pp.pyparsing_unicode.LatinA):
     pass

 turkish_word = pp.Word(Turkish_set.alphas)

- Updated state machine import examples, with state machine demos for:
. traffic light
. library book checkin/checkout
. document review/approval

In the traffic light example, you can use the custom 'statemachine' keyword
to define the states for a traffic light, and have the state classes
auto-generated for you:

   statemachine TrafficLightState:
       Red -> Green
       Green -> Yellow
       Yellow -> Red

Similar for state machines with named transitions, like the library book
state example:

   statemachine LibraryBookState:
       New -(shelve)-> Available
       Available -(reserve)-> OnHold
       OnHold -(release)-> Available
       Available -(checkout)-> CheckedOut
       CheckedOut -(checkin)-> Available

Once the classes are defined, then additional Python code can reference those
classes to add class attributes, instance methods, etc.

See the examples in examples/statemachine

- Added an example parser for the decaf language. This language is used in
CS compiler classes in many colleges and universities.

- Fixup of docstrings to Sphinx format, inclusion of test files in the source
package, and convert markdown to rst throughout the distribution, great job
by Matěj Cepl!

- Expanded the whitespace characters recognized by the White class to include
all unicode defined spaces. Suggested in Issue 51 by rtkjbillo.

- Added optional postParse argument to ParserElement.runTests() to add a
custom callback to be called for test strings that parse successfully. Useful
for running tests that do additional validation or processing on the parsed
results. See updated chemicalFormulas.py example.

- Removed distutils fallback in setup.py. If installing the package fails,
please update to the latest version of setuptools. Plus overall project code
cleanup (CRLFs, whitespace, imports, etc.), thanks Jon Dufresne!

- Fix bug in CaselessKeyword, to make its behavior consistent with
Keyword(caseless=True). Fixes Issue 65 reported by telesphore.

Links

• PyPI: https://pypi.org/project/pyparsing
• Changelog: https://pyup.io/changelogs/pyparsing/
• Repo: https://github.com/pyparsing/pyparsing/
• Docs: https://pythonhosted.org/pyparsing/

Update tox from 3.6.1 to 3.7.0.

The bot wasn't able to find a changelog for this release. Got an idea?

Links

• PyPI: https://pypi.org/project/tox
• Docs: https://tox.readthedocs.org/

Update wrapt from 1.10.11 to 1.11.0.

Changelog

1.11.0

---------------

**Bugs Fixed**

* When using arithmetic operations through a proxy object, checks about
the types of arguments were not being performed correctly, which could
result in an exception being raised to indicate that a proxy object had
not been initialised when in fact the argument wasn't even an instance
of a proxy object.

Because an incorrect cast in C level code was being performed and
an attribute in memory checked on the basis of it being a type different
to what it actually was, technically it may have resulted in a process
crash if the size of the object was smaller than the type being casted
to.

* The ``__complex__()`` special method wasn't implemented and using
``complex()`` on a proxy object would give wrong results or fail.

* When using the C extension, if an exception was raised when using inplace
or, ie., ``|=``, the error condition wasn't being correctly propagated
back which would result in an exception showing up as wrong location
in subsequent code.

* Type of ``long`` was used instead of ``Py_hash_t`` for Python 3.3+. This
caused compiler warnings on Windows, which depending on what locale was
set to, would cause pip to fail when installing the package.

* If calling ``Class.instancemethod`` and passing ``self`` explicitly, the
ability to access ``__name__`` and ``__module__`` on the final bound
method were not preserved. This was due to a ``partial`` being used for
this special case, and it doesn't preserve introspection.

* Fixed typo in the getter property of ``ObjectProxy`` for accessing
``__annotations__``. Appeared that it was still working as would fall back
to using generic ``__getattr__()`` to access attribute on wrapped object.

**Features Changed**

* Dropped support for Python 2.6 and 3.3.

* If ``copy.copy()`` or ``copy.deepcopy()`` is used on an instance of the
``ObjectProxy`` class, a ``NotImplementedError`` exception is raised, with
a message indicating that the object proxy must implement the
``__copy__()`` or ``__deepcopy__()`` method. This is in place of the
default ``TypeError`` exception with message indicating a pickle error.

* If ``pickle.dump()`` or ``pickle.dumps()`` is used on an instance of the
``ObjectProxy`` class, a ``NotImplementedError`` exception is raised, with
a message indicating that the object proxy must implement the
``__reduce_ex__()`` method. This is in place of the default ``TypeError``
exception with message indicating a pickle error.

Links

• PyPI: https://pypi.org/project/wrapt
• Changelog: https://pyup.io/changelogs/wrapt/
• Repo: https://github.com/GrahamDumpleton/wrapt

[codecov]

Codecov Report

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

@@          Coverage Diff           @@
##           master    #570   +/-   ##
======================================
  Coverage    96.8%   96.8%           
======================================
  Files          54      54           
  Lines        2853    2853           
  Branches      326     326           
======================================
  Hits         2761    2761           
  Misses         53      53           
  Partials       39      39