Scheduled weekly dependency update for week 23

[pyup-bot]

Update pytest from 3.6.0 to 3.6.1.

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

Links

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

Update aiohttp from 3.2.1 to 3.3.1.

Changelog

3.3.0

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

Features
--------

- Raise ``ConnectionResetError`` instead of ``CancelledError`` on trying to
write to a closed stream. (`2499 <https://github.com/aio-libs/aiohttp/pull/2499>`_)
- Implement ``ClientTimeout`` class and support socket read timeout. (`2768 <https://github.com/aio-libs/aiohttp/pull/2768>`_)
- Enable logging when ``aiohttp.web`` is used as a program (`2956 <https://github.com/aio-libs/aiohttp/pull/2956>`_)
- Add canonical property to resources (`2968 <https://github.com/aio-libs/aiohttp/pull/2968>`_)
- Forbid reading response BODY after release (`2983 <https://github.com/aio-libs/aiohttp/pull/2983>`_)
- Implement base protocol class to avoid a dependency from internal
``asyncio.streams.FlowControlMixin`` (`2986 <https://github.com/aio-libs/aiohttp/pull/2986>`_)
- Cythonize ``helpers.reify``, 5% boost on macro benchmark (`2995 <https://github.com/aio-libs/aiohttp/pull/2995>`_)
- Optimize HTTP parser (`3015 <https://github.com/aio-libs/aiohttp/pull/3015>`_)
- Implement ``runner.addresses`` property. (`3036 <https://github.com/aio-libs/aiohttp/pull/3036>`_)
- Use ``bytearray`` instead of a list of ``bytes`` in websocket reader. It
improves websocket message reading a little. (`3039 <https://github.com/aio-libs/aiohttp/pull/3039>`_)
- Remove heartbeat on closing connection on keepalive timeout. The used hack
violates HTTP protocol. (`3041 <https://github.com/aio-libs/aiohttp/pull/3041>`_)
- Limit websocket message size on reading to 4 MB by default. (`3045 <https://github.com/aio-libs/aiohttp/pull/3045>`_)


Bugfixes
--------

- Don't reuse a connection with the same URL but different proxy/TLS settings
(`2981 <https://github.com/aio-libs/aiohttp/pull/2981>`_)
- When parsing the Forwarded header, the optional port number is now preserved.
(`3009 <https://github.com/aio-libs/aiohttp/pull/3009>`_)


Improved Documentation
----------------------

- Make Change Log more visible in docs (`3029 <https://github.com/aio-libs/aiohttp/pull/3029>`_)
- Make style and grammar improvements on the FAQ page. (`3030 <https://github.com/aio-libs/aiohttp/pull/3030>`_)
- Document that signal handlers should be async functions since aiohttp 3.0
(`3032 <https://github.com/aio-libs/aiohttp/pull/3032>`_)


Deprecations and Removals
-------------------------

- Deprecate custom application's router. (`3021 <https://github.com/aio-libs/aiohttp/pull/3021>`_)


Misc
----

- 3008, 3011

Links

• PyPI: https://pypi.org/project/aiohttp
• Changelog: https://pyup.io/changelogs/aiohttp/
• Repo: https://github.com/aio-libs/aiohttp

Update aiomysql from 0.0.15 to 0.0.16.

Changelog

0.0.16

^^^^^^^^^^^^^^^^^^^

* Added ability to execute precompiled sqlalchemy queries 294 (Thanks vlanse)

Links

• PyPI: https://pypi.org/project/aiomysql
• Changelog: https://pyup.io/changelogs/aiomysql/
• Repo: https://github.com/aio-libs/aiomysql

Update sqlalchemy from 1.2.7 to 1.2.8.

Changelog

1.2.8

:released: May 28, 2018

 .. change::
 	:tags: bug, orm
 	:tickets: 4256

 	Fixed regression in 1.2.7 caused by :ticket:`4228`, which itself was fixing
 	a 1.2-level regression, where the ``query_cls`` callable passed to a
 	:class:`.Session` was assumed to be a subclass of :class:`.Query`  with
 	class method availability, as opposed to an arbitrary callable.    In
 	particular, the dogpile caching example illustrates ``query_cls`` as a
 	function and not a :class:`.Query` subclass.

 .. change::
     :tags: bug, engine
     :tickets: 4252
     :versions: 1.3.0b1

     Fixed connection pool issue whereby if a disconnection error were raised
     during the connection pool's "reset on return" sequence in conjunction with
     an explicit transaction opened against the enclosing :class:`.Connection`
     object (such as from calling :meth:`.Session.close` without a rollback or
     commit, or calling :meth:`.Connection.close` without first closing a
     transaction declared with :meth:`.Connection.begin`), a double-checkin would
     result, which could then lead towards concurrent checkouts of the same
     connection. The double-checkin condition is now prevented overall by an
     assertion, as well as the specific double-checkin scenario has been
     fixed.

 .. change::
     :tags: bug, oracle
     :tickets: 4264
     :versions: 1.3.0b1

     The Oracle BINARY_FLOAT and BINARY_DOUBLE datatypes now participate within
     cx_Oracle.setinputsizes(), passing along NATIVE_FLOAT, so as to support the
     NaN value.  Additionally, :class:`.oracle.BINARY_FLOAT`,
     :class:`.oracle.BINARY_DOUBLE` and :class:`.oracle.DOUBLE_PRECISION` now
     subclass :class:`.Float`, since these are floating point datatypes, not
     decimal.  These datatypes were already defaulting the
     :paramref:`.Float.asdecimal` flag to False in line with what
     :class:`.Float` already does.

 .. change::
     :tags: bug, oracle
     :versions: 1.3.0b1

     Added reflection capabilities for the :class:`.oracle.BINARY_FLOAT`,
     :class:`.oracle.BINARY_DOUBLE` datatypes.


 .. change::
 	:tags: bug, ext
 	:tickets: 4247

 	The horizontal sharding extension now makes use of the identity token
 	added to ORM identity keys as part of :ticket:`4137`, when an object
 	refresh or column-based deferred load or unexpiration operation occurs.
 	Since we know the "shard" that the object originated from, we make
 	use of this value when refreshing, thereby avoiding queries against
 	other shards that don't match this object's identity in any case.

 .. change::
     :tags: bug, sql
     :versions: 1.3.0b1

     Fixed issue where the "ambiguous literal" error message used when
     interpreting literal values as SQL expression values would encounter a
     tuple value, and fail to format the message properly. Pull request courtesy
     Miguel Ventura.

 .. change::
     :tags: bug, mssql
     :tickets: 4250

     Fixed a 1.2 regression caused by :ticket:`4061` where the SQL Server
     "BIT" type would be considered to be "native boolean".  The goal here
     was to avoid creating a CHECK constraint on the column, however the bigger
     issue is that the BIT value does not behave like a true/false constant
     and cannot be interpreted as a standalone expression, e.g.
     "WHERE <column>".   The SQL Server dialect now goes back to being
     non-native boolean, but with an extra flag that still avoids creating
     the CHECK constraint.

 .. change::
     :tags: bug, oracle
     :tickets: 4259
     :versions: 1.3.0b1

     Altered the Oracle dialect such that when an :class:`.Integer` type is in
     use, the cx_Oracle.NUMERIC type is set up for setinputsizes().  In
     SQLAlchemy 1.1 and earlier, cx_Oracle.NUMERIC was passed for all numeric
     types unconditionally, and in 1.2 this was removed to allow for better
     numeric precision.  However, for integers, some database/client setups
     will fail to coerce boolean values True/False into integers which introduces
     regressive behavior when using SQLAlchemy 1.2.  Overall, the setinputsizes
     logic seems like it will need a lot more flexibility going forward so this
     is a start for that.

 .. change::
     :tags: bug, engine
     :versions: 1.3.0b1

     Fixed a reference leak issue where the values of the parameter dictionary
     used in a statement execution would remain referenced by the "compiled
     cache", as a result of storing the key view used by Python 3 dictionary
     keys().  Pull request courtesy Olivier Grisel.

 .. change::
     :tags: bug, orm
     :tickets: 4128

     Fixed a long-standing regression that occurred in version
     1.0, which prevented the use of a custom :class:`.MapperOption`
     that alters the _params of a :class:`.Query` object for a
     lazy load, since the lazy loader itself would overwrite those
     parameters.   This applies to the "temporal range" example
     on the wiki.  Note however that the
     :meth:`.Query.populate_existing` method is now required in
     order to rewrite the mapper options associated with an object
     already loaded in the identity map.

     As part of this change, a custom defined
     :class:`.MapperOption` will now cause lazy loaders related to
     the target object to use a non-baked query by default unless
     the :meth:`.MapperOption._generate_cache_key` method is implemented.
     In particular, this repairs one regression which occured when
     using the dogpile.cache "advanced" example, which was not
     returning cached results and instead emitting SQL due to an
     incompatibility with the baked query loader; with the change,
     the ``RelationshipCache`` option included for many releases
     in the dogpile example will disable the "baked" query altogether.
     Note that the dogpile example is also modernized to avoid both
     of these issues as part of issue :ticket:`4258`.

 .. change::
 	:tags: bug, ext
 	:tickets: 4266
 	:versions: 1.3.0b1

 	Fixed a race condition which could occur if automap
 	:meth:`.AutomapBase.prepare` were used within a multi-threaded context
 	against other threads which  may call :func:`.configure_mappers` as a
 	result of use of other mappers.  The unfinished mapping work of automap
 	is particularly sensitive to being pulled in by a
 	:func:`.configure_mappers` step leading to errors.

 .. change::
     :tags: bug, orm

     Fixed bug where the new :meth:`.baked.Result.with_post_criteria`
     method would not interact with a subquery-eager loader correctly,
     in that the "post criteria" would not be applied to embedded
     subquery eager loaders.   This is related to :ticket:`4128` in that
     the post criteria feature is now used by the lazy loader.

 .. change::
 	:tags: bug, tests
 	:tickets: 4249
 	:versions: 1.3.0b1

 	Fixed a bug in the test suite where if an external dialect returned
 	``None`` for ``server_version_info``, the exclusion logic would raise an
 	``AttributeError``.

 .. change::
     :tags: bug, orm
     :tickets: 4258

     Updated the dogpile.caching example to include new structures that
     accommodate for the "baked" query system, which is used by default within
     lazy loaders and some eager relationship loaders. The dogpile.caching
     "relationship_caching" and "advanced" examples were also broken due to
     :ticket:`4256`.  The issue here is also worked-around by the fix in
     :ticket:`4128`.

.. changelog::

Links

• PyPI: https://pypi.org/project/sqlalchemy
• Changelog: https://pyup.io/changelogs/sqlalchemy/
• Homepage: http://www.sqlalchemy.org

Update sphinx from 1.7.4 to 1.7.5.

Changelog

1.7.5

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

Bugs fixed
----------

* 4924: html search: Upper characters problem in any other languages
* 4932: apidoc: some subpackage is ignored if sibling subpackage contains a
module starting with underscore
* 4863, 4938, 4939: i18n doesn't handle node.title correctly tat used for
contents, topic, admonition, table and section.
* 4913: i18n: literal blocks in bullet list are not translated
* 4962: C++, raised TypeError on duplicate declaration.
* 4825: C++, properly parse expr roles and give better error messages when
(escaped) line breaks are present.
* C++, properly use ``desc_addname`` nodes for prefixes of names.
* C++, parse pack expansions in function calls.
* 4915, 4916: links on search page are broken when using dirhtml builder
* 4969: autodoc: constructor method should not have return annotation
* latex: deeply nested enumerated list which is beginning with non-1 causes
LaTeX engine crashed
* 4978: latex: shorthandoff is not set up for Brazil locale
* 4928: i18n: Ignore dot-directories like .git/ in LC_MESSAGES/
* 4946: py domain: type field could not handle "None" as a type
* 4979: latex: Incorrect escaping of curly braces in index entries
* 4956: autodoc: Failed to extract document from a subclass of the class on
mocked module
* 4973: latex: glossary directive adds whitespace to each item
* 4980: latex: Explicit labels on code blocks are duplicated
* 4919: node.asdom() crashes if toctree has :numbered: option
* 4914: autodoc: Parsing error when using dataclasses without default values
* 4931: autodoc: crashed when handler for autodoc-skip-member raises an error
* 4931: autodoc: crashed when subclass of mocked class are processed by
napoleon module
* 5007: sphinx-build crashes when error log contains a "%" character

Links

• PyPI: https://pypi.org/project/sphinx
• Changelog: https://pyup.io/changelogs/sphinx/
• Homepage: http://sphinx-doc.org/

[codecov]

Codecov Report

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

@@           Coverage Diff           @@
##           master     #372   +/-   ##
=======================================
  Coverage   80.96%   80.96%           
=======================================
  Files          13       13           
  Lines         604      604           
  Branches       92       92           
=======================================
  Hits          489      489           
  Misses        103      103           
  Partials       12       12

---

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 fc79892...832c7b9. Read the comment docs.