Scheduled weekly dependency update for week 45

[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.

alembic	0.9.5	»	0.9.6	PyPI | Changelog | Repo | Docs
certifi	2017.7.27.1	»	2017.11.5	PyPI | Homepage
filelock	2.0.12	»	2.0.13	PyPI | Repo
newrelic	2.94.0.79	»	2.96.0.80	PyPI | Changelog | Homepage | Bugtracker
oauthlib	2.0.4	»	2.0.6	PyPI | Changelog | Repo
plaster	0.5	»	1.0	PyPI | Changelog | Homepage
psycopg2	2.7.3.1	»	2.7.3.2	PyPI | Changelog | Homepage
raven	6.2.1	»	6.3.0	PyPI | Changelog | Repo
sqlalchemy	1.1.14	»	1.1.15	PyPI | Changelog | Homepage

Changelogs

alembic 0.9.5 -> 0.9.6

0.9.6

:released: October 13, 2017

.. change::
:tags: bug, commands
🎟️ 458

   Fixed a few Python3.6 deprecation warnings by replacing ``StopIteration``
   with ``return``, as well as using ``getfullargspec()`` instead of
   ``getargspec()`` under Python 3.

.. change::
:tags: bug, commands
🎟️ 441

   An addition to :ticket:`441` fixed in 0.9.5, we forgot to also filter
   for the ``+`` sign in migration names which also breaks due to the relative
   migrations feature.

.. change::
:tags: bug, autogenerate
🎟️ 442

   Fixed bug expanding upon the fix for
   :ticket:`85` which adds the correct module import to the
   "inner" type for an ``ARRAY`` type, the fix now accommodates for the
   generic ``sqlalchemy.types.ARRAY`` type added in SQLAlchemy 1.1,
   rendering the inner type correctly regardless of whether or not the
   Postgresql dialect is present.

.. change::
:tags: bug, mysql
🎟️ 455

   Fixed bug where server default comparison of CURRENT_TIMESTAMP would fail
   on MariaDB 10.2 due to a change in how the function is
   represented by the database during reflection.

.. change::
:tags: bug, autogenerate
:pullreq: bitbucket:70

   Fixed bug where comparison of ``Numeric`` types would produce
   a difference if the Python-side ``Numeric`` inadvertently specified
   a non-None "scale" with a "precision" of None, even though this ``Numeric``
   type will pass over the "scale" argument when rendering. Pull request
   courtesy Ivan Mmelnychuk.

.. change::
:tags: feature, commands
🎟️ 447

   The ``alembic history`` command will now make use of the revision
   environment ``env.py`` unconditionally if the ``revision_environment``
   configuration flag is set to True.  Previously, the environment would
   only be invoked if the history specification were against a database-stored
   revision token.

.. change::
:tags: bug, batch
🎟️ 457

   The name of the temporary table in batch mode is now generated
   off of the original table name itself, to avoid conflicts for the
   unusual case of multiple batch operations running against the same
   database schema at the same time.

.. change::
:tags: bug, autogenerate
🎟️ 456

   A :class:`.ForeignKeyConstraint` can now render correctly if the
   ``link_to_name`` flag is set, as it will not attempt to resolve the name
   from a "key" in this case.  Additionally, the constraint will render
   as-is even if the remote column name isn't present on the referenced
   remote table.

.. change::
:tags: bug, runtime, py3k
🎟️ 449

   Reworked "sourceless" system to be fully capable of handling any
   combination of: Python2/3x, pep3149 or not, PYTHONOPTIMIZE or not,
   for locating and loading both env.py files as well as versioning files.
   This includes: locating files inside of ``__pycache__`` as well as listing
   out version files that might be only in ``versions/__pycache__``, deduplicating
   version files that may be in ``versions/__pycache__`` and ``versions/``
   at the same time, correctly looking for .pyc or .pyo files based on
   if pep488 is present or not. The latest Python3x deprecation warnings
   involving importlib are also corrected.

.. changelog::

oauthlib 2.0.4 -> 2.0.6

2.0.5

---

• Fix OAuth2Error.response_mode for 463.
• Documentation improvement.

plaster 0.5 -> 1.0

1.0

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

• Improve the exception message for InvalidURI to show the config_uri.
  See Fix messaging around the InvalidURI exception Pylons/plaster#17

psycopg2 2.7.3.1 -> 2.7.3.2

2.7.3.2

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

• Wheel package compiled against PostgreSQL 10.0 libpq and OpenSSL 1.0.2l
  (:tickets:601, 602)

raven 6.2.1 -> 6.3.0

6.3.0

---

• [Core] Changed default timeout on http calls to 5 seconds
• [Core] Fixed relative paths for traces generated on Windows
• [Django] Fixed import issues for Django projects < 1.7
• [Django] Fixed django management command data option
• [Django/DRF] Added application/octet-stream to non-cacheable types in middleware
• [Django] Added parsing X-Forwarded-For for user.ip_address
• [Flask] Added request.remote_addr as fallback for ip addresses
• [Lambda] Added initial AWS Lambda support with contrib.awslambda.LambdaClient

sqlalchemy 1.1.14 -> 1.1.15

1.1.15

:released: November 3, 2017

.. change:
:tags: bug, sqlite
🎟️ 4099
:versions: 1.2.0b3

   Fixed bug where SQLite CHECK constraint reflection would fail
   if the referenced table were in a remote schema, e.g. on SQLite a
   remote database referred to by ATTACH.

.. change::
:tags: bug, mysql
🎟️ 4097
:versions: 1.2.0b3

   Warning emitted when MariaDB 10.2.8 or earlier in the 10.2
   series is detected as there are major issues with CHECK
   constraints within these versions that were resolved as of
   10.2.9.

   Note that this changelog message was NOT released with
   SQLAlchemy 1.2.0b3 and was added retroactively.

.. change::
:tags: bug, mssql
🎟️ 4095
:versions: 1.2.0b3

   Added a full range of "connection closed" exception codes to the
   PyODBC dialect for SQL Server, including '08S01', '01002', '08003',
   '08007', '08S02', '08001', 'HYT00', 'HY010'.  Previously, only '08S01'
   was covered.

.. change::
:tags: bug, sql
🎟️ 4126
:versions: 1.2.0b4

   Fixed bug where ``__repr__`` of :class:`.ColumnDefault` would fail
   if the argument were a tuple.  Pull request courtesy Nicolas Caniart.

.. change::
:tags: bug, orm, declarative
🎟️ 4124
:versions: 1.2.0b4

   Fixed bug where a descriptor that is elsewhere a mapped column
   or relationship within a hierarchy based on :class:`.AbstractConcreteBase`
   would be referred towards during a refresh operation, causing an error
   as the attribute is not mapped as a mapper property.
   A similar issue can arise for other attributes like the "type" column
   added by :class:`.AbstractConcreteBase` if the class fails to include
   "concrete=True" in its mapper, however the check here should also
   prevent that scenario from causing a problem.

.. change:: 4006
:tags: bug, postgresql
🎟️ 4006
:versions: 1.2.0b3

   Made further fixes to the :class:`.ARRAY` class in conjunction with
   COLLATE, as the fix made in :ticket:`4006` failed to accommodate
   for a multidimensional array.

.. change::
:tags: bug, orm, ext
🎟️ 4116
:versions: 1.2.0b4

   Fixed bug where the association proxy would inadvertently link itself
   to an :class:`.AliasedClass` object if it were called first with
   the :class:`.AliasedClass` as a parent, causing errors upon subsequent
   usage.

.. change::
:tags: bug, mysql
🎟️ 4120
:versions: 1.2.0b4

   MySQL 5.7.20 now warns for use of the tx_isolation variable; a version
   check is now performed and uses transaction_isolation instead
   to prevent this warning.

.. change::
:tags: bug, postgresql
🎟️ 4107
:versions: 1.2.0b3

   Fixed bug in :obj:`.array_agg` function where passing an argument
   that is already of type :class:`.ARRAY`, such as a Postgresql
   :obj:`.postgresql.array` construct, would produce a ``ValueError``, due
   to the function attempting to nest the arrays.

.. change::
:tags: bug, orm
🎟️ 4078
:versions: 1.2.0b3

   Fixed bug where ORM relationship would warn against conflicting sync
   targets (e.g. two relationships would both write to the same column) for
   sibling classes in an inheritance hierarchy, where the two relationships
   would never actually conflict during writes.

.. change::
:tags: bug, postgresql
🎟️ 4074
:versions: 1.2.0b3

   Fixed bug in Postgresql :meth:`.postgresql.dml.Insert.on_conflict_do_update`
   which would prevent the insert statement from being used as a CTE,
   e.g. via :meth:`.Insert.cte`, within another statement.

.. change::
:tags: bug, orm
🎟️ 4103
:versions: 1.2.0b3

   Fixed bug where correlated select used against single-table inheritance
   entity would fail to render correctly in the outer query, due to adjustment
   for single inheritance discriminator criteria inappropriately re-applying
   the criteria to the outer query.

.. change:
:tags: bug, mysql
🎟️ 4096
:versions: 1.2.0b3

   Fixed issue where CURRENT_TIMESTAMP would not reflect correctly
   in the MariaDB 10.2 series due to a syntax change, where the function
   is now represented as ``current_timestamp()``.

.. change:
:tags: bug, mysql
🎟️ 4098
:versions: 1.2.0b3

   MariaDB 10.2 now supports CHECK constraints (warning: use version 10.2.9
   or greater due to upstream issues noted in :ticket:`4097`).  Reflection
   now takes these CHECK constraints into account when they are present in
   the ``SHOW CREATE TABLE`` output.

.. change::
:tags: bug, sql
🎟️ 4093
:versions: 1.2.0b3

   Fixed bug where the recently added :meth:`.ColumnOperators.any_`
   and :meth:`.ColumnOperators.all_` methods didn't work when called
   as methods, as opposed to using the standalone functions
   :func:`~.expression.any_` and :func:`~.expression.all_`.  Also
   added documentation examples for these relatively unintuitive
   SQL operators.

.. changelog::

That's it for now!

Happy merging! 🤖