Scheduled weekly dependency update for week 35

[pyup-bot]

Update beautifultable from 0.7.0 to 0.8.0.

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

Links

• PyPI: https://pypi.org/project/beautifultable
• Repo: https://github.com/pri22296/beautifultable/tarball/0.8.0

Update SQLAlchemy from 1.3.7 to 1.3.8.

Changelog

1.3.8

:released: August 27, 2019

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

     Fixed bug where :class:`.Load` objects were not pickleable due to
     mapper/relationship state in the internal context dictionary.  These
     objects are now converted to picklable using similar techniques as that of
     other elements within the loader option system that have long been
     serializable.

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

     Revised the approach for the just added support for the psycopg2
     "execute_values()" feature added in 1.3.7 for :ticket:`4623`.  The approach
     relied upon a regular expression that would fail to match for a more
     complex INSERT statement such as one which had subqueries involved.   The
     new approach matches exactly the string that was rendered as the VALUES
     clause.

 .. change::
     :tags: usecase, orm
     :tickets: 4285

     Added support for the use of an :class:`.Enum` datatype using Python
     pep-435 enumeration objects as values for use as a primary key column
     mapped by the ORM.  As these values are not inherently sortable, as
     required by the ORM for primary keys, a new
     :attr:`.TypeEngine.sort_key_function` attribute is added to the typing
     system which allows any SQL type to  implement a sorting for Python objects
     of its type which is consulted by the unit of work.   The :class:`.Enum`
     type then defines this using the  database value of a given enumeration.
     The sorting scheme can be  also be redefined by passing a callable to the
     :paramref:`.Enum.sort_key_function` parameter.  Pull request courtesy
     Nicolas Caniart.

 .. change::
     :tags: bug, engine
     :tickets: 4807

     Fixed an issue whereby if the dialect "initialize" process which occurs on
     first connect would encounter an unexpected exception, the initialize
     process would fail to complete and then no longer attempt on subsequent
     connection attempts, leaving the dialect in an un-initialized, or partially
     initialized state, within the scope of parameters that need to be
     established based on inspection of a live connection.   The "invoke once"
     logic in the event system has been reworked to accommodate for this
     occurrence using new, private API features that establish an "exec once"
     hook that will continue to allow the initializer to fire off on subsequent
     connections, until it completes without raising an exception. This does not
     impact the behavior of the existing ``once=True`` flag within the event
     system.

 .. change::
     :tags: bug, sqlite, reflection
     :tickets: 4810

     Fixed bug where a FOREIGN KEY that was set up to refer to the parent table
     by table name only without the column names would not correctly be
     reflected as far as setting up the "referred columns", since SQLite's
     PRAGMA does not report on these columns if they weren't given explicitly.
     For some reason this was harcoded to assume the name of the local column,
     which might work for some cases but is not correct. The new approach
     reflects the primary key of the referred table and uses the constraint
     columns list as the referred columns list, if the remote column(s) aren't
     present in the reflected pragma directly.


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

     Fixed bug where Postgresql operators such as
     :meth:`.postgresql.ARRAY.Comparator.contains` and
     :meth:`.postgresql.ARRAY.Comparator.contained_by` would fail to function
     correctly for non-integer values when used against a
     :class:`.postgresql.array` object, due to an erroneous assert statement.

 .. change::
     :tags: feature, engine
     :tickets: 4815

     Added new parameter :paramref:`.create_engine.hide_parameters` which when
     set to True will cause SQL parameters to no longer be logged, nor rendered
     in the string representation of a :class:`.StatementError` object.


 .. change::
     :tags: usecase, postgresql
     :tickets: 4824

     Added support for reflection of CHECK constraints that include the special
     PostgreSQL qualifier "NOT VALID", which can be present for CHECK
     constraints that were added to an exsiting table with the directive that
     they not be applied to existing data in the table. The PostgreSQL
     dictionary for CHECK constraints as returned by
     :meth:`.Inspector.get_check_constraints` may include an additional entry
     ``dialect_options`` which within will contain an entry ``"not_valid":
     True`` if this symbol is detected.   Pull request courtesy Bill Finn.

.. changelog::

Links

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

Update alembic from 1.0.11 to 1.1.0.

Changelog

1.1.0

:released: August 26, 2019

 .. change::
     :tags: change

     Alembic 1.1 bumps the minimum version of SQLAlchemy to 1.1.   As was the
     case before, Python requirements remain at Python 2.7, or in the 3.x series
     Python 3.4.

 .. change::
     :tags: change, internals

     The test suite for Alembic now makes use of SQLAlchemy's testing framework
     directly.  Previously, Alembic had its own version of this framework that
     was mostly copied from that of SQLAlchemy to enable testing with older
     SQLAlchemy versions.  The majority of this code is now removed so that both
     projects can leverage improvements from a common testing framework.

 .. change::
     :tags: bug, commands
     :tickets: 562

     Fixed bug where the double-percent logic applied to some dialects such as
     psycopg2 would be rendered in ``--sql`` mode, by allowing dialect options
     to be passed through to the dialect used to generate SQL and then providing
     ``paramstyle="named"`` so that percent signs need not be doubled.   For
     users having this issue, existing env.py scripts need to add
     ``dialect_opts={"paramstyle": "named"}`` to their offline
     context.configure().  See the ``alembic/templates/generic/env.py`` template
     for an example.

 .. change::
     :tags: bug, py3k

     Fixed use of the deprecated "imp" module, which is used to detect  pep3147
     availability as well as to locate .pyc files, which started  emitting
     deprecation warnings during the test suite.   The warnings were not being
     emitted earlier during the test suite, the change is possibly due to
     changes in py.test itself but this is not clear. The check for pep3147 is
     set to True for any Python version 3.5 or greater now and importlib is used
     when available.  Note that some dependencies such as distutils may still be
     emitting this warning. Tests are adjusted to accommodate for dependencies
     that emit the warning as well.


 .. change::
     :tags: bug, mysql
     :tickets: 594

     Fixed issue where emitting a change of column name for MySQL did not
     preserve the column comment, even if it were specified as existing_comment.


 .. change::
     :tags: bug, setup
     :tickets: 592

     Removed the "python setup.py test" feature in favor of a straight run of
     "tox".   Per Pypa / pytest developers, "setup.py" commands are in general
     headed towards deprecation in favor of tox.  The tox.ini script has been
     updated such that running "tox" with no arguments will perform a single run
     of the test suite against the default installed Python interpreter.

     .. seealso::

         https://github.com/pypa/setuptools/issues/1684

         https://github.com/pytest-dev/pytest/issues/5534

 .. change::
     :tags: usecase, commands
     :tickets: 571

     The "alembic init" command will now proceed if the target directory exists
     as long as it's still empty.  Previously, it would not proceed if the
     directory existed. The new behavior is modeled from what git does, to
     accommodate for container or other deployments where an Alembic target
     directory may need to be already mounted instead of being created with
     alembic init.  Pull request courtesy Aviskar KC.



.. changelog::

Links

• PyPI: https://pypi.org/project/alembic
• Changelog: https://pyup.io/changelogs/alembic/
• Homepage: https://alembic.sqlalchemy.org
• Docs: https://pythonhosted.org/alembic/

Update pytest from 4.6.3 to 4.6.5.

Changelog

4.6.5

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

Bug Fixes
---------

- `4344 <https://github.com/pytest-dev/pytest/issues/4344>`_: Fix RuntimeError/StopIteration when trying to collect package with "__init__.py" only.


- `5478 <https://github.com/pytest-dev/pytest/issues/5478>`_: Fix encode error when using unicode strings in exceptions with ``pytest.raises``.


- `5524 <https://github.com/pytest-dev/pytest/issues/5524>`_: Fix issue where ``tmp_path`` and ``tmpdir`` would not remove directories containing files marked as read-only,
which could lead to pytest crashing when executed a second time with the ``--basetemp`` option.


- `5547 <https://github.com/pytest-dev/pytest/issues/5547>`_: ``--step-wise`` now handles ``xfail(strict=True)`` markers properly.


- `5650 <https://github.com/pytest-dev/pytest/issues/5650>`_: Improved output when parsing an ini configuration file fails.

4.6.4

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

Bug Fixes
---------

- `5404 <https://github.com/pytest-dev/pytest/issues/5404>`_: Emit a warning when attempting to unwrap a broken object raises an exception,
for easier debugging (`5080 <https://github.com/pytest-dev/pytest/issues/5080>`__).


- `5444 <https://github.com/pytest-dev/pytest/issues/5444>`_: Fix ``--stepwise`` mode when the first file passed on the command-line fails to collect.


- `5482 <https://github.com/pytest-dev/pytest/issues/5482>`_: Fix bug introduced in 4.6.0 causing collection errors when passing
more than 2 positional arguments to ``pytest.mark.parametrize``.


- `5505 <https://github.com/pytest-dev/pytest/issues/5505>`_: Fix crash when discovery fails while using ``-p no:terminal``.

Links

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

Update setuptools from 41.1.0 to 41.2.0.

Changelog

41.2.0

-------

* 479: Remove some usage of the deprecated ``imp`` module.
* 1565: Changed html_sidebars from string to list of string as per
https://www.sphinx-doc.org/en/master/changes.htmlid58

Links

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

[coveralls]

Coverage remained the same at 100.0% when pulling aae16fd on pyup-scheduled-update-2019-09-02 into e8798ad on master.

[pyup-bot]

Closing this in favor of #255