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 monthly dependency update for July #97

Closed
wants to merge 110 commits into from

Conversation

pyup-bot
Copy link
Contributor

@pyup-bot pyup-bot commented Jul 1, 2019

Update adal from 1.0.2 to 1.2.1.

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

Links

Update azure-batch from 4.1.3 to 7.0.0.

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

Links

Update azure-common from 1.1.14 to 1.1.23.

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

Links

Update azure-datalake-store from 0.0.25 to 0.0.46.

Changelog

0.0.46

+++++++++++++++++++
* Expose per request timeout. Default to 60.
* Concat will not retry by default.
* Bug fixes.

0.0.45

+++++++++++++++++++
* Update open and close ADLFile semantics
* Refactor code and improve performance for opening a file

0.0.44

+++++++++++++++++++
* Add continuation token to LISTSTATUS api call
* Update api-version to 2018-09-01

0.0.43

+++++++++++++++++++
* Fix bug in downloader when glob returns a single file

0.0.42

+++++++++++++++++++
* Update docstrings
* Remove logging setlevel to DEBUG for recursive acl operations

0.0.41

+++++++++++++++++++
* Remove GetContentSummary api call
* Move check_token() under retry block
* Expose timeout parameter for AdlDownloader and AdlUploader
* Raise an exception instead of silently break for zero length reads

0.0.40

+++++++++++++++++++
* Fix zero length read
* Remove dependence on custom wheel and conform to PEP 420

0.0.39

+++++++++++++++++++
* Fix for Chunked Decoding exception thrown while reading response.content

0.0.38

+++++++++++++++++++
* Added support for recursive acl functions
* Fixed bug due to missing filesessionid in get_chunk

0.0.37

+++++++++++++++++++
* Reverted some changes introduced in 0.0.35 that didn't work with other tokens

0.0.36

+++++++++++++++++++
* Fixed typo in refresh_token call

0.0.35

+++++++++++++++++++
* Added retry for getting tokens
* Added requests>=2.20 because of CVE 2018-18074
* Fixed test parameters and updated test recordings

0.0.34

+++++++++++++++++++
* Fixed concat issue with plus(or other symbols) in filename
* Added readinto method
* Changed api-version to 2018-05-01 for all.

0.0.32

+++++++++++++++++++
* Fixed test bug
* Fixed empty folder upload bug
* Fixed ADL Downloader block size bug

0.0.31

+++++++++++++++++++
* Added support for batched ls

0.0.30

+++++++++++++++++++
* Fixed .travis.yml order to add azure-nspg dependency

0.0.29

+++++++++++++++++++
* Fixed HISTORY.rst and Pypi documentation

0.0.28

+++++++++++++++++++
* Added recovery from DatalakeBadOffsetException

0.0.27

+++++++++++++++++++
* Fixed bug in single file check
* Added Python2 exception compatibility

0.0.26

+++++++++++++++++++
* Fixed bug due to not importing errno
* Fixed bug in os.makedirs race condition
* Updated Readme with correct environment variables and fixed some links
Links

Update azure-eventgrid from 1.1.0 to 1.3.0.

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

Links

Update azure-graphrbac from 0.40.0 to 0.61.1.

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

Links

Update azure-keyvault from 1.0.0 to 1.1.0.

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

Links

Update azure-mgmt-advisor from 1.0.1 to 2.0.1.

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

Links

Update azure-mgmt-applicationinsights from 0.1.1 to 0.2.0.

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

Links

Update azure-mgmt-authorization from 0.50.0 to 0.60.0.

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

Links

Update azure-mgmt-batch from 5.0.1 to 6.0.0.

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

Links

Update azure-mgmt-cdn from 3.0.0 to 3.1.0.

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

Links

Update azure-mgmt-cognitiveservices from 3.0.0 to 5.0.0.

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

Links

Update azure-mgmt-compute from 4.0.1 to 5.0.0.

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

Links

Update azure-mgmt-consumption from 2.0.0 to 3.0.0.

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

Links

Update azure-mgmt-containerinstance from 1.0.0 to 1.5.0.

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

Links

Update azure-mgmt-containerregistry from 2.1.0 to 2.8.0.

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

Links

Update azure-mgmt-containerservice from 4.2.0 to 5.3.0.

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

Links

Update azure-mgmt-cosmosdb from 0.4.1 to 0.7.0.

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

Links

Update azure-mgmt-datafactory from 0.6.0 to 0.7.0.

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

Links

Update azure-mgmt-datalake-nspkg from 2.0.0 to 3.0.1.

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

Links

Update azure-mgmt-devtestlabs from 2.2.0 to 3.0.0.

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

Links

Update azure-mgmt-dns from 1.2.0 to 3.0.0.

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

Links

Update azure-mgmt-eventgrid from 1.0.0 to 2.2.0.

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

Links

Update azure-mgmt-eventhub from 2.1.0 to 3.0.0.

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

Links

Update azure-mgmt-hanaonazure from 0.1.1 to 0.8.0.

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

Links

Update azure-mgmt-iothub from 0.5.0 to 0.8.2.

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

Links

Update azure-mgmt-keyvault from 1.0.0 to 2.0.0.

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

Links

Update azure-mgmt-managementpartner from 0.1.0 to 0.1.1.

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

Links

Update azure-mgmt-marketplaceordering from 0.1.0 to 0.2.1.

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

Links

Update azure-mgmt-media from 0.2.0 to 1.1.1.

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

Links

Update azure-mgmt-monitor from 0.5.2 to 0.7.0.

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

Links

Update azure-mgmt-msi from 0.2.0 to 1.0.0.

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

Links

Update azure-mgmt-network from 2.0.0 to 3.0.0.

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

Links

Update azure-mgmt-notificationhubs from 2.0.0 to 2.1.0.

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

Links

Update azure-mgmt-nspkg from 2.0.0 to 3.0.2.

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

Links

Update azure-mgmt-rdbms from 1.2.0 to 1.9.0.

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

Links

Update azure-mgmt-recoveryservicesbackup from 0.3.0 to 0.4.0.

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

Links

Update azure-mgmt-redis from 5.0.0 to 6.0.0.

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

Links

Update azure-mgmt-relay from 0.1.0 to 0.2.0.

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

Links

Update azure-mgmt-reservations from 0.2.1 to 0.3.2.

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

Links

Update azure-mgmt-resource from 2.0.0 to 3.0.0.

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

Links

Update azure-mgmt-search from 2.0.0 to 2.1.0.

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

Links

Update azure-mgmt-servicebus from 0.5.1 to 0.6.0.

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

Links

Update azure-mgmt-servicefabric from 0.1.0 to 0.3.0.

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

Links

Update azure-mgmt-sql from 0.9.1 to 0.12.0.

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

Links

Update azure-mgmt-storage from 1.5.0 to 4.0.0.

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

Links

Update azure-mgmt-subscription from 0.2.0 to 0.4.1.

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

Links

Update azure-mgmt-trafficmanager from 0.50.0 to 0.51.0.

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

Links

Update azure-mgmt-web from 0.35.0 to 0.42.0.

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

Links

Update azure-mgmt from 2.0.0 to 4.0.0.

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

Links

Update azure-nspkg from 2.0.0 to 3.0.2.

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

Links

Update azure-servicebus from 0.21.1 to 0.50.1.

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

Links

Update azure-servicefabric from 6.3.0.0 to 6.5.0.0.

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

Links

Update azure-storage-blob from 1.3.1 to 2.0.1.

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

Links

Update azure-storage-common from 1.1.0 to 2.0.0.

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

Links

Update azure-storage-file from 1.3.1 to 2.0.1.

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

Links

Update azure-storage-nspkg from 3.0.0 to 3.1.0.

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

Links

Update azure-storage-queue from 1.1.0 to 2.0.1.

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

Links

Update azure from 3.0.0 to 4.0.0.

Changelog

4.0.0

azure-mgmt_4.0.0


azure-mgmt-dns_2.0.0


azure-mgmt-servicefabric_0.2.0


azure-mgmt-storage_2.0.0


azure-mgmt-eventhub_2.1.0


azure-servicefabric_6.3.0.0


azure-mgmt-containerservice_4.2.0


azure-mgmt-network_2.0.0


azure-mgmt-containerregistry_2.1.0


azure-mgmt-compute_4.0.1


azure-mgmt-compute_4.0.0


azure-mgmt-resource_2.0.0


azure-cognitiveservices-search-autosuggest_0.1.0


azure-mgmt-media_1.0.0rc2


azure-mgmt-iotcentral_0.1.0


azure-common_1.1.14


azure-applicationinsights_0.1.0


azure-mgmt-devspaces_0.1.0


azure-cognitiveservices-vision-customvision_0.3.0


azure-loganalytics_0.1.0


azure-mgmt-servicebus_0.5.1


azure-common_1.1.13


azure-mgmt-keyvault_1.0.0
* Moving azure-mgmt-keyvault to API version 2018-02-14
* Adding network_acls vault property for limiting network access to a vault
* Adding managed storage account key backup, restore and soft delete support
* Adding vault property enable_purge_protection for enhance protection against vault deletion
* Breaking change in vault create_or_update now returns a 'LROPoller' objects rather than the Vault, to
allow callers to determine when the vault is ready to accept traffic. Callers should use the result() method
to block until the vault is accessible.
* Upgraded to autorest 3.0 generated code

**General Breaking changes**

This version uses a next-generation code generator that *might* introduce breaking changes.

- Model signatures now use only keyword-argument syntax. All positional arguments must be re-written as keyword-arguments.
To keep auto-completion in most cases, models are now generated for Python 2 and Python 3. Python 3 uses the "*" syntax for keyword-only arguments.
- Enum types now use the "str" mixin (class AzureEnum(str, Enum)) to improve the behavior when unrecognized enum values are encountered.
While this is not a breaking change, the distinctions are important, and are documented here:
https://docs.python.org/3/library/enum.htmlothers
At a glance:

- "is" should not be used at all.
- "format" will return the string value, where "%s" string formatting will return `NameOfEnum.stringvalue`. Format syntax should be prefered.

- New Long Running Operation:

- Return type changes from `msrestazure.azure_operation.AzureOperationPoller` to `msrest.polling.LROPoller`. External API is the same.
- Return type is now **always** a `msrest.polling.LROPoller`, regardless of the optional parameters used.
- The behavior has changed when using `raw=True`. Instead of returning the initial call result as `ClientRawResponse`,
 without polling, now this returns an LROPoller. After polling, the final resource will be returned as a `ClientRawResponse`.
- New `polling` parameter. The default behavior is `Polling=True` which will poll using ARM algorithm. When `Polling=False`,
 the response of the initial call will be returned without polling.
- `polling` parameter accepts instances of subclasses of `msrest.polling.PollingMethod`.
- `add_done_callback` will no longer raise if called after polling is finished, but will instead execute the callback right away.

azure-keyvault_1.0.0
Links

Update babel from 2.6.0 to 2.7.0.

Changelog

2.7.0

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

Possibly incompatible changes
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

These may be backward incompatible in some cases, as some more-or-less internal
APIs have changed. Please feel free to file issues if you bump into anything
strange and we'll try to help!

* General: Internal uses of ``babel.util.odict`` have been replaced with
``collections.OrderedDict`` from The Python standard library.

Improvements
~~~~~~~~~~~~

* CLDR: Upgrade to CLDR 35.1 - Alberto Mardegan, Aarni Koskela (626, 643)
* General: allow anchoring path patterns to the start of a string - Brian Cappello (600)
* General: Bumped version requirement on pytz - chrisbrake (592)
* Messages: `pybabel compile`: exit with code 1 if errors were encountered - Aarni Koskela (647)
* Messages: Add omit-header to update_catalog - Cédric Krier (633)
* Messages: Catalog update: keep user comments from destination by default - Aarni Koskela (648)
* Messages: Skip empty message when writing mo file - Cédric Krier (564)
* Messages: Small fixes to avoid crashes on badly formatted .po files - Bryn Truscott (597)
* Numbers: `parse_decimal()` `strict` argument and `suggestions` - Charly C (590)
* Numbers: don't repeat suggestions in parse_decimal strict - Serban Constantin (599)
* Numbers: implement currency formatting with long display names - Luke Plant (585)
* Numbers: parse_decimal(): assume spaces are equivalent to non-breaking spaces when not in strict mode - Aarni Koskela (649)
* Performance: Cache locale_identifiers() - Aarni Koskela (644)

Bugfixes
~~~~~~~~

* CLDR: Skip alt=... for week data (minDays, firstDay, weekendStart, weekendEnd) - Aarni Koskela (634)
* Dates: Fix wrong weeknumber for 31.12.2018 - BT-sschmid (621)
* Locale: Avoid KeyError trying to get data on WindowsXP - mondeja (604)
* Locale: get_display_name(): Don't attempt to concatenate variant information to None - Aarni Koskela (645)
* Messages: pofile: Add comparison operators to _NormalizedString - Aarni Koskela (646)
* Messages: pofile: don't crash when message.locations can't be sorted - Aarni Koskela (646)

Tooling & docs
~~~~~~~~~~~~~~

* Docs: Remove all references to deprecated easy_install - Jon Dufresne (610)
* Docs: Switch print statement in docs to print function - NotAFile
* Docs: Update all pypi.python.org URLs to pypi.org - Jon Dufresne (587)
* Docs: Use https URLs throughout project where available - Jon Dufresne (588)
* Support: Add testing and document support for Python 3.7 - Jon Dufresne (611)
* Support: Test on Python 3.8-dev - Aarni Koskela (642)
* Support: Using ABCs from collections instead of collections.abc is deprecated. - Julien Palard (609)
* Tests: Fix conftest.py compatibility with pytest 4.3 - Miro Hrončok (635)
* Tests: Update pytest and pytest-cov - Miro Hrončok (635)
Links

Update cachetools from 2.1.0 to 3.1.1.

Changelog

3.1.1

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

- Document how to use shared caches with ``cachedmethod``.

- Fix pickling/unpickling of cache keys

3.1.0

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

- Fix Python 3.8 compatibility issue.

- Use ``time.monotonic`` as default timer if available.

- Improve documentation regarding thread safety.

3.0.0

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

- Officially support Python 3.7.

- Drop Python 3.3 support (breaking change).

- Remove ``missing`` cache constructor parameter (breaking change).

- Remove ``self`` from ``cachedmethod`` key arguments (breaking
change).

- Add support for ``maxsize=None`` in ``cachetools.func`` decorators.
Links

Update certifi from 2018.4.16 to 2019.6.16.

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

Links

Update cffi from 1.11.5 to 1.12.3.

Changelog

1.12.3

=======

* Fix for nested struct types that end in a var-sized array (405).

* Add support for using ``U`` and ``L`` characters at the end of integer
constants in ``ffi.cdef()`` (thanks Guillaume).

* More 3.8 fixes.

1.12.2

=======

* Added temporary workaround to compile on CPython 3.8.0a2.

1.12.1

=======

* CPython 3 on Windows: we again no longer compile with ``Py_LIMITED_API``
by default because such modules *still* cannot be used with virtualenv.
The problem is that it doesn't work in CPython <= 3.4, and for
technical reason we can't enable this flag automatically based on the
version of Python.

Like before, `Issue 350`_ mentions a workaround if you still want
the ``Py_LIMITED_API`` flag and *either* you are not concerned about
virtualenv *or* you are sure your module will not be used on CPython
<= 3.4: pass ``define_macros=[("Py_LIMITED_API", None)]`` to the
``ffibuilder.set_source()`` call.

1.12

=====

* `Direct support for pkg-config`__.

* ``ffi.from_buffer()`` takes a new optional *first* argument that gives
the array type of the result.  It also takes an optional keyword argument
``require_writable`` to refuse read-only Python buffers.

* ``ffi.new()``, ``ffi.gc()`` or ``ffi.from_buffer()`` cdata objects
can now be released at known times, either by using the ``with``
keyword or by calling the new ``ffi.release()``.

* Windows, CPython 3.x: cffi modules are linked with ``python3.dll``
again.  This makes them independant on the exact CPython version,
like they are on other platforms.  **It requires virtualenv 16.0.0.**

* Accept an expression like ``ffi.new("int[4]", p)`` if ``p`` is itself
another cdata ``int[4]``.

* CPython 2.x: ``ffi.dlopen()`` failed with non-ascii file names on Posix

* CPython: if a thread is started from C and then runs Python code (with
callbacks or with the embedding solution), then previous versions of
cffi would contain possible crashes and/or memory leaks.  Hopefully,
this has been fixed (see `issue 362`_).

* Support for ``ffi.cdef(..., pack=N)`` where N is a power of two.
Means to emulate ``pragma pack(N)`` on MSVC.  Also, the default on
Windows is now ``pack=8``, like on MSVC.  This might make a difference
in corner cases, although I can't think of one in the context of CFFI.
The old way ``ffi.cdef(..., packed=True)`` remains and is equivalent
to ``pack=1`` (saying e.g. that fields like ``int`` should be aligned
to 1 byte instead of 4).

.. __: cdef.htmlpkgconfig
.. _`issue 362`: https://bitbucket.org/cffi/cffi/issues/362/


Older Versions
==============
Links

Update cryptography from 2.3 to 2.7.

Changelog

2.7

~~~~~~~~~~~~~~~~

* **BACKWARDS INCOMPATIBLE:** We no longer distribute 32-bit ``manylinux1``
wheels. Continuing to produce them was a maintenance burden.
* **BACKWARDS INCOMPATIBLE:** Removed the
``cryptography.hazmat.primitives.mac.MACContext`` interface. The ``CMAC`` and
``HMAC`` APIs have not changed, but they are no longer registered as
``MACContext`` instances.
* Removed support for running our tests with ``setup.py test``. Users
interested in running our tests can continue to follow the directions in our
:doc:`development documentation</development/getting-started>`.
* Add support for :class:`~cryptography.hazmat.primitives.poly1305.Poly1305`
when using OpenSSL 1.1.1 or newer.
* Support serialization with ``Encoding.OpenSSH`` and ``PublicFormat.OpenSSH``
in
:meth:`Ed25519PublicKey.public_bytes
<cryptography.hazmat.primitives.asymmetric.ed25519.Ed25519PublicKey.public_bytes>`
.
* Correctly allow passing a ``SubjectKeyIdentifier`` to
:meth:`~cryptography.x509.AuthorityKeyIdentifier.from_issuer_subject_key_identifier`
and deprecate passing an ``Extension`` object. The documentation always
required ``SubjectKeyIdentifier`` but the implementation previously
required an ``Extension``.

.. _v2-6-1:

2.6.1

~~~~~~~~~~~~~~~~~~

* Resolved an error in our build infrastructure that broke our Python3 wheels
for macOS and Linux.

.. _v2-6:

2.6

~~~~~~~~~~~~~~~~

* **BACKWARDS INCOMPATIBLE:** Removed
``cryptography.hazmat.primitives.asymmetric.utils.encode_rfc6979_signature``
and
``cryptography.hazmat.primitives.asymmetric.utils.decode_rfc6979_signature``,
which had been deprecated for nearly 4 years. Use
:func:`~cryptography.hazmat.primitives.asymmetric.utils.encode_dss_signature`
and
:func:`~cryptography.hazmat.primitives.asymmetric.utils.decode_dss_signature`
instead.
* **BACKWARDS INCOMPATIBLE**: Removed ``cryptography.x509.Certificate.serial``,
which had been deprecated for nearly 3 years. Use
:attr:`~cryptography.x509.Certificate.serial_number` instead.
* Updated Windows, macOS, and ``manylinux1`` wheels to be compiled with
OpenSSL 1.1.1b.
* Added support for :doc:`/hazmat/primitives/asymmetric/ed448` when using
OpenSSL 1.1.1b or newer.
* Added support for :doc:`/hazmat/primitives/asymmetric/ed25519` when using
OpenSSL 1.1.1b or newer.
* :func:`~cryptography.hazmat.primitives.serialization.load_ssh_public_key` can
now load ``ed25519`` public keys.
* Add support for easily mapping an object identifier to its elliptic curve
class via
:func:`~cryptography.hazmat.primitives.asymmetric.ec.get_curve_for_oid`.
* Add support for OpenSSL when compiled with the ``no-engine``
(``OPENSSL_NO_ENGINE``) flag.

.. _v2-5:

2.5

~~~~~~~~~~~~~~~~

* **BACKWARDS INCOMPATIBLE:** :term:`U-label` strings were deprecated in
version 2.1, but this version removes the default ``idna`` dependency as
well. If you still need this deprecated path please install cryptography
with the ``idna`` extra: ``pip install cryptography[idna]``.
* **BACKWARDS INCOMPATIBLE:** The minimum supported PyPy version is now 5.4.
* Numerous classes and functions have been updated to allow :term:`bytes-like`
types for keying material and passwords, including symmetric algorithms, AEAD
ciphers, KDFs, loading asymmetric keys, and one time password classes.
* Updated Windows, macOS, and ``manylinux1`` wheels to be compiled with
OpenSSL 1.1.1a.
* Added support for :class:`~cryptography.hazmat.primitives.hashes.SHA512_224`
and :class:`~cryptography.hazmat.primitives.hashes.SHA512_256` when using
OpenSSL 1.1.1.
* Added support for :class:`~cryptography.hazmat.primitives.hashes.SHA3_224`,
:class:`~cryptography.hazmat.primitives.hashes.SHA3_256`,
:class:`~cryptography.hazmat.primitives.hashes.SHA3_384`, and
:class:`~cryptography.hazmat.primitives.hashes.SHA3_512` when using OpenSSL
1.1.1.
* Added support for :doc:`/hazmat/primitives/asymmetric/x448` when using
OpenSSL 1.1.1.
* Added support for :class:`~cryptography.hazmat.primitives.hashes.SHAKE128`
and :class:`~cryptography.hazmat.primitives.hashes.SHAKE256` when using
OpenSSL 1.1.1.
* Added initial support for parsing PKCS12 files with
:func:`~cryptography.hazmat.primitives.serialization.pkcs12.load_key_and_certificates`.
* Added support for :class:`~cryptography.x509.IssuingDistributionPoint`.
* Added ``rfc4514_string()`` method to
:meth:`x509.Name <cryptography.x509.Name.rfc4514_string>`,
:meth:`x509.RelativeDistinguishedName
<cryptography.x509.RelativeDistinguishedName.rfc4514_string>`, and
:meth:`x509.NameAttribute <cryptography.x509.NameAttribute.rfc4514_string>`
to format the name or component an :rfc:`4514` Distinguished Name string.
* Added
:meth:`~cryptography.hazmat.primitives.asymmetric.ec.EllipticCurvePublicKey.from_encoded_point`,
which immediately checks if the point is on the curve and supports compressed
points. Deprecated the previous method
:meth:`~cryptography.hazmat.primitives.asymmetric.ec.EllipticCurvePublicNumbers.from_encoded_point`.
* Added :attr:`~cryptography.x509.ocsp.OCSPResponse.signature_hash_algorithm`
to ``OCSPResponse``.
* Updated :doc:`/hazmat/primitives/asymmetric/x25519` support to allow
additional serialization methods. Calling
:meth:`~cryptography.hazmat.primitives.asymmetric.x25519.X25519PublicKey.public_bytes`
with no arguments has been deprecated.
* Added support for encoding compressed and uncompressed points via
:meth:`~cryptography.hazmat.primitives.asymmetric.ec.EllipticCurvePublicKey.public_bytes`. Deprecated the previous method
:meth:`~cryptography.hazmat.primitives.asymmetric.ec.EllipticCurvePublicNumbers.encode_point`.


.. _v2-4-2:

2.4.2

~~~~~~~~~~~~~~~~~~

* Updated Windows, macOS, and ``manylinux1`` wheels to be compiled with
OpenSSL 1.1.0j.

.. _v2-4-1:

2.4.1

~~~~~~~~~~~~~~~~~~

* Fixed a build breakage in our ``manylinux1`` wheels.

.. _v2-4:

2.4

~~~~~~~~~~~~~~~~

* **BACKWARDS INCOMPATIBLE:** Dropped support for LibreSSL 2.4.x.
* Deprecated OpenSSL 1.0.1 support. OpenSSL 1.0.1 is no longer supported by
the OpenSSL project. At this time there is no time table for dropping
support, however we strongly encourage all users to upgrade or install
``cryptography`` from a wheel.
* Added initial :doc:`OCSP </x509/ocsp>` support.
* Added support for :class:`~cryptography.x509.PrecertPoison`.

.. _v2-3-1:

2.3.1

~~~~~~~~~~~~~~~~~~

* Updated Windows, macOS, and ``manylinux1`` wheels to be compiled with
OpenSSL 1.1.0i.

.. _v2-3:
Links

Update debtcollector from 1.20.0 to 1.21.0.

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

Links

Update entrypoints from 0.2.3 to 0.3.

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

Links

Update gevent from 1.3.5 to 1.4.0.

Changelog

1.4.0

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

- Build with Cython 0.29 in '3str' mode.

- Test with PyPy 6.0 on Windows.

- Add support for application-wide callbacks when ``Greenlet`` objects
are started. See :pr:`1289`, provided by Yury Selivanov.

- Fix consuming a single ready object using
``next(gevent.iwait(objs))``. Previously such a construction would
hang because `iter` was not called. See :pr:`1288`, provided by Josh
Snyder. This is not recommended, though, as unwaited objects will
have dangling links (but see next item).

- Make `gevent.iwait` return an iterator that can now also be used as
a context manager. If you'll only be consuming part of the iterator,
use it in a ``with`` block to avoid leaking resources. See
:pr:`1290`, provided by Josh Snyder.

- Fix semaphores to immediately notify links if they are ready and
``rawlink()`` is called. This behaves like ``Event`` and
``AsyncEvent``. Note that the order in which semaphore links are
called is not specified. See :issue:`1287`, reported by Dan Milon.

- Improve safety of handling exceptions during interpreter shutdown.
See :issue:`1295` reported by BobDenar1212.

- Remove the deprecated ability to specify ``GEVENT_RESOLVER`` and
other importable settings as a ``path/to/a/package.module.item``.
This had race conditions and didn't work with complicated resolver
implementations. Place the required package or module on `sys.path`
first.

- Reduce the chances that using the blocking monitor functionality
could result in apparently random ``SystemError:
Objects/tupleobject.c: bad argument to internal function``. Reported
in :issue:`1302` by Ulrich Petri.

- Refactored the gevent test runner and test suite to make them more
reusable. In particular, the tests are now run with ``python -m
gevent.tests``. See :issue:`1293`.

- Make a monkey-patched ``socket.getaddrinfo`` return socket module
enums instead of plain integers for the socket type and address
family on Python 3. See :issue:`1310` reported by TheYOSH.

.. note:: This requires Python 3.4.3 or above due to an undocumented
         change in that version.

- Make gevent's pywsgi server set the non-standard environment value
``wsgi.input_terminated`` to True. See :issue:`1308`.

- Make `gevent.util.assert_switches` produce more informative messages
when the assertion fails.

- Python 2: If a `gevent.socket` was closed asynchronously (in a
different greenlet or a hub callback), `AttributeError` could result
if the socket was already in use. Now the correct socket.error
should be raised.

- Fix :meth:`gevent.threadpool.ThreadPool.join` raising a
`UserWarning` when using the libuv backend. Reported in
:issue:`1321` by ZeroNet.

- Fix ``FileObjectPosix.seek`` raising `OSError` when it should have
been `IOError` on Python 2. Reported by, and PR by, Ricardo Kirkner.
See :issue:`1323`.

- Upgrade libuv from 1.23.2 to 1.24.0.

1.3.7

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

- Formatting run info no longer includes ``gevent.local.local``
objects that have no value in the greenlet. See :issue:`1275`.

- Fixed negative length in pywsgi's Input read functions for non chunked body.
Reported in :issue:`1274` by tzickel.

- Upgrade libuv from 1.22.0 to 1.23.2.

- Fix opening files in text mode in CPython 2 on Windows by patching
libuv. See :issue:`1282` reported by wiggin15.

1.3.6

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

- gevent now depends on greenlet 0.4.14 or above. gevent binary wheels
for 1.3.5 and below must have greenlet 0.4.13 installed on Python
3.7 or they will crash. Reported by Alexey Stepanov in :issue:`1260`
and pkittenis in :issue:`1261`.

- :class:`gevent.local.local` subclasses correctly supports
``staticmethod`` functions. Reported by Brendan Powers in
:issue:`1266`.
Links

Update google-api-core from 1.3.0 to 1.13.0.

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

Links

Update google-auth from 1.5.1 to 1.6.3.

Changelog

1.6.3

------

02-15-2019 9:31 PST

Implementation Changes
+++++++++++++

- follow rfc 7515 : strip padding from JWS segments 324 (`324 <https://github.com/googleapis/google-auth-library-python/pull/324>`_)
- Add retry to _metadata.ping() (`323 <https://github.com/googleapis/google-auth-library-python/pull/323>`_)

1.6.2

------

12-17-2018 10:51 PST

Documentation
+++++++++++++

- Announce deprecation of Python 2.7 (`311 <https://github.com/googleapis/google-auth-library-python/pull/311>`_)
- Link all the PRs in CHANGELOG (`307 <https://github.com/googleapis/google-auth-library-python/pull/307>`_)

1.6.1

------

11-12-2018 10:10 PST

Implementation Changes
++++++++++++++++++++++

- Automatically refresh impersonated credentials (`304 <https://github.com/googleapis/google-auth-library-python/pull/304>`_)

1.6.0

------

11-09-2018 11:07 PST

New Features
++++++++++++

- Add google.auth.impersonated_credentials (`299 <https://github.com/googleapis/google-auth-library-python/pull/299>`_)

Documentation
+++++++++++++

- Update link to documentation for default credentials (`296 <https://github.com/googleapis/google-auth-library-python/pull/296>`_)
- Update github issue templates (`300 <https://github.com/googleapis/google-auth-library-python/pull/300>`_)
- Remove punctuation which becomes part of the url (`284 <https://github.com/googleapis/google-auth-library-python/pull/284>`_)

Internal / Testing Changes
++++++++++++++++++++++++++

- Update trampoline.sh (`302 <https://github.com/googleapis/google-auth-library-python/pull/302>`_)
- Enable static type checking with pytype (`298 <https://github.com/googleapis/google-auth-library-python/pull/298>`_)
- Make classifiers in setup.py an array. (`280 <https://github.com/googleapis/google-auth-library-python/pull/280>`_)
Links

Update google-cloud-core from 0.28.1 to 1.0.2.

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

Links

Update google-cloud-storage from 1.10.0 to 1.16.1.

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

Links

Update google-resumable-media from 0.3.1 to 0.3.2.

Changelog

0.3.2

12-17-2018 17:31 PST

Implementation Changes
- Using `str` instead of `repr` for multipart boundary.

Dependencies
- Making `requests` a strict dependency for the `requests` subpackage.

Documentation
- Announce deprecation of Python 2.7 ([51](https://github.com/googleapis/google-resumable-media-python/pull/51))
- Fix broken redirect after repository move
- Updating generated static content in docs.

Internal / Testing Changes
- Modify file not found test to look for the correct error message
- Harden tests so they can run with debug logging statements
- Adding AppVeyor support.
- Marking the version in `master` as `.dev1`.
Links

Update googleapis-common-protos from 1.5.3 to 1.6.0.

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

Links

Update greenlet from 0.4.14 to 0.4.15.

Changelog

0.4.15

===========
- Support for RISC-V architecture
- Workaround a gcc bug on ppc64
Links

Update idna from 2.7 to 2.8.

Changelog

2.8

++++++++++++++++

- Update to Unicode 11.0.0.
- Provide more specific exceptions for some malformed labels.
Links

Update jeepney from 0.3.1 to 0.4.

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

Links

Update keyring from 13.2.1 to 19.0.2.

Changelog

19.0.2

------

* Refresh package skeleton.
* Adopt `black <https://pypi.org/project/black>`_ code style.

19.0.1

------

* Merge with 18.0.1.

19.0.0

------

* 383: Drop support for EOL Python 2.7 - 3.4.

18.0.1

------

* 386: ExceptionInfo no longer retains a reference to the
traceback.

18.0.0

------

* 375: On macOS, the backend now raises a ``KeyringLocked``
when access to the keyring is denied (on get or set) instead
of ``PasswordSetError`` or ``KeyringError``. Any API users
may need to account for this change, probably by catching
the parent ``KeyringError``.
Additionally, the error message from the underying error is
now included in any errors that occur.

17.1.1

------

* 368: Update packaging technique to avoid 0.0.0 releases.

17.1.0

------

* 366: When calling ``keyring.core.init_backend``, if any
limit function is supplied, it is saved and later honored by
the ``ChainerBackend`` as well.

17.0.0

------

* 345: Remove application attribute from stored passwords
using SecretService, addressing regression introduced in
10.5.0 (292). Impacted Linux keyrings will once again
prompt for a password for "Python program".

16.1.1

------

* 362: Fix error on import due to circular imports
on Python 3.4.

16.1.0

------

* Refactor ChainerBackend, introduced in 16.0 to function
as any other backend, activating when relevant.

16.0.2

------

* 319: In Windows backend, trap all exceptions when
attempting to import pywin32.

16.0.1

------

* 357: Once again allow all positive, non-zero priority
keyrings to participate.

16.0.0

------

* 323: Fix race condition in delete_password on Windows.
* 352: All suitable backends (priority 1 and greater) are
allowed to participate.

15.2.0

------

* 350: Added new API for ``get_credentials``, for backends
that can resolve both a username and password for a service.

15.1.0

------

* 340: Add the Null keyring, disabled by default.
* 340: Added ``--disable`` option to command-line
interface.
* 340: Now honor a ``PYTHON_KEYRING_BACKEND``
environment variable to select a backend. Environments
may set to ``keyring.backends.null.Keyring`` to disable
keyring.

15.0.0

------

Removed deprecated ``keyring.util.escape`` module.

Fixed warning about using deprecated Abstract Base Classes
from collections module.

14.0.0

------

Removed ``getpassbackend`` module and alias in
``keyring.get_pass_get_password``. Instead, just use::

 keyring.get_password(getpass.getuser(), 'Python')
Links

Update keystoneauth1 from 3.10.0 to 3.14.0.

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

Links

Update msgpack from 0.5.6 to 0.6.1.

Changelog

0.6.1

======

Release Date: 2019-01-25

This release is for mitigating pain caused by v0.6.1 reduced max input limits
for security reason.

* ``unpackb(data)`` configures ``max_*_len`` options from ``len(data)``,
instead of static default sizes.

* ``Unpacker(max_buffer_len=N)`` configures ``max_*_len`` options from ``N``,
instead of static default sizes.

* ``max_bin_len``, ``max_str_len``, and ``max_ext_len`` are deprecated.
Since this is minor release, it's document only deprecation.

0.6

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

New features:

- Added `msgpack2json` continuous mode (`-c` and `-C`) to convert a stream of top-level objects (4)

Bug fixes:

- Fixed a bug that could cause a newline to be printed incorrectly in pretty-printing mode

0.6.0

======

Release Date: 2018-11-30

This release contains some backward incompatible changes for security reason (DoS).

Important changes
-----------------

* unpacker: Default value of input limits are smaller than before to avoid DoS attack.
If you need to handle large data, you need to specify limits manually. (319)

* Unpacker doesn't wrap underlaying ``ValueError`` (including ``UnicodeError``) into
``UnpackValueError``.  If you want to catch all exception during unpack, you need
to use ``try ... except Exception`` with minimum try code block. (323, 233)

* ``PackValueError`` and ``PackOverflowError`` are also removed.  You need to catch
normal ``ValueError`` and ``OverflowError``. (323, 233)

* Unpacker has ``strict_map_key`` option now.  When it is true, only bytes and str
(unicode in Python 2) are allowed for map keys.  It is recommended to avoid
hashdos.  Default value of this option is False for backward compatibility reason.
But it will be changed True in 1.0. (296, 334)

Other changes
-------------

* Extension modules are merged.  There is ``msgpack._cmsgpack`` instead of
``msgpack._packer`` and ``msgpack._unpacker``. (314, 328)

* Add ``Unpacker.getbuffer()`` method. (320)

* unpacker: ``msgpack.StackError`` is raised when input data contains too
nested data. (331)

* unpacker: ``msgpack.FormatError`` is raised when input data is not valid
msgpack format. (331)

0.5.12

* Added support for JRuby 9K.
* Added a benchmarking suite.
* Fixed a bug in the handling of options given to MessagePack.unpack in JRuby.

0.5.11

NEW FEATURE
* `MessagePackIgnoreAttribute` to exclude properties. Issue 55

0.5.10

CHANGES
* WinRT and Windows Phone (not Silverlight) builds now do not have AllowPartiallyTrustedCallersAttribute because it causes MethodAccessException on Windows Phone. This should not be breaking change effectively because apps in app container themselves should be SecurityCritical. Issue 64.

BUG FIXES
* Avoid memcmp usage for Windows Phone App Certification. Issue 65.

0.5.9

* Fixed Unpackerread_map_header and read_array_header
* Added support for Symbol GC added since MRI 2.2.0

0.5.8

BUG FIXES
* Fix Unpacker fails to unpack data when the stream returns data one by one. Issue 59
* Fix Unpacker cannot read empty bytes from System.Net API. Issue 60

Relase 0.5.9 - 2015/2/01

BUG FIXES
* Fix NullReferenceException is thrown for annotated non-public members serialization/deserialization in WinRT.
* Fix collection typed property which has non-public setter are not handled correctly. Issue 62.
* Fix ArgumentOutOfRangeException occurs when serializing members count is greater than 127. Issue 63.

0.5.7

BUG FIXES
* Fix serializer uses unnecessary reflection to get collection typed property.
* Fix generated serializers in source code style may have extra fields when multiple serializers are generated at a time.
* Mpu.exe's --refernce option distinction now respects platform rules and uses absolute paths instead of relative paths.
* Fix lambda expressions in source code causes failure of mpu.exe in Mono.

IMPROVEMENTS
* Add mpu.exe -r option which is shorthand of --reference.
* Add default and implicit --reference=./MsgPack.dll option in mpu.exe
Links

Update msrest from 0.5.4 to 0.6.8.

Changelog

0.6.8

BugFixes

- Impossible to serialize XML if model contains UTF8 characters on Python 2.7

<!-- Reviewable:start -->
---
This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/fusionapp/docker-postgresql/97)
<!-- Reviewable:end -->

@pyup-bot
Copy link
Contributor Author

pyup-bot commented Aug 1, 2019

Closing this in favor of #98

@pyup-bot pyup-bot closed this Aug 1, 2019
@mithrandi mithrandi deleted the pyup-scheduled-update-2019-07-01 branch August 1, 2019 15:53
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.

1 participant