Scheduled weekly dependency update for week 38

[pyup-bot]

Update SQLAlchemy from 1.2.11 to 1.2.12.

Changelog

1.2.12

:released: September 19, 2018

 .. change::
     :tags: bug, postgresql
     :tickets: 4325

     Fixed bug in PostgreSQL dialect where compiler keyword arguments such as
     ``literal_binds=True`` were not being propagated to a DISTINCT ON
     expression.

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

     Fixed issue where :class:`.BakedQuery` did not include the specific query
     class used by the :class:`.Session` as part of the cache key, leading to
     incompatibilities when using custom query classes, in particular the
     :class:`.ShardedQuery` which has some different argument signatures.

 .. change::
     :tags: bug, postgresql
     :tickets: 4324

     Fixed the :func:`.postgresql.array_agg` function, which is a slightly
     altered version of the usual :func:`.functions.array_agg` function, to also
     accept an incoming "type" argument without forcing an ARRAY around it,
     essentially the same thing that was fixed for the generic function in 1.1
     in :ticket:`4107`.

 .. change::
     :tags: bug, postgresql
     :tickets: 4323

     Fixed bug in PostgreSQL ENUM reflection where a case-sensitive, quoted name
     would be reported by the query including quotes, which would not match a
     target column during table reflection as the quotes needed to be stripped
     off.


 .. change::
    :tags: bug, orm

    Added a check within the weakref cleanup for the :class:`.InstanceState`
    object to check for the presence of the ``dict`` builtin, in an effort to
    reduce error messages generated when these cleanups occur during interpreter
    shutdown.  Pull request courtesy Romuald Brunet.

 .. change::
     :tags: bug, orm, declarative
     :tickets: 4326

     Fixed bug where the declarative scan for attributes would receive the
     expression proxy delivered by a hybrid attribute at the class level, and
     not the hybrid attribute itself, when receiving the descriptor via the
     ``declared_attr`` callable on a subclass of an already-mapped class. This
     would lead to an attribute that did not report itself as a hybrid when
     viewed within :attr:`.Mapper.all_orm_descriptors`.


 .. change::
     :tags: bug, orm
     :tickets: 4334
     :versions: 1.3.0b1

     Fixed bug where use of :class:`.Lateral` construct in conjunction with
     :meth:`.Query.join` as well as :meth:`.Query.select_entity_from` would not
     apply clause adaption to the right side of the join.   "lateral" introduces
     the use case of the right side of a join being correlatable.  Previously,
     adaptation of this clause wasn't considered.   Note that in 1.2 only,
     a selectable introduced by :meth:`.Query.subquery` is still not adapted
     due to :ticket:`4304`; the selectable needs to be produced by the
     :func:`.select` function to be the right side of the "lateral" join.

 .. change::
    :tags: bug, oracle
    :tickets: 4335

    Fixed issue for cx_Oracle 7.0 where the behavior of Oracle param.getvalue()
    now returns a list, rather than a single scalar value, breaking
    autoincrement logic throughout the Core and ORM. The dml_ret_array_val
    compatibility flag is used for cx_Oracle 6.3 and 6.4 to establish compatible
    behavior with 7.0 and forward, for cx_Oracle 6.2.1 and prior a version
    number check falls back to the old logic.


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

     Fixed 1.2 regression caused by :ticket:`3472` where the handling of an
     "updated_at" style column within the context of a post-update operation
     would also occur for a row that is to be deleted following the update,
     meaning both that a column with a Python-side value generator would show
     the now-deleted value that was emitted for the UPDATE before the DELETE
     (which was not the previous behavor), as well as that a SQL- emitted value
     generator would have the attribute expired, meaning the previous value
     would be unreachable due to the row having been deleted and the object
     detached from the session.The "postfetch" logic that was added as part of
     :ticket:`3472` is now skipped entirely for an object that ultimately is to
     be deleted.

.. changelog::

Links

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

Update pytest from 3.7.3 to 3.8.1.

Changelog

3.8.1

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

Bug Fixes
---------

- `3286 <https://github.com/pytest-dev/pytest/issues/3286>`_: ``.pytest_cache`` directory is now automatically ignored by Git. Users who would like to contribute a solution for other SCMs please consult/comment on this issue.


- `3749 <https://github.com/pytest-dev/pytest/issues/3749>`_: Fix the following error during collection of tests inside packages::

   TypeError: object of type 'Package' has no len()


- `3941 <https://github.com/pytest-dev/pytest/issues/3941>`_: Fix bug where indirect parametrization would consider the scope of all fixtures used by the test function to determine the parametrization scope, and not only the scope of the fixtures being parametrized.


- `3973 <https://github.com/pytest-dev/pytest/issues/3973>`_: Fix crash of the assertion rewriter if a test changed the current working directory without restoring it afterwards.


- `3998 <https://github.com/pytest-dev/pytest/issues/3998>`_: Fix issue that prevented some caplog properties (for example ``record_tuples``) from being available when entering the debugger with ``--pdb``.


- `3999 <https://github.com/pytest-dev/pytest/issues/3999>`_: Fix ``UnicodeDecodeError`` in python2.x when a class returns a non-ascii binary ``__repr__`` in an assertion which also contains non-ascii text.



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

- `3996 <https://github.com/pytest-dev/pytest/issues/3996>`_: New `Deprecations and Removals <https://docs.pytest.org/en/latest/deprecations.html>`_ page shows all currently
deprecated features, the rationale to do so, and alternatives to update your code. It also list features removed
from pytest in past major releases to help those with ancient pytest versions to upgrade.



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

- `3955 <https://github.com/pytest-dev/pytest/issues/3955>`_: Improve pre-commit detection for changelog filenames


- `3975 <https://github.com/pytest-dev/pytest/issues/3975>`_: Remove legacy code around im_func as that was python2 only

3.8.0

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

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

- `2452 <https://github.com/pytest-dev/pytest/issues/2452>`_: ``Config.warn`` and ``Node.warn`` have been
deprecated, see `<https://docs.pytest.org/en/latest/deprecations.htmlconfig-warn-and-node-warn>`_ for rationale and
examples.

- `3936 <https://github.com/pytest-dev/pytest/issues/3936>`_: ``pytest.mark.filterwarnings`` second parameter is no longer regex-escaped,
making it possible to actually use regular expressions to check the warning message.

**Note**: regex-escaping the match string was an implementation oversight that might break test suites which depend
on the old behavior.



Features
--------

- `2452 <https://github.com/pytest-dev/pytest/issues/2452>`_: Internal pytest warnings are now issued using the standard ``warnings`` module, making it possible to use
the standard warnings filters to manage those warnings. This introduces ``PytestWarning``,
``PytestDeprecationWarning`` and ``RemovedInPytest4Warning`` warning types as part of the public API.

Consult `the documentation <https://docs.pytest.org/en/latest/warnings.htmlinternal-pytest-warnings>`_ for more info.


- `2908 <https://github.com/pytest-dev/pytest/issues/2908>`_: ``DeprecationWarning`` and ``PendingDeprecationWarning`` are now shown by default if no other warning filter is
configured. This makes pytest more compliant with
`PEP-0506 <https://www.python.org/dev/peps/pep-0565/recommended-filter-settings-for-test-runners>`_. See
`the docs <https://docs.pytest.org/en/latest/warnings.htmldeprecationwarning-and-pendingdeprecationwarning>`_ for
more info.


- `3251 <https://github.com/pytest-dev/pytest/issues/3251>`_: Warnings are now captured and displayed during test collection.


- `3784 <https://github.com/pytest-dev/pytest/issues/3784>`_: ``PYTEST_DISABLE_PLUGIN_AUTOLOAD`` environment variable disables plugin auto-loading when set.


- `3829 <https://github.com/pytest-dev/pytest/issues/3829>`_: Added the ``count`` option to ``console_output_style`` to enable displaying the progress as a count instead of a percentage.


- `3837 <https://github.com/pytest-dev/pytest/issues/3837>`_: Added support for 'xfailed' and 'xpassed' outcomes to the ``pytester.RunResult.assert_outcomes`` signature.



Bug Fixes
---------

- `3911 <https://github.com/pytest-dev/pytest/issues/3911>`_: Terminal writer now takes into account unicode character width when writing out progress.


- `3913 <https://github.com/pytest-dev/pytest/issues/3913>`_: Pytest now returns with correct exit code (EXIT_USAGEERROR, 4) when called with unknown arguments.


- `3918 <https://github.com/pytest-dev/pytest/issues/3918>`_: Improve performance of assertion rewriting.



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

- `3566 <https://github.com/pytest-dev/pytest/issues/3566>`_: Added a blurb in usage.rst for the usage of -r flag which is used to show an extra test summary info.


- `3907 <https://github.com/pytest-dev/pytest/issues/3907>`_: Corrected type of the exceptions collection passed to ``xfail``: ``raises`` argument accepts a ``tuple`` instead of ``list``.



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

- `3853 <https://github.com/pytest-dev/pytest/issues/3853>`_: Removed ``"run all (no recorded failures)"`` message printed with ``--failed-first`` and ``--last-failed`` when there are no failed tests.

3.7.4

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

Bug Fixes
---------

- `3506 <https://github.com/pytest-dev/pytest/issues/3506>`_: Fix possible infinite recursion when writing ``.pyc`` files.


- `3853 <https://github.com/pytest-dev/pytest/issues/3853>`_: Cache plugin now obeys the ``-q`` flag when ``--last-failed`` and ``--failed-first`` flags are used.


- `3883 <https://github.com/pytest-dev/pytest/issues/3883>`_: Fix bad console output when using ``console_output_style=classic``.


- `3888 <https://github.com/pytest-dev/pytest/issues/3888>`_: Fix macOS specific code using ``capturemanager`` plugin in doctests.



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

- `3902 <https://github.com/pytest-dev/pytest/issues/3902>`_: Fix pytest.org links

Links

• PyPI: https://pypi.org/project/pytest
• Changelog: https://pyup.io/changelogs/pytest/
• Homepage: https://docs.pytest.org/en/latest/

Update pytest-cov from 2.5.1 to 2.6.0.

Changelog

2.6.0

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

* Dropped support for Python < 3.4, Pytest < 3.5 and Coverage < 4.4.
* Fixed some documentation formatting. Contributed by Jean Jordaan and Julian.
* Added an example with ``addopts`` in documentation. Contributed by Samuel Giffard in
`195 <https://github.com/pytest-dev/pytest-cov/pull/195>`_.
* Fixed ``TypeError: 'NoneType' object is not iterable`` in certain xdist configurations. Contributed by Jeremy Bowman in
`213 <https://github.com/pytest-dev/pytest-cov/pull/213>`_.
* Added a ``no_cover`` marker and fixture. Fixes
`78 <https://github.com/pytest-dev/pytest-cov/issues/78>`_.
* Fixed broken ``no_cover`` check when running doctests. Contributed by Terence Honles in
`200 <https://github.com/pytest-dev/pytest-cov/pull/200>`_.
* Fixed various issues with path normalization in reports (when combining coverage data from parallel mode). Fixes
`130 <https://github.com/pytest-dev/pytest-cov/issues/161>`_.
Contributed by Ryan Hiebert & Ionel Cristian Mărieș in
`178 <https://github.com/pytest-dev/pytest-cov/pull/178>`_.
* Report generation failures don't raise exceptions anymore. A warning will be logged instead. Fixes
`161 <https://github.com/pytest-dev/pytest-cov/issues/161>`_.
* Fixed multiprocessing issue on Windows (empty env vars are not passed). Fixes
`165 <https://github.com/pytest-dev/pytest-cov/issues/165>`_.

Links

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

[coveralls]

Coverage remained the same at 91.765% when pulling 5705f2b on pyup-scheduled-update-2018-09-24 into 70871ec on master.