Skip to content
This repository was archived by the owner on Dec 17, 2019. It is now read-only.

Scheduled monthly dependency update for December#42

Closed
pyup-bot wants to merge 8 commits intodevelopfrom
pyup-scheduled-update-12-01-2017
Closed

Scheduled monthly dependency update for December#42
pyup-bot wants to merge 8 commits intodevelopfrom
pyup-scheduled-update-12-01-2017

Conversation

@pyup-bot
Copy link
Copy Markdown
Contributor

@pyup-bot pyup-bot commented Dec 1, 2017

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.

Flask-SQLAlchemy 2.3.0 » 2.3.2 PyPI | Changelog | Repo | Docs
Jinja2 2.9.6 » 2.10 PyPI | Homepage
SQLAlchemy 1.1.14 » 1.1.15 PyPI | Changelog | Homepage
coverage 4.4.1 » 4.4.2 PyPI | Changelog | Repo
paramiko 2.3.1 » 2.4.0 PyPI | Changelog | Repo
bcrypt 3.1.3 » 3.1.4 PyPI | Repo
pytz 2017.2 » 2017.3 PyPI | Homepage | Docs
tzlocal 1.4 » 1.5.1 PyPI | Changelog | Repo

Changelogs

Flask-SQLAlchemy 2.3.0 -> 2.3.2

2.3.2


Released on October 11, 2017

  • Don't mask the parent table for single-table inheritance models. (561_)

.. _561: pallets-eco/flask-sqlalchemy#561

2.3.1


Released on October 5, 2017

  • If a model has a table name that matches an existing table in the metadata,
    use that table. Fixes a regression where reflected tables were not picked up
    by models. (551_)
  • Raise the correct error when a model has a table name but no primary key.
    (556_)
  • Fix repr on models that don't have an identity because they have not been
    flushed yet. (555_)
  • Allow specifying a max_per_page limit for pagination, to avoid users
    specifying high values in the request args. (542_)
  • For paginate with error_out=False, the minimum value for page is
    1 and per_page is 0. (558_)

.. _542: pallets-eco/flask-sqlalchemy#542
.. _551: pallets-eco/flask-sqlalchemy#551
.. _555: pallets-eco/flask-sqlalchemy#555
.. _556: pallets-eco/flask-sqlalchemy#556
.. _558: pallets-eco/flask-sqlalchemy#558

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::

coverage 4.4.1 -> 4.4.2

4.4.2


  • Support for Python 3.7. In some cases, class and module docstrings are no
    longer counted in statement totals, which could slightly change your total
    results.
  • Specifying both --source and --include no longer silently ignores the
    include setting, instead it displays a warning. Thanks, Loïc Dachary. Closes
    issue 265_ and issue 101_.
  • Fixed a race condition when saving data and multiple threads are tracing
    (issue 581_). It could produce a "dictionary changed size during iteration"
    RuntimeError. I believe this mostly but not entirely fixes the race
    condition. A true fix would likely be too expensive. Thanks, Peter Baughman
    for the debugging, and Olivier Grisel for the fix with tests.
  • Configuration values which are file paths will now apply tilde-expansion,
    closing issue 589_.
  • Now secondary config files like tox.ini and setup.cfg can be specified
    explicitly, and prefixed sections like [coverage:run] will be read. Fixes
    issue 588_.
  • Be more flexible about the command name displayed by help, fixing
    issue 600_. Thanks, Ben Finney.

.. _issue 101: https://bitbucket.org/ned/coveragepy/issues/101/settings-under-report-affect-running
.. _issue 581: https://bitbucket.org/ned/coveragepy/issues/581/race-condition-when-saving-data-under
.. _issue 588: https://bitbucket.org/ned/coveragepy/issues/588/using-rcfile-path-to-toxini-uses-run
.. _issue 589: https://bitbucket.org/ned/coveragepy/issues/589/allow-expansion-in-coveragerc
.. _issue 600: https://bitbucket.org/ned/coveragepy/issues/600/get-program-name-from-command-line-when

.. _changes_441:

tzlocal 1.4 -> 1.5.1

1.5.1


  • 1.5 had a bug that slipped through testing, fixed that,
    increased test coverage.

1.5


  • No longer treats macOS as special, but as a unix.
  • get_windows_info.py is renamed to update_windows_mappings.py
  • Windows mappings now also contain mappings from deprecated zoneinfo names.
    (Preston-Landers, regebro)

That's it for now!

Happy merging! 🤖

@pyup-bot
Copy link
Copy Markdown
Contributor Author

pyup-bot commented Jan 1, 2018

Closing this in favor of #43

@pyup-bot pyup-bot closed this Jan 1, 2018
@b-reich b-reich deleted the pyup-scheduled-update-12-01-2017 branch January 1, 2018 15:07
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant