Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Scheduled weekly dependency update for week 26 #3378

Merged
merged 9 commits into from Jun 27, 2017

Conversation

pyup-bot
Copy link
Collaborator

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.

autobahn 17.6.1 » 17.6.2 PyPI | Changelog | Homepage
botocore 1.5.70 » 1.5.75 PyPI | Changelog | Repo
pbr 3.0.1 » 3.1.1 PyPI | Changelog | Homepage
PyJWT 1.5.0 » 1.5.2 PyPI | Changelog | Repo
pylint 1.7.1 » 1.7.2 PyPI | Changelog | Repo
SQLAlchemy 1.1.10 » 1.1.11 PyPI | Changelog | Homepage

Changelogs

autobahn 17.6.1 -> 17.6.2

17.6.2


Published 2017-06-24 <https://pypi.python.org/pypi/autobahn/17.6.2>__

  • new: force register option when joining realms
  • fix: TLS options in components API

botocore 1.5.70 -> 1.5.75

1.5.75

======

  • api-change:lambda: Update lambda client to latest version

1.5.74

======

  • api-change:lightsail: Update lightsail client to latest version
  • api-change:route53: Update route53 client to latest version
  • api-change:codepipeline: Update codepipeline client to latest version
  • api-change:dms: Update dms client to latest version

1.5.73

======

  • api-change:dax: Update dax client to latest version
  • api-change:waf: Update waf client to latest version
  • api-change:ssm: Update ssm client to latest version
  • api-change:route53: Update route53 client to latest version
  • api-change:waf-regional: Update waf-regional client to latest version

1.5.72

======

  • api-change:workdocs: Update workdocs client to latest version

1.5.71

======

  • enhancement:s3: All S3 requests will now use SigV4 by default so that we can take advantage of stronger security algorithms and improved access key isolation.
  • api-change:organizations: Update organizations client to latest version

pbr 3.0.1 -> 3.1.1

3.1.0

  • allow user to override the output location of api docs
  • fix tests based on API change in Sphinx
  • Updated from global requirements
  • Add binding option for WSGI server
  • Ignore index URL lines in requirements.txt files

PyJWT 1.5.0 -> 1.5.2

1.5.2

1.5.01.5.0


Changed

  • Add support for ECDSA public keys in RFC 4253 (OpenSSH) format 244
  • Renamed commandline script jwt to jwt-cli to avoid issues with the script clobbering the jwt module in some circumstances. 187
  • Better error messages when using an algorithm that requires the cryptography package, but it isn't available 230
  • Tokens with future 'iat' values are no longer rejected 190
  • Non-numeric 'iat' values now raise InvalidIssuedAtError instead of DecodeError
  • Remove rejection of future 'iat' claims 252

Fixed

  • Add back 'ES512' for backward compatibility (for now) 225
  • Fix incorrectly named ECDSA algorithm 219
  • Fix rpm build 196

Added

  • Add JWK support for HMAC and RSA keys 202

1.5.1

SQLAlchemy 1.1.10 -> 1.1.11

1.1.11

:released: Monday, June 19, 2017

.. change:: 4012
:tags: bug, sql
🎟️ 4012
:versions: 1.2.0b1

   Fixed AttributeError which would occur in :class:`.WithinGroup`
   construct during an iteration of the structure.

.. change:: 4011
:tags: bug, orm
🎟️ 4011
:versions: 1.2.0b1

   Fixed issue with subquery eagerloading which continues on from
   the series of issues fixed in :ticket:`2699`, :ticket:`3106`,
   :ticket:`3893` involving that the "subquery" contains the correct
   FROM clause when beginning from a joined inheritance subclass
   and then subquery eager loading onto a relationship from
   the base class, while the query also includes criteria against
   the subclass. The fix in the previous tickets did not accommodate
   for additional subqueryload operations loading more deeply from
   the first level, so the fix has been further generalized.

.. change:: 4005
:tags: bug, postgresql
🎟️ 4005
:versions: 1.2.0b1

   Continuing with the fix that correctly handles Postgresql
   version string "10devel" released in 1.1.8, an additional regexp
   bump to handle version strings of the form "10beta1".   While
   Postgresql now offers better ways to get this information, we
   are sticking w/ the regexp at least through 1.1.x for the least
   amount of risk to compatibility w/ older or alternate Postgresql
   databases.

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

   Fixed bug where using :class:`.ARRAY` with a string type that
   features a collation would fail to produce the correct syntax
   within CREATE TABLE.

.. change:: 4007
:tags: bug, mysql
🎟️ 4007
:versions: 1.2.0b1

   MySQL 5.7 has introduced permission limiting for the "SHOW VARIABLES"
   command; the MySQL dialect will now handle when SHOW returns no
   row, in particular for the initial fetch of SQL_MODE, and will
   emit a warning that user permissions should be modified to allow the
   row to be present.

.. change:: 3994
:tags: bug, mssql
🎟️ 3994
:versions: 1.2.0b1

   Fixed bug where SQL Server transaction isolation must be fetched
   from a different view when using Azure data warehouse, the query
   is now attempted against both views and then a NotImplemented
   is raised unconditionally if failure continues to provide the
   best resiliency against future arbitrary API changes in new
   SQL Server versions.

.. change:: 3997
:tags: bug, oracle
🎟️ 3997
:versions: 1.2.0b1

   Support for two-phase transactions has been removed entirely for
   cx_Oracle when version 6.0b1 or later of the DBAPI is in use.  The two-
   phase feature historically has never been usable under cx_Oracle 5.x in
   any case, and cx_Oracle 6.x has removed the connection-level "twophase"
   flag upon which this feature relied.

.. change:: 3973
:tags: bug, mssql
🎟️ 3973
:versions: 1.2.0b1

   Added a placeholder type :class:`.mssql.XML` to the SQL Server
   dialect, so that a reflected table which includes this type can
   be re-rendered as a CREATE TABLE.  The type has no special round-trip
   behavior nor does it currently support additional qualifying
   arguments.

.. changelog::

That's it for now!

Happy merging! 🤖

@mention-bot
Copy link

@pyup-bot, thanks for your PR! By analyzing the history of the files in this pull request, we identified @tardyp and @rodrigc to be potential reviewers.

@codecov
Copy link

codecov bot commented Jun 26, 2017

Codecov Report

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

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #3378   +/-   ##
=======================================
  Coverage   88.27%   88.27%           
=======================================
  Files         323      323           
  Lines       33578    33578           
=======================================
  Hits        29640    29640           
  Misses       3938     3938

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 7f8134a...cb8d352. Read the comment docs.

@tardyp tardyp merged commit b44c4e8 into master Jun 27, 2017
@tardyp tardyp deleted the pyup-scheduled-update-06-26-2017 branch July 22, 2017 19:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants