[requires.io] dependency update on master branch #39

mithrandi · 2016-04-14T06:38:29Z

This change is

codecov-io · 2016-04-14T06:40:36Z

Current coverage is `100.00%`

Merging #39 into master will not affect coverage as of 20a0aef

@@            master     #39   diff @@
======================================
  Files            7       7       
  Stmts          263     263       
  Branches        23      23       
  Methods          0               
======================================
  Hit            263     263       
  Partial          0       0       
  Missed           0       0

Review entire Coverage Diff as of 20a0aef

Powered by Codecov. Updated on successful CI builds.

mithrandi · 2016-04-14T08:07:33Z

Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

151: Scheduled weekly dependency update for week 35 r=mithrandi ## 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. <table align="center"> <tr> <td><b>hyperlink</b></td> <td align="center">17.3.0</td> <td align="center">»</td> <td align="center">17.3.1</td> <td> <a href="https://pypi.python.org/pypi/hyperlink">PyPI</a> | <a href="https://pyup.io/changelogs/hyperlink/">Changelog</a> | <a href="https://github.com/python-hyper/hyperlink">Repo</a> </td> <tr> <td><b>hypothesis</b></td> <td align="center">3.18.0</td> <td align="center">»</td> <td align="center">3.22.0</td> <td> <a href="https://pypi.python.org/pypi/hypothesis">PyPI</a> | <a href="https://pyup.io/changelogs/hypothesis/">Changelog</a> | <a href="https://github.com/HypothesisWorks/hypothesis/issues">Repo</a> </td> <tr> <td><b>pyasn1-modules</b></td> <td align="center">0.0.11</td> <td align="center">»</td> <td align="center">0.1.1</td> <td> <a href="https://pypi.python.org/pypi/pyasn1-modules">PyPI</a> | <a href="https://pyup.io/changelogs/pyasn1-modules/">Changelog</a> | <a href="https://github.com/etingof/pyasn1-modules">Repo</a> </td> <tr> <td><b>pyasn1</b></td> <td align="center">0.3.2</td> <td align="center">»</td> <td align="center">0.3.3</td> <td> <a href="https://pypi.python.org/pypi/pyasn1">PyPI</a> | <a href="https://pyup.io/changelogs/pyasn1/">Changelog</a> | <a href="https://github.com/etingof/pyasn1">Repo</a> </td> </tr> </table> ## Changelogs ### hypothesis 3.18.0 -> 3.22.0 >### 3.22.0 >------------------- >This release provides what should be a substantial performance improvement to >numpy arrays generated using :ref:`provided numpy support <hypothesis-numpy>`, >and adds a new ``fill_value`` argument to :func:`~hypothesis.extra.numpy.arrays` >to control this behaviour. >This work was funded by `Stripe <https://stripe.com/>`_. >------------------- >### 3.21.3 >------------------- >This release fixes some extremely specific circumstances that probably have >never occurred in the wild where users of >:func:`~hypothesis.searchstrategy.deferred` might have seen a RuntimeError from >too much recursion, usually in cases where no valid example could have been >generated anyway. >------------------- >### 3.21.2 >------------------- >This release fixes some minor bugs in argument validation: > * :ref:`hypothesis.extra.numpy <hypothesis-numpy>` dtype strategies would raise an internal error > instead of an InvalidArgument exception when passed an invalid > endianness specification. > * :func:`~hypothesis.strategies.fractions` would raise an internal error instead of an InvalidArgument > if passed ``float("nan")`` as one of its bounds. > * The error message for passing ``float("nan")`` as a bound to various > strategies has been improved. > * Various bound arguments will now raise InvalidArgument in cases where > they would previously have raised an internal TypeError or > ValueError from the relevant conversion function. > * :func:`~hypothesis.strategies.streaming` would not have emitted a > deprecation warning when called with an invalid argument. >------------------- >### 3.21.1 >------------------- >This release fixes a bug where test failures that were the result of >an example would print an extra stack trace before re-raising the >exception. >------------------- >### 3.21.0 >------------------- >This release deprecates Hypothesis's strict mode, which turned Hypothesis's >deprecation warnings into errors. Similar functionality can be achieved >by using :func:`simplefilter('error', HypothesisDeprecationWarning) <python:warnings.simplefilter>`. >------------------- >### 3.20.0 >------------------- >This release renames the relevant arguments on the >:func:`~hypothesis.strategies.datetimes`, :func:`~hypothesis.strategies.dates`, >:func:`~hypothesis.strategies.times`, and :func:`~hypothesis.strategies.timedeltas` >strategies to ``min_value`` and ``max_value``, to make them consistent with the >other strategies in the module. >The old argument names are still supported but will emit a deprecation warning >when used explicitly as keyword arguments. Arguments passed positionally will >go to the new argument names and are not deprecated. >------------------- >### 3.19.3 >------------------- >This release provides a major overhaul to the internals of how Hypothesis >handles shrinking. >This should mostly be visible in terms of getting better examples for tests >which make heavy use of :func:`~hypothesis.strategies.composite`, >:ref:`data <interactive-draw>` or :ref:`flatmap <flatmap>` where the data >drawn depends a lot on previous choices, especially where size parameters are >affected. Previously Hypothesis would have struggled to reliably produce >good examples here. Now it should do much better. Performance should also be >better for examples with a non-zero ``min_size``. >You may see slight changes to example generation (e.g. improved example >diversity) as a result of related changes to internals, but they are unlikely >to be significant enough to notice. >------------------- >### 3.19.2 >------------------- >This release fixes two bugs in ``hypothesis.extra.numpy``: >* :func:`~hypothesis.extra.numpy.unicode_string_dtypes` didn't work at all due > to an incorrect dtype specifier. Now it does. >* Various impossible conditions would have been accepted but would error when > they fail to produced any example. Now they raise an explicit InvalidArgument > error. >------------------- >### 3.19.1 >------------------- >This is a bugfix release for :issue:`739`, where bounds for >:func:`~hypothesis.strategies.fractions` or floating-point >:func:`~hypothesis.strategies.decimals` were not properly converted to >integers before passing them to the integers strategy. >This excluded some values that should have been possible, and could >trigger internal errors if the bounds lay between adjacent integers. >You can now bound :func:`~hypothesis.strategies.fractions` with two >arbitrarily close fractions. >It is now an explicit error to supply a min_value, max_value, and >max_denominator to :func:`~hypothesis.strategies.fractions` where the value >bounds do not include a fraction with denominator at most max_denominator. >------------------- >### 3.19.0 >------------------- >This release adds the :func:`~hypothesis.strategies.from_regex` strategy, >which generates strings that contain a match of a regular expression. >Thanks to Maxim Kulkin for creating the >`hypothesis-regex <https://github.com/maximkulkin/hypothesis-regex>`_ >package and then helping to upstream it! (:issue:`662`) >------------------- >### 3.18.5 >------------------- >This is a bugfix release for :func:`~hypothesis.strategies.integers`. >Previously the strategy would hit an internal assertion if passed non-integer >bounds for ``min_value`` and ``max_value`` that had no integers between them. >The strategy now raises InvalidArgument instead. >------------------- >### 3.18.4 >------------------- >Release to fix a bug where mocks can be used as test runners under certain >conditions. Specifically, if a mock is injected into a test via pytest >fixtures or patch decorators, and that mock is the first argument in the >list, hypothesis will think it represents self and turns the mock >into a test runner. If this happens, the affected test always passes >because the mock is executed instead of the test body. Sometimes, it >will also fail health checks. >Fixes :issue:`491` and a section of :issue:`198`. >Thanks to Ben Peterson for this bug fix. >------------------- >### 3.18.3 >------------------- >This release should improve the performance of some tests which >experienced a slow down as a result of the 3.13.0 release. >Tests most likely to benefit from this are ones that make extensive >use of `min_size` parameters, but others may see some improvement >as well. >------------------- >### 3.18.2 >------------------- >This release fixes a bug introduced in 3.18.0. If the arguments >``whitelist_characters`` and ``blacklist_characters`` to >:func:`~hypothesis.strategies.characters` both contained elements, then an >``InvalidArgument`` exception would be raised. >Thanks to Zac Hatfield-Dodds for reporting and fixing this. >------------------- >### 3.18.1 >------------------- >This is a bug fix release to fix :issue:`780`, where >:func:`~hypothesis.strategies.sets` and similar would trigger health check >errors if their element strategy could only produce one element (e.g. >if it was :func:`~hypothesis.strategies.just`). >------------------- That's it for now! Happy merging! 🤖

155: Scheduled weekly dependency update for week 36 r=mithrandi ## 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. <table align="center"> <tr> <td><b>hypothesis</b></td> <td align="center">3.22.0</td> <td align="center">»</td> <td align="center">3.23.2</td> <td> <a href="https://pypi.python.org/pypi/hypothesis">PyPI</a> | <a href="https://pyup.io/changelogs/hypothesis/">Changelog</a> | <a href="https://github.com/HypothesisWorks/hypothesis/issues">Repo</a> </td> <tr> <td><b>pyrsistent</b></td> <td align="center">0.12.3</td> <td align="center">»</td> <td align="center">0.13.0</td> <td> <a href="https://pypi.python.org/pypi/pyrsistent">PyPI</a> | <a href="https://pyup.io/changelogs/pyrsistent/">Changelog</a> | <a href="http://github.com/tobgu/pyrsistent/">Repo</a> </td> </tr> </table> ## Changelogs ### hypothesis 3.22.0 -> 3.23.2 >### 3.23.2 >------------------- >This is a small refactoring release that removes a now-unused parameter to an >internal API. It shouldn't have any user visible effect. >------------------- >### 3.23.1 >------------------- >Hypothesis no longer propagates the dynamic scope of settings into strategy >definitions. >This release is a small change to something that was never part of the public >API and you will almost certainly not notice any effect unless you're doing >something surprising, but for example the following code will now give a >different answer in some circumstances: >.. code-block:: python > import hypothesis.strategies as st > from hypothesis import settings > CURRENT_SETTINGS = st.builds(lambda: settings.default) >(We don't actually encourage you writing code like this) >Previously this would have generated the settings that were in effect at the >point of definition of ``CURRENT_SETTINGS``. Now it will generate the settings >that are used for the current test. >It is very unlikely to be significant enough to be visible, but you may also >notice a small performance improvement. >------------------- >### 3.23.0 >------------------- >This release adds a ``unique`` argument to :func:`~hypothesis.extra.numpy.arrays` >which behaves the same ways as the corresponding one for >:func:`~hypothesis.strategies.lists`, requiring all of the elements in the >generated array to be distinct. >------------------- >### 3.22.2 >------------------- >This release fixes an issue where Hypothesis would raise a ``TypeError`` when >using the datetime-related strategies if running with ``PYTHONOPTIMIZE=2``. >This bug was introduced in v3.20.0. (See :issue:`822`) >------------------- >### 3.22.1 >------------------- >Hypothesis now transparently handles problems with an internal unicode cache, >including file truncation or read-only filesystems (:issue:`767`). >Thanks to Sam Hames for the patch. >------------------- ### pyrsistent 0.12.3 -> 0.13.0 >### 0.13.0 > * Fix 113, Skip field factories when loading pickled objects. There is a > minor backwards incompatibilty in the behaviour because of this. Thanks > teepark for fi this! > * Fix 116, negative indexing for pdeques. Thanks Julian for this! That's it for now! Happy merging! 🤖

161: Scheduled weekly dependency update for week 40 r=mithrandi ## 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. <table align="center"> <tr> <td><b>asn1crypto</b></td> <td align="center">0.22.0</td> <td align="center">»</td> <td align="center">0.23.0</td> <td> <a href="https://pypi.python.org/pypi/asn1crypto">PyPI</a> | <a href="https://pyup.io/changelogs/asn1crypto/">Changelog</a> | <a href="https://github.com/wbond/asn1crypto/issues">Repo</a> </td> <tr> <td><b>hypothesis</b></td> <td align="center">3.23.2</td> <td align="center">»</td> <td align="center">3.31.2</td> <td> <a href="https://pypi.python.org/pypi/hypothesis">PyPI</a> | <a href="https://pyup.io/changelogs/hypothesis/">Changelog</a> | <a href="https://github.com/HypothesisWorks/hypothesis/issues">Repo</a> </td> <tr> <td><b>pyasn1-modules</b></td> <td align="center">0.1.1</td> <td align="center">»</td> <td align="center">0.1.4</td> <td> <a href="https://pypi.python.org/pypi/pyasn1-modules">PyPI</a> | <a href="https://pyup.io/changelogs/pyasn1-modules/">Changelog</a> | <a href="https://github.com/etingof/pyasn1-modules">Repo</a> </td> <tr> <td><b>pyasn1</b></td> <td align="center">0.3.3</td> <td align="center">»</td> <td align="center">0.3.6</td> <td> <a href="https://pypi.python.org/pypi/pyasn1">PyPI</a> | <a href="https://pyup.io/changelogs/pyasn1/">Changelog</a> | <a href="https://github.com/etingof/pyasn1">Repo</a> </td> <tr> <td><b>pyopenssl</b></td> <td align="center">17.2.0</td> <td align="center">»</td> <td align="center">17.3.0</td> <td> <a href="https://pypi.python.org/pypi/pyopenssl">PyPI</a> | <a href="https://pyup.io/changelogs/pyopenssl/">Changelog</a> | <a href="https://pyopenssl.org/">Homepage</a> | <a href="http://pythonhosted.org/pyOpenSSL/">Docs</a> </td> <tr> <td><b>six</b></td> <td align="center">1.10.0</td> <td align="center">»</td> <td align="center">1.11.0</td> <td> <a href="https://pypi.python.org/pypi/six">PyPI</a> | <a href="https://pyup.io/changelogs/six/">Changelog</a> | <a href="http://pypi.python.org/pypi/six/">Homepage</a> | <a href="http://pythonhosted.org/six/">Docs</a> </td> <tr> <td><b>twisted[tls]</b></td> <td align="center">17.5.0</td> <td align="center">»</td> <td align="center">17.9.0</td> <td> <a href="https://pypi.python.org/pypi/twisted">PyPI</a> | <a href="https://pyup.io/changelogs/twisted/">Changelog</a> | <a href="http://twistedmatrix.com/">Homepage</a> | <a href="https://twistedmatrix.com/trac/">Bugtracker</a> </td> <tr> <td><b>zope.interface</b></td> <td align="center">4.4.2</td> <td align="center">»</td> <td align="center">4.4.3</td> <td> <a href="https://pypi.python.org/pypi/zope.interface">PyPI</a> | <a href="https://pyup.io/changelogs/zope.interface/">Changelog</a> | <a href="https://github.com/zopefoundation/zope.interface">Repo</a> </td> </tr> </table> ## Changelogs ### asn1crypto 0.22.0 -> 0.23.0 >### 0.23.0 > - Backwards compatibility break: the `tag_type`, `explicit_tag` and > `explicit_class` attributes on `core.Asn1Value` no longer exist and were > replaced by the `implicit` and `explicit` attributes. Field param dicts > may use the new `explicit` and `implicit` keys, or the old `tag_type` and > `tag` keys. The attribute changes will likely to have little to no impact > since they were primarily an implementation detail. > - Teletex strings used inside of X.509 certificates are now interpreted > using Windows-1252 (a superset of ISO-8859-1). This enables compatibility > with certificates generated by OpenSSL. Strict parsing of Teletex strings > can be retained by using the `x509.strict_teletex()` context manager. > - Added support for nested explicit tagging, supporting values that are > defined with explicit tagging and then added as a field of another > structure using explicit tagging. > - Fixed a `UnicodeDecodeError` when trying to find the (optional) dependency > OpenSSL on Python 2 > - Fixed `next_update` field of `crl.TbsCertList` to be optional > - Added the `x509.Certificate.sha256_fingerprint` property > - `x509.Certificate.ocsp_urls` and `x509.DistributionPoint.url` will now > return `https://`, `ldap://` and `ldaps://` URLs in addition to `http://`. > - Added CMS Attribute Protection definitions from RFC 6211 > - Added OIDs from RFC 6962 ### hypothesis 3.23.2 -> 3.31.2 >### 3.31.2 >------------------- >This release fixes some formatting and small typos/grammar issues in the >documentation, specifically the page docs/settings.rst, and the inline docs >for the various settings. >------------------- >### 3.31.1 >------------------- >This release improves the handling of deadlines so that they act better with >the shrinking process. This fixes :issue:`892`. >This involves two changes: >1. The deadline is raised during the initial generation and shrinking, and then > lowered to the set value for final replay. This restricts our attention to > examples which exceed the deadline by a more significant margin, which > increases their reliability. >2. When despite the above a test still becomes flaky because it is > significantly faster on rerun than it was on its first run, the error > message is now more explicit about the nature of this problem, and includes > both the initial test run time and the new test run time. >In addition, this release also clarifies the documentation of the deadline >setting slightly to be more explicit about where it applies. >This work was funded by `Smarkets <https://smarkets.com/>`_. >------------------- >### 3.31.0 >------------------- >This release blocks installation of Hypothesis on Python 3.3, which >:PEP:`reached its end of life date on 2017-09-29 <398>`. >This should not be of interest to anyone but downstream maintainers - >if you are affected, migrate to a secure version of Python as soon as >possible or at least seek commercial support. >------------------- >### 3.30.4 >------------------- >This release makes several changes: >1. It significantly improves Hypothesis's ability to use coverage information > to find interesting examples. >2. It reduces the default ``max_examples`` setting from 200 to 100. This takes > advantage of the improved algorithm meaning fewer examples are typically > needed to get the same testing and is sufficiently better at covering > interesting behaviour, and offsets some of the performance problems of > running under coverage. >3. Hypothesis will always try to start its testing with an example that is near > minimized. >The new algorithm for 1 also makes some changes to Hypothesis's low level data >generation which apply even with coverage turned off. They generally reduce the >total amount of data generated, which should improve test performance somewhat. >Between this and 3 you should see a noticeable reduction in test runtime (how >much so depends on your tests and how much example size affects their >performance. On our benchmarks, where data generation dominates, we saw up to >a factor of two performance improvement, but it's unlikely to be that large. >------------------- >### 3.30.3 >------------------- >This release fixes some formatting and small typos/grammar issues in the >documentation, specifically the page docs/details.rst, and some inline >docs linked from there. >------------------- >### 3.30.2 >------------------- >This release changes Hypothesis's caching approach for functions in >``hypothesis.strategies``. Previously it would have cached extremely >aggressively and cache entries would never be evicted. Now it adopts a >least-frequently used, least recently used key invalidation policy, and is >somewhat more conservative about which strategies it caches. >This should cause some workloads (anything that creates strategies based on >dynamic values, e.g. using flatmap or composite) to see a significantly lower >memory usage. >------------------- >### 3.30.1 >------------------- >This release fixes a bug where when running with use_coverage=True inside an >existing running instance of coverage, Hypothesis would frequently put files >that the coveragerc excluded in the report for the enclosing coverage. >------------------- >### 3.30.0 >------------------- >This release introduces two new features: >* pytest users can specify a seed to use for ``given`` based tests by passing > the ``--hypothesis-seed`` command line argument. >* When a test fails, either with a health check failure or a falsifying example, > Hypothesis will print out a seed that led to that failure, if the test is not > already running with a fixed seed. You can then recreate that failure using either > the ``seed`` decorator or (if you are running pytest) with ``--hypothesis-seed``. >This work was funded by `Smarkets <https://smarkets.com/>`_. >------------------- >### 3.29.0 >------------------- >This release makes Hypothesis coverage aware. Hypothesis now runs all test >bodies under coverage, and uses this information to guide its testing. >The :attr:`~hypothesis.settings.use_coverage` setting can be used to disable >this behaviour if you want to test code that is sensitive to coverage being >enabled (either because of performance or interaction with the trace function). >The main benefits of this feature are: >* Hypothesis now observes when examples it discovers cover particular lines > or branches and stores them in the database for later. >* Hypothesis will make some use of this information to guide its exploration of > the search space and improve the examples it finds (this is currently used > only very lightly and will likely improve significantly in future releases). >This also has the following side-effects: >* Hypothesis now has an install time dependency on the coverage package. >* Tests that are already running Hypothesis under coverage will likely get > faster. >* Tests that are not running under coverage now run their test bodies under > coverage by default. >This feature is only partially supported under pypy. It is significantly slower >than on CPython and is turned off by default as a result, but it should still >work correctly if you want to use it. >------------------- >### 3.28.3 >------------------- >This release is an internal change that affects how Hypothesis handles >calculating certain properties of strategies. >The primary effect of this is that it fixes a bug where use of >:func:`~hypothesis.deferred` could sometimes trigger an internal assertion >error. However the fix for this bug involved some moderately deep changes to >how Hypothesis handles certain constructs so you may notice some additional >knock-on effects. >In particular the way Hypothesis handles drawing data from strategies that >cannot generate any values has changed to bail out sooner than it previously >did. This may speed up certain tests, but it is unlikely to make much of a >difference in practice for tests that were not already failing with >Unsatisfiable. >------------------- >### 3.28.2 >------------------- >This is a patch release that fixes a bug in the `hypothesis.extra.pandas` documentation where it incorrectly referred to column instead of columns. >------------------- >### 3.28.1 >------------------- >This is a refactoring release. It moves a number of internal uses >of nametuple over to using attrs based classes, and removes a couple >of internal namedtuple classes that were no longer in use. >It should have no user visible impact. >------------------- >### 3.28.0 >------------------- >This release adds support for testing pandas via the :ref:`hypothesis.extra.pandas <hypothesis-pandas>` >module. >It also adds a dependency on attrs. >This work was funded by `Stripe <https://stripe.com/>`_. >------------------- >### 3.27.1 >------------------- >This release fixes some formatting and broken cross-references in the >documentation, which includes editing docstrings - and thus a patch release. >------------------- >### 3.27.0 >------------------- >This release introduces a :attr:`~hypothesis.settings.deadline` >setting to Hypothesis. >When set this turns slow tests into errors. By default it is unset but will >warn if you exceed 200ms, which will become the default value in a future >release. >This work was funded by `Smarkets <https://smarkets.com/>`_. >------------------- >### 3.26.0 >------------------- >Hypothesis now emits deprecation warnings if you are using the legacy >SQLite example database format, or the tool for merging them. These were >already documented as deprecated, so this doesn't change their deprecation >status, only that we warn about it. >------------------- >### 3.25.1 >------------------- >This release fixes a bug with generating numpy datetime and timedelta types: >When inferring the strategy from the dtype, datetime and timedelta dtypes with >sub-second precision would always produce examples with one second resolution. >Inferring a strategy from a time dtype will now always produce example with the >same precision. >------------------- >### 3.25.0 >------------------- >This release changes how Hypothesis shrinks and replays examples to take into >account that it can encounter new bugs while shrinking the bug it originally >found. Previously it would end up replacing the originally found bug with the >new bug and show you only that one. Now it is (often) able to recognise when >two bugs are distinct and when it finds more than one will show both. >------------------- >### 3.24.2 >------------------- >This release removes the (purely internal and no longer useful) >``strategy_test_suite`` function and the corresponding strategytests module. >------------------- >### 3.24.1 >------------------- >This release improves the reduction of examples involving floating point >numbers to produce more human readable examples. >It also has some general purpose changes to the way the minimizer works >internally, which may see some improvement in quality and slow down of test >case reduction in cases that have nothing to do with floating point numbers. >------------------- >### 3.24.0 >------------------- >Hypothesis now emits deprecation warnings if you use example() inside a >test function or strategy definition (this was never intended to be supported, >but is sufficiently widespread that it warrants a deprecation path). >------------------- >### 3.23.3 >------------------- >This is a bugfix release for :func:`~hypothesis.strategies.decimals` >with the ``places`` argument. >- No longer fails health checks (:issue:`725`, due to internal filtering) >- Specifying a ``min_value`` and ``max_value`` without any decimals with > ``places`` places between them gives a more useful error message. >- Works for any valid arguments, regardless of the decimal precision context. >------------------- ### pyopenssl 17.2.0 -> 17.3.0 >### 17.3.0 >------------------- >Backward-incompatible changes: >^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ >- Dropped support for Python 3.3. > `677 <https://github.com/pyca/pyopenssl/pull/677>`_ >- Removed the deprecated ``OpenSSL.rand`` module. > This is being done ahead of our normal deprecation schedule due to its lack of use and the fact that it was becoming a maintenance burden. > ``os.urandom()`` should be used instead. > `675 <https://github.com/pyca/pyopenssl/pull/675>`_ >Deprecations: >^^^^^^^^^^^^^ >- Deprecated ``OpenSSL.tsafe``. > `673 <https://github.com/pyca/pyopenssl/pull/673>`_ >Changes: >^^^^^^^^ >- Fixed a memory leak in ``OpenSSL.crypto.CRL``. > `690 <https://github.com/pyca/pyopenssl/pull/690>`_ >- Fixed a memory leak when verifying certificates with ``OpenSSL.crypto.X509StoreContext``. > `691 <https://github.com/pyca/pyopenssl/pull/691>`_ >---- ### six 1.10.0 -> 1.11.0 >### 1.11.0 >------ >- Pull request 178: `with_metaclass` now properly proxies `__prepare__` to the > underlying metaclass. >- Pull request 191: Allow `with_metaclass` to work with metaclasses implemented > in C. >- Pull request 203: Add parse_http_list and parse_keqv_list to moved > urllib.request. >- Pull request 172 and issue 171: Add unquote_to_bytes to moved urllib.parse. >- Pull request 167: Add `six.moves.getoutput`. >- Pull request 80: Add `six.moves.urllib_parse.splitvalue`. >- Pull request 75: Add `six.moves.email_mime_image`. >- Pull request 72: Avoid creating reference cycles through tracebacks in > `reraise`. ### zope.interface 4.4.2 -> 4.4.3 >### 4.4.3 >------------------ >- Avoid exceptions when the ``__annotations__`` attribute is added to > interface definitions with Python 3.x type hints. See `issue 98 > <https://github.com/zopefoundation/zope.interface/issues/98>`_. >- Fix the possibility of a rare crash in the C extension when > deallocating items. See `issue 100 > <https://github.com/zopefoundation/zope.interface/issues/100>`_. That's it for now! Happy merging! 🤖

163: Scheduled weekly dependency update for week 42 r=mithrandi ## 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. <table align="center"> <tr> <td><b>cryptography</b></td> <td align="center">2.0.3</td> <td align="center">»</td> <td align="center">2.1.1</td> <td> <a href="https://pypi.python.org/pypi/cryptography">PyPI</a> | <a href="https://pyup.io/changelogs/cryptography/">Changelog</a> | <a href="https://github.com/pyca/cryptography">Repo</a> </td> <tr> <td><b>hypothesis</b></td> <td align="center">3.31.2</td> <td align="center">»</td> <td align="center">3.33.0</td> <td> <a href="https://pypi.python.org/pypi/hypothesis">PyPI</a> | <a href="https://pyup.io/changelogs/hypothesis/">Changelog</a> | <a href="https://github.com/HypothesisWorks/hypothesis/issues">Repo</a> </td> <tr> <td><b>pyasn1-modules</b></td> <td align="center">0.1.4</td> <td align="center">»</td> <td align="center">0.1.5</td> <td> <a href="https://pypi.python.org/pypi/pyasn1-modules">PyPI</a> | <a href="https://pyup.io/changelogs/pyasn1-modules/">Changelog</a> | <a href="https://github.com/etingof/pyasn1-modules">Repo</a> </td> <tr> <td><b>pyasn1</b></td> <td align="center">0.3.6</td> <td align="center">»</td> <td align="center">0.3.7</td> <td> <a href="https://pypi.python.org/pypi/pyasn1">PyPI</a> | <a href="https://pyup.io/changelogs/pyasn1/">Changelog</a> | <a href="https://github.com/etingof/pyasn1">Repo</a> </td> <tr> <td><b>pyrsistent</b></td> <td align="center">0.13.0</td> <td align="center">»</td> <td align="center">0.14.0</td> <td> <a href="https://pypi.python.org/pypi/pyrsistent">PyPI</a> | <a href="https://pyup.io/changelogs/pyrsistent/">Changelog</a> | <a href="http://github.com/tobgu/pyrsistent/">Repo</a> </td> </tr> </table> ## Changelogs ### cryptography 2.0.3 -> 2.1.1 >### 2.1 >~~~~~~~~~~~~~~~~ >* **FINAL DEPRECATION** Python 2.6 support is deprecated, and will be removed > in the next release of ``cryptography``. >* **BACKWARDS INCOMPATIBLE:** ``Whirlpool``, ``RIPEMD160``, and > ``UnsupportedExtension`` have been removed in accordance with our > :doc:`/api-stability` policy. >* **BACKWARDS INCOMPATIBLE:** :attr:`~cryptography.x509.DNSName.value`, > :attr:`~cryptography.x509.RFC822Name.value`, and > :attr:`~cryptography.x509.UniformResourceIdentifier.value` will now return > an :term:`A-label` string when parsing a certificate containing an > internationalized domain name (IDN) or if the caller passed a :term:`U-label` > to the constructor. See below for additional deprecations related to this > change. >* Installing ``cryptography`` now requires ``pip`` 6 or newer. >* Deprecated passing :term:`U-label` strings to the > :class:`~cryptography.x509.DNSName`, > :class:`~cryptography.x509.UniformResourceIdentifier`, and > :class:`~cryptography.x509.RFC822Name` constructors. Instead, users should > pass values as :term:`A-label` strings with ``idna`` encoding if necessary. > This change will not affect anyone who is not processing internationalized > domains. >* Added support for > :class:`~cryptography.hazmat.primitives.ciphers.algorithms.ChaCha20`. In > most cases users should choose > :class:`~cryptography.hazmat.primitives.ciphers.aead.ChaCha20Poly1305` > rather than using this unauthenticated form. >* Added :meth:`~cryptography.x509.CertificateRevocationList.is_signature_valid` > to :class:`~cryptography.x509.CertificateRevocationList`. >* Support :class:`~cryptography.hazmat.primitives.hashes.BLAKE2b` and > :class:`~cryptography.hazmat.primitives.hashes.BLAKE2s` with > :class:`~cryptography.hazmat.primitives.hmac.HMAC`. >* Added support for > :class:`~cryptography.hazmat.primitives.ciphers.modes.XTS` mode for > AES. >* Added support for using labels with > :class:`~cryptography.hazmat.primitives.asymmetric.padding.OAEP` when using > OpenSSL 1.0.2 or greater. >* Improved compatibility with NSS when issuing certificates from an issuer > that has a subject with non-``UTF8String`` string types. >* Add support for the :class:`~cryptography.x509.DeltaCRLIndicator` extension. >* Add support for the :class:`~cryptography.x509.TLSFeature` > extension. This is commonly used for enabling ``OCSP Must-Staple`` in > certificates. >* Add support for the :class:`~cryptography.x509.FreshestCRL` extension. >.. _v2-0-3: ### hypothesis 3.31.2 -> 3.33.0 >### 3.33.0 >------------------- >This release supports strategy inference for more field types in Django >:func:`~hypothesis.extra.django.models` - you can now omit an argument for >Date, Time, Duration, Slug, IP Address, and UUID fields. (:issue:`642`) >Strategy generation for fields with grouped choices now selects choices from >each group, instead of selecting from the group names. >------------------- >### 3.32.2 >------------------- >This patch removes the ``mergedb`` tool, introduced in Hypothesis 1.7.1 >on an experimental basis. It has never actually worked, and the new >:doc:`Hypothesis example database <database>` is designed to make such a >tool unnecessary. >------------------- >### 3.32.1 >------------------- >This patch has two improvements for strategies based on enumerations. >- :func:`~hypothesis.strategies.from_type` now handles enumerations correctly, > delegating to :func:`~hypothesis.strategies.sampled_from`. Previously it > noted that ``Enum.__init__`` has no required arguments and therefore delegated > to :func:`~hypothesis.strategies.builds`, which would subsequently fail. >- When sampling from an :class:`python:enum.Flag`, we also generate combinations > of members. Eg for ``Flag('Permissions', 'READ, WRITE, EXECUTE')`` we can now > generate, ``Permissions.READ``, ``Permissions.READ|WRITE``, and so on. >------------------- >### 3.32.0 >------------------- >This changes the default value of >:attr:`use_coverage=True <hypothesis.settings.use_coverage>` to True when >running on pypy (it was already True on CPython). >It was previously set to False because we expected it to be too slow, but >recent benchmarking shows that actually performance of the feature on pypy is >fairly acceptable - sometimes it's slower than on CPython, sometimes it's >faster, but it's generally within a factor of two either way. >------------------- >### 3.31.6 >------------------- >This patch improves the quality of strategies inferred from Numpy dtypes: >* Integer dtypes generated examples with the upper half of their (non-sign) bits > set to zero. The inferred strategies can now produce any representable integer. >* Fixed-width unicode- and byte-string dtypes now cap the internal example > length, which should improve example and shrink quality. >* Numpy arrays can only store fixed-size strings internally, and allow shorter > strings by right-padding them with null bytes. Inferred string strategies > no longer generate such values, as they can never be retrieved from an array. > This improves shrinking performance by skipping useless values. >This has already been useful in Hypothesis - we found an overflow bug in our >Pandas support, and as a result :func:`~hypothesis.extra.pandas.indexes` and >:func:`~hypothesis.extra.pandas.range_indexes` now check that ``min_size`` >and ``max_size`` are at least zero. >------------------- >### 3.31.5 >------------------- >This release fixes a performance problem in tests where >:attr:`~hypothesis.settings.use_coverage` is set to True. >Tests experience a slow-down proportionate to the amount of code they cover. >This is still the case, but the factor is now low enough that it should be >unnoticeable. Previously it was large and became much larger in 3.28.4. >------------------- >### 3.31.4 >------------------- >:func:`~hypothesis.strategies.from_type` failed with a very confusing error >if passed a :func:`~python:typing.NewType` (:issue:`901`). These psudeo-types >are now unwrapped correctly, and strategy inference works as expected. >------------------- >### 3.31.3 >------------------- >This release makes some small optimisations to our use of coverage that should >reduce constant per-example overhead. This is probably only noticeable on >examples where the test itself is quite fast. On no-op tests that don't test >anything you may see up to a fourfold speed increase (which is still >significantly slower than without coverage). On more realistic tests the speed >up is likely to be less than that. >------------------- ### pyrsistent 0.13.0 -> 0.14.0 >### 0.14.0 > * Fix 117, pmap now accepts iterators as input to constructor. Thanks Julian for this! > * Drop support for Python 2.6. Nothing has been done in this release that will explicitly > break pyrsistent for 2.6 but it will not be considered moving forward. Dropping 2.6 > support is the reason for stepping the second decimal instead of the third. That's it for now! Happy merging! 🤖

167: Scheduled weekly dependency update for week 46 r=mithrandi ## 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. <table align="center"> <tr> <td><b>attrs</b></td> <td align="center">17.2.0</td> <td align="center">»</td> <td align="center">17.3.0</td> <td> <a href="https://pypi.python.org/pypi/attrs">PyPI</a> | <a href="https://pyup.io/changelogs/attrs/">Changelog</a> | <a href="http://www.attrs.org/">Homepage</a> </td> <tr> <td><b>cryptography</b></td> <td align="center">2.1.2</td> <td align="center">»</td> <td align="center">2.1.3</td> <td> <a href="https://pypi.python.org/pypi/cryptography">PyPI</a> | <a href="https://pyup.io/changelogs/cryptography/">Changelog</a> | <a href="https://github.com/pyca/cryptography">Repo</a> </td> <tr> <td><b>hypothesis</b></td> <td align="center">3.33.0</td> <td align="center">»</td> <td align="center">3.37.0</td> <td> <a href="https://pypi.python.org/pypi/hypothesis">PyPI</a> | <a href="https://pyup.io/changelogs/hypothesis/">Changelog</a> | <a href="https://github.com/HypothesisWorks/hypothesis/issues">Repo</a> </td> </tr> </table> ## Changelogs ### attrs 17.2.0 -> 17.3.0 >### 17.3.0 >------------------- >Backward-incompatible Changes >^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ >- Attributes are not defined on the class body anymore. > This means that if you define a class ``C`` with an attribute ``x``, the class will *not* have an attribute ``x`` for introspection anymore. > Instead of ``C.x``, use ``attr.fields(C).x`` or look at ``C.__attrs_attrs__``. > The old behavior has been deprecated since version 16.1. > (`253 <https://github.com/python-attrs/attrs/issues/253>`_) >Changes >^^^^^^^ >- ``super()`` and ``__class__`` now work on Python 3 when ``slots=True``. > (`102 <https://github.com/python-attrs/attrs/issues/102>`_, `226 <https://github.com/python-attrs/attrs/issues/226>`_, `269 <https://github.com/python-attrs/attrs/issues/269>`_, `270 <https://github.com/python-attrs/attrs/issues/270>`_, `272 <https://github.com/python-attrs/attrs/issues/272>`_) >- Added ``type`` argument to ``attr.ib()`` and corresponding ``type`` attribute to ``attr.Attribute``. > This change paves the way for automatic type checking and serialization (though as of this release ``attrs`` does not make use of it). > In Python 3.6 or higher, the value of ``attr.Attribute.type`` can alternately be set using variable type annotations > (see `PEP 526 <https://www.python.org/dev/peps/pep-0526/>`_). (`151 <https://github.com/python-attrs/attrs/issues/151>`_, `214 <https://github.com/python-attrs/attrs/issues/214>`_, `215 <https://github.com/python-attrs/attrs/issues/215>`_, `239 <https://github.com/python-attrs/attrs/issues/239>`_) >- The combination of ``str=True`` and ``slots=True`` now works on Python 2. > (`198 <https://github.com/python-attrs/attrs/issues/198>`_) >- ``attr.Factory`` is hashable again. (`204 > <https://github.com/python-attrs/attrs/issues/204>`_) >- Subclasses now can overwrite attribute definitions of their superclass. > That means that you can -- for example -- change the default value for an attribute by redefining it. > (`221 <https://github.com/python-attrs/attrs/issues/221>`_, `229 <https://github.com/python-attrs/attrs/issues/229>`_) >- Added new option ``auto_attribs`` to ``attr.s`` that allows to collect annotated fields without setting them to ``attr.ib()``. > Setting a field to an ``attr.ib()`` is still possible to supply options like validators. > Setting it to any other value is treated like it was passed as ``attr.ib(default=value)`` -- passing an instance of ``attr.Factory`` also works as expected. > (`262 <https://github.com/python-attrs/attrs/issues/262>`_, `277 <https://github.com/python-attrs/attrs/issues/277>`_) >- Instances of classes created using ``attr.make_class()`` can now be pickled. > (`282 <https://github.com/python-attrs/attrs/issues/282>`_) >---- ### hypothesis 3.33.0 -> 3.37.0 >### 3.37.0 >------------------- >This is a deprecation release for some health check related features. >The following are now deprecated: >* Passing :attr:`~hypothesis.HealthCheck.exception_in_generation` to > :attr:`~hypothesis.settings.suppress_health_check`. This no longer does > anything even when passed - All errors that occur during data generation > will now be immediately reraised rather than going through the health check > mechanism. >* Passing :attr:`~hypothesis.HealthCheck.random_module` to > :attr:`~hypothesis.settings.suppress_health_check`. This hasn't done anything > for a long time, but was never explicitly deprecated. Hypothesis always seeds > the random module when running given tests, so this is no longer an error > and suppressing it doesn't do anything. >* Passing non-:class:`~hypothesis.HealthCheck` values in > :attr:`~hypothesis.settings.suppress_health_check`. This was previously > allowed but never did anything useful. >In addition, passing a non-iterable value as :attr:`~hypothesis.settings.suppress_health_check` >will now raise an error immediately (it would never have worked correctly, but >it would previously have failed later). Some validation error messages have >also been updated. >This work was funded by `Smarkets <https://smarkets.com/>`_. >------------------- >### 3.36.1 >------------------- >This is a yak shaving release, mostly concerned with our own tests. >While :func:`~python:inspect.getfullargspec` was documented as deprecated >in Python 3.5, it never actually emitted a warning. Our code to silence >this (nonexistent) warning has therefore been removed. >We now run our tests with ``DeprecationWarning`` as an error, and made some >minor changes to our own tests as a result. This required similar upstream >updates to :pypi:`coverage` and :pypi:`execnet` (a test-time dependency via >:pypi:`pytest-xdist`). >There is no user-visible change in Hypothesis itself, but we encourage you >to consider enabling deprecations as errors in your own tests. >------------------- >### 3.36.0 >------------------- >This release adds a setting to the public API, and does some internal cleanup: >- The :attr:`~hypothesis.settings.derandomize` setting is now documented (:issue:`890`) >- Removed - and disallowed - all 'bare excepts' in Hypothesis (:issue:`953`) >- Documented the :attr:`~hypothesis.settings.strict` setting as deprecated, and > updated the build so our docs always match deprecations in the code. >------------------- >### 3.35.0 >------------------- >This minor release supports constraining :func:`~hypothesis.strategies.uuids` >to generate :class:`~python:uuid.UUID`s of a particular version. >(:issue:`721`) >Thanks to Dion Misic for this feature. >------------------- >### 3.34.1 >------------------- >This patch updates the documentation to suggest >:func:`builds(callable) <hypothesis.strategies.builds>` instead of >:func:`just(callable()) <hypothesis.strategies.just>`. >------------------- >### 3.34.0 >------------------- >Hypothesis now emits deprecation warnings if you apply >:func:`given <hypothesis.given>` more than once to a target. >Applying :func:`given <hypothesis.given>` repeatedly wraps the target multiple >times. Each wrapper will search the space of of possible parameters separately. >This is equivalent but will be much more inefficient than doing it with a >single call to :func:`given <hypothesis.given>`. >For example, instead of >``given(booleans()) given(integers())``, you could write >``given(booleans(), integers())`` >------------------- >### 3.33.1 >------------------- >This is a bugfix release: >- :func:`~hypothesis.strategies.builds` would try to infer a strategy for > required positional arguments of the target from type hints, even if they > had been given to :func:`~hypothesis.strategies.builds` as positional > arguments (:issue:`946`). Now it only infers missing required arguments. >- An internal introspection function wrongly reported ``self`` as a required > argument for bound methods, which might also have affected > :func:`~hypothesis.strategies.builds`. Now it knows better. >------------------- That's it for now! Happy merging! 🤖

170: Scheduled weekly dependency update for week 49 r=mithrandi a=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. <table align="center"> <tr> <td><b>cryptography</b></td> <td align="center">2.1.3</td> <td align="center">»</td> <td align="center">2.1.4</td> <td> <a href="https://pypi.python.org/pypi/cryptography">PyPI</a> | <a href="https://pyup.io/changelogs/cryptography/">Changelog</a> | <a href="https://github.com/pyca/cryptography">Repo</a> </td> <tr> <td><b>eliot</b></td> <td align="center">1.2.0</td> <td align="center">»</td> <td align="center">1.3.0</td> <td> <a href="https://pypi.python.org/pypi/eliot">PyPI</a> | <a href="https://pyup.io/changelogs/eliot/">Changelog</a> | <a href="https://github.com/ClusterHQ/eliot/">Repo</a> </td> <tr> <td><b>hypothesis</b></td> <td align="center">3.38.5</td> <td align="center">»</td> <td align="center">3.40.1</td> <td> <a href="https://pypi.python.org/pypi/hypothesis">PyPI</a> | <a href="https://pyup.io/changelogs/hypothesis/">Changelog</a> | <a href="https://github.com/HypothesisWorks/hypothesis/issues">Repo</a> </td> <tr> <td><b>pyopenssl</b></td> <td align="center">17.4.0</td> <td align="center">»</td> <td align="center">17.5.0</td> <td> <a href="https://pypi.python.org/pypi/pyopenssl">PyPI</a> | <a href="https://pyup.io/changelogs/pyopenssl/">Changelog</a> | <a href="https://pyopenssl.org/">Homepage</a> | <a href="http://pythonhosted.org/pyOpenSSL/">Docs</a> </td> </tr> </table> ## Changelogs ### eliot 1.2.0 -> 1.3.0 >### 1.3.0 ### hypothesis 3.38.5 -> 3.40.1 >### 3.40.1 >------------------- >This release makes two changes: >* It makes the calculation of some of the metadata that Hypothesis uses for > shrinking occur lazily. This should speed up performance of test case > generation a bit because it no longer calculates information it doesn't need. >* It improves the shrinker for certain classes of nested examples. e.g. when > shrinking lists of lists, the shrinker is now able to concatenate two > adjacent lists together into a single list. As a result of this change, > shrinking may get somewhat slower when the minimal example found is large. >------------------- >### 3.40.0 >------------------- >This release improves how various ways of seeding Hypothesis interact with the >example database: >* Using the example database with :func:`~hypothesis.seed` is now deprecated. > You should set ``database=None`` if you are doing that. This will only warn > if you actually load examples from the database while using ``seed``. >* The :attr:`~hypothesis.settings.derandomize` will behave the same way as > ``seed``. >* Using ``--hypothesis-seed`` will disable use of the database. >* If a test used examples from the database, it will not suggest using a seed > to reproduce it, because that won't work. >This work was funded by `Smarkets <https://smarkets.com/>`_. >------------------- >### 3.39.0 >------------------- >This release adds a new health check that checks if the smallest "natural" >possible example of your test case is very large - this will tend to cause >Hypothesis to generate bad examples and be quite slow. >This work was funded by `Smarkets <https://smarkets.com/>`_. >------------------- >### 3.38.9 >------------------- >This is a documentation release to improve the documentation of shrinking >behaviour for Hypothesis's strategies. >------------------- >### 3.38.8 >------------------- >This release improves the performance of >:func:`~hypothesis.strategies.characters` when using ``blacklist_characters`` >and :func:`~hypothesis.strategies.from_regex` when using negative character >classes. >The problems this fixes were found in the course of work funded by >`Smarkets <https://smarkets.com/>`_. >------------------- >### 3.38.7 >------------------- >This is a patch release for :func:`~hypothesis.strategies.from_regex`, which >had a bug in handling of the :obj:`python:re.VERBOSE` flag (:issue:`992`). >Flags are now handled correctly when parsing regex. >------------------- >### 3.38.6 >------------------- >This patch changes a few byte-string literals from double to single quotes, >thanks to an update in :pypi:`unify`. There are no user-visible changes. >------------------- ### pyopenssl 17.4.0 -> 17.5.0 >### 17.5.0 >------------------- >Backward-incompatible changes: >^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ >* The minimum ``cryptography`` version is now 2.1.4. >Deprecations: >^^^^^^^^^^^^^ >*none* >Changes: >^^^^^^^^ >- Fixed a potential use-after-free in the verify callback and resolved a memory leak when loading PKCS12 files with ``cacerts``. > `723 <https://github.com/pyca/pyopenssl/pull/723>`_ >- Added ``Connection.export_keying_material`` for RFC 5705 compatible export of keying material. > `725 <https://github.com/pyca/pyopenssl/pull/725>`_ >---- That's it for now! Happy merging! 🤖

174: Scheduled weekly dependency update for week 00 r=mithrandi a=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. <table align="center"> <tr> <td><b>asn1crypto</b></td> <td align="center">0.23.0</td> <td align="center">»</td> <td align="center">0.24.0</td> <td> <a href="https://pypi.python.org/pypi/asn1crypto">PyPI</a> | <a href="https://pyup.io/changelogs/asn1crypto/">Changelog</a> | <a href="https://github.com/wbond/asn1crypto/issues">Repo</a> </td> <tr> <td><b>attrs</b></td> <td align="center">17.3.0</td> <td align="center">»</td> <td align="center">17.4.0</td> <td> <a href="https://pypi.python.org/pypi/attrs">PyPI</a> | <a href="https://pyup.io/changelogs/attrs/">Changelog</a> | <a href="http://www.attrs.org/">Homepage</a> </td> <tr> <td><b>hypothesis</b></td> <td align="center">3.40.1</td> <td align="center">»</td> <td align="center">3.44.4</td> <td> <a href="https://pypi.python.org/pypi/hypothesis">PyPI</a> | <a href="https://pyup.io/changelogs/hypothesis/">Changelog</a> | <a href="https://github.com/HypothesisWorks/hypothesis/issues">Repo</a> </td> <tr> <td><b>ipaddress</b></td> <td align="center">1.0.18</td> <td align="center">»</td> <td align="center">1.0.19</td> <td> <a href="https://pypi.python.org/pypi/ipaddress">PyPI</a> | <a href="https://github.com/phihag/ipaddress">Repo</a> </td> <tr> <td><b>pyrsistent</b></td> <td align="center">0.14.1</td> <td align="center">»</td> <td align="center">0.14.2</td> <td> <a href="https://pypi.python.org/pypi/pyrsistent">PyPI</a> | <a href="https://pyup.io/changelogs/pyrsistent/">Changelog</a> | <a href="http://github.com/tobgu/pyrsistent/">Repo</a> </td> <tr> <td><b>toolz</b></td> <td align="center">0.8.2</td> <td align="center">»</td> <td align="center">0.9.0</td> <td> <a href="https://pypi.python.org/pypi/toolz">PyPI</a> | <a href="https://github.com/pytoolz/toolz">Repo</a> </td> </tr> </table> ## Changelogs ### asn1crypto 0.23.0 -> 0.24.0 >### 0.24.0 > - `x509.Certificate().self_signed` will no longer return `"yes"` under any > circumstances. This helps prevent confusion since the library does not > verify the signature. Instead a library like oscrypto should be used > to confirm if a certificate is self-signed. > - Added various OIDs to `x509.KeyPurposeId()` > - Added `x509.Certificate().private_key_usage_period_value` > - Added structures for parsing common subject directory attributes for > X.509 certificates, including `x509.SubjectDirectoryAttribute()` > - Added `algos.AnyAlgorithmIdentifier()` for situations where an > algorithm identifier may contain a digest, signed digest or encryption > algorithm OID > - Fixed a bug with `x509.Certificate().subject_directory_attributes_value` > not returning the correct value > - Fixed a bug where explicitly-tagged fields in a `core.Sequence()` would > not function properly when the field had a default value > - Fixed a bug with type checking in `pem.armor()` ### attrs 17.3.0 -> 17.4.0 >### 17.4.0 >------------------- >Backward-incompatible Changes >^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ >- The traversal of MROs when using multiple inheritance was backward: > If you defined a class ``C`` that subclasses ``A`` and ``B`` like ``C(A, B)``, ``attrs`` would have collected the attributes from ``B`` *before* those of ``A``. > This is now fixed and means that in classes that employ multiple inheritance, the output of ``__repr__`` and the order of positional arguments in ``__init__`` changes. > Due to the nature of this bug, a proper deprecation cycle was unfortunately impossible. > Generally speaking, it's advisable to prefer ``kwargs``-based initialization anyways – *especially* if you employ multiple inheritance and diamond-shaped hierarchies. > `298 <https://github.com/python-attrs/attrs/issues/298>`_, > `299 <https://github.com/python-attrs/attrs/issues/299>`_, > `304 <https://github.com/python-attrs/attrs/issues/304>`_ >- The ``__repr__`` set by ``attrs`` > no longer produces an ``AttributeError`` > when the instance is missing some of the specified attributes > (either through deleting > or after using ``init=False`` on some attributes). > This can break code > that relied on ``repr(attr_cls_instance)`` raising ``AttributeError`` > to check if any attr-specified members were unset. > If you were using this, > you can implement a custom method for checking this:: > def has_unset_members(self): > for field in attr.fields(type(self)): > try: > getattr(self, field.name) > except AttributeError: > return True > return False > `308 <https://github.com/python-attrs/attrs/issues/308>`_ >Deprecations >^^^^^^^^^^^^ >- The ``attr.ib(convert=callable)`` option is now deprecated in favor of ``attr.ib(converter=callable)``. > This is done to achieve consistency with other noun-based arguments like *validator*. > *convert* will keep working until at least January 2019 while raising a ``DeprecationWarning``. > `307 <https://github.com/python-attrs/attrs/issues/307>`_ >Changes >^^^^^^^ >- Generated ``__hash__`` methods now hash the class type along with the attribute values. > Until now the hashes of two classes with the same values were identical which was a bug. > The generated method is also *much* faster now. > `261 <https://github.com/python-attrs/attrs/issues/261>`_, > `295 <https://github.com/python-attrs/attrs/issues/295>`_, > `296 <https://github.com/python-attrs/attrs/issues/296>`_ >- ``attr.ib``\ ’s ``metadata`` argument now defaults to a unique empty ``dict`` instance instead of sharing a common empty ``dict`` for all. > The singleton empty ``dict`` is still enforced. > `280 <https://github.com/python-attrs/attrs/issues/280>`_ >- ``ctypes`` is optional now however if it's missing, a bare ``super()`` will not work in slots classes. > This should only happen in special environments like Google App Engine. > `284 <https://github.com/python-attrs/attrs/issues/284>`_, > `286 <https://github.com/python-attrs/attrs/issues/286>`_ >- The attribute redefinition feature introduced in 17.3.0 now takes into account if an attribute is redefined via multiple inheritance. > In that case, the definition that is closer to the base of the class hierarchy wins. > `285 <https://github.com/python-attrs/attrs/issues/285>`_, > `287 <https://github.com/python-attrs/attrs/issues/287>`_ >- Subclasses of ``auto_attribs=True`` can be empty now. > `291 <https://github.com/python-attrs/attrs/issues/291>`_, > `292 <https://github.com/python-attrs/attrs/issues/292>`_ >- Equality tests are *much* faster now. > `306 <https://github.com/python-attrs/attrs/issues/306>`_ >- All generated methods now have correct ``__module__``, ``__name__``, and (on Python 3) ``__qualname__`` attributes. > `309 <https://github.com/python-attrs/attrs/issues/309>`_ >---- ### hypothesis 3.40.1 -> 3.44.4 >### 3.44.4 >------------------- >This release fixes :issue:`1044`, which slowed tests by up to 6% >due to broken caching. >------------------- >### 3.44.3 >------------------- >This release improves the shrinker in cases where examples drawn earlier can >affect how much data is drawn later (e.g. when you draw a length parameter in >a composite and then draw that many elements). Examples found in cases like >this should now be much closer to minimal. >------------------- >### 3.44.2 >------------------- >This is a pure refactoring release which changes how Hypothesis manages its >set of examples internally. It should have no externally visible effects. >------------------- >### 3.44.1 >------------------- >This release fixes :issue:`997`, in which under some circumstances the body of >tests run under Hypothesis would not show up when run under coverage even >though the tests were run and the code they called outside of the test file >would show up normally. >------------------- >### 3.44.0 >------------------- >This release adds a new feature: The :ref:`reproduce_failure <reproduce_failure>`, >designed to make it easy to use Hypothesis's binary format for examples to >reproduce a problem locally without having to share your example database >between machines. >This also changes when seeds are printed: >* They will no longer be printed for > normal falsifying examples, as there are now adequate ways of reproducing those > for all cases, so it just contributes noise. >* They will once again be printed when reusing examples from the database, as > health check failures should now be more reliable in this scenario so it will > almost always work in this case. >This work was funded by `Smarkets <https://smarkets.com/>`_. >------------------- >### 3.43.1 >------------------- >This release fixes a bug with Hypothesis's database management - examples that >were found in the course of shrinking were saved in a way that indicated that >they had distinct causes, and so they would all be retried on the start of the >next test. The intended behaviour, which is now what is implemented, is that >only a bounded subset of these examples would be retried. >------------------- >### 3.43.0 >------------------- >:exc:`~hypothesis.errors.HypothesisDeprecationWarning` now inherits from >:exc:`python:FutureWarning` instead of :exc:`python:DeprecationWarning`, >as recommended by :pep:`565` for user-facing warnings (:issue:`618`). >If you have not changed the default warnings settings, you will now see >each distinct :exc:`~hypothesis.errors.HypothesisDeprecationWarning` >instead of only the first. >------------------- >### 3.42.2 >------------------- >This patch fixes :issue:`1017`, where instances of a list or tuple subtype >used as an argument to a strategy would be coerced to tuple. >------------------- >### 3.42.1 >------------------- >This release has some internal cleanup, which makes reading the code >more pleasant and may shrink large examples slightly faster. >------------------- >### 3.42.0 >------------------- >This release deprecates :ref:`faker-extra`, which was designed as a transition >strategy but does not support example shrinking or coverage-guided discovery. >------------------- >### 3.41.0 >------------------- >:func:`~hypothesis.strategies.sampled_from` can now sample from >one-dimensional numpy ndarrays. Sampling from multi-dimensional >ndarrays still results in a deprecation warning. Thanks to Charlie >Tanksley for this patch. >------------------- ### pyrsistent 0.14.1 -> 0.14.2 >### 0.14.2 > * Fix 121, regression in PClass.set() introduced in 0.14.1. That's it for now! Happy merging! 🤖

175: Scheduled weekly dependency update for week 01 r=mithrandi a=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. <table align="center"> <tr> <td><b>hypothesis</b></td> <td align="center">3.44.4</td> <td align="center">»</td> <td align="center">3.44.13</td> <td> <a href="https://pypi.python.org/pypi/hypothesis">PyPI</a> | <a href="https://pyup.io/changelogs/hypothesis/">Changelog</a> | <a href="https://github.com/HypothesisWorks/hypothesis/issues">Repo</a> </td> </tr> </table> ## Changelogs ### hypothesis 3.44.4 -> 3.44.13 >### 3.44.13 >-------------------- >This release changes the average bit length of values drawn from >:func:`~hypothesis.strategies.integers` to be much smaller. Additionally it >changes the shrinking order so that now size is considered before sign - e.g. >-1 will be preferred to +10. >The new internal format for integers required some changes to the minimizer to >make work well, so you may also see some improvements to example quality in >unrelated areas. >-------------------- >### 3.44.12 >-------------------- >This changes Hypothesis's internal implementation of weighted sampling. This >will affect example distribution and quality, but you shouldn't see any other >effects. >-------------------- >### 3.44.11 >-------------------- >This is a change to some internals around how Hypothesis handles avoiding >generating duplicate examples and seeking out novel regions of the search >space. >You are unlikely to see much difference as a result of it, but it fixes >a bug where an internal assertion could theoretically be triggered and has some >minor effects on the distribution of examples so could potentially find bugs >that have previously been missed. >-------------------- >### 3.44.10 >-------------------- >This patch avoids creating debug statements when debugging is disabled. >Profiling suggests this is a 5-10% performance improvement (:issue:`1040`). >------------------- >### 3.44.9 >------------------- >This patch blacklists null characters (``'\x00'``) in automatically created >strategies for Django :obj:`~django:django.db.models.CharField` and >:obj:`~django:django.db.models.TextField`, due to a database issue which >`was recently fixed upstream <https://code.djangoproject.com/ticket/28201>`_ >(Hypothesis :issue:`1045`). >------------------- >### 3.44.8 >------------------- >This release makes the Hypothesis shrinker slightly less greedy in order to >avoid local minima - when it gets stuck, it makes a small attempt to search >around the final example it would previously have returned to find a new >starting point to shrink from. This should improve example quality in some >cases, especially ones where the test data has dependencies among parts of it >that make it difficult for Hypothesis to proceed. >------------------- >### 3.44.7 >------------------- >This release adds support for `Django 2 ><https://www.djangoproject.com/weblog/2017/dec/02/django-20-released/>`_ in >the hypothesis-django extra. >This release drops support for Django 1.10, as it is no longer supported by >the Django team. >------------------- >### 3.44.6 >------------------- >This release speeds up test case reduction in many examples by being better at >detecting large shrinks it can use to discard redundant parts of its input. >This will be particularly noticeable in examples that make use of filtering >and for some integer ranges. >------------------- >### 3.44.5 >------------------- >Happy new year! >This is a no-op release that updates the year range on all of >the copyright headers in our source to include 2018. >------------------- That's it for now! Happy merging! 🤖

184: Scheduled weekly dependency update for week 09 r=mithrandi a=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. <table align="center"> <tr> <td><b>hyperlink</b></td> <td align="center">17.3.1</td> <td align="center">»</td> <td align="center">18.0.0</td> <td> <a href="https://pypi.python.org/pypi/hyperlink">PyPI</a> | <a href="https://pyup.io/changelogs/hyperlink/">Changelog</a> | <a href="https://github.com/python-hyper/hyperlink">Repo</a> </td> <tr> <td><b>hypothesis</b></td> <td align="center">3.44.16</td> <td align="center">»</td> <td align="center">3.48.0</td> <td> <a href="https://pypi.python.org/pypi/hypothesis">PyPI</a> | <a href="https://pyup.io/changelogs/hypothesis/">Changelog</a> | <a href="https://github.com/HypothesisWorks/hypothesis/issues">Repo</a> </td> </tr> </table> ## Changelogs ### hypothesis 3.44.16 -> 3.48.0 >### 3.48.0 >------------------- >This release improves some "unhappy paths" when using Hypothesis >with the standard library :mod:`python:unittest` module: >- Applying :func:`given <hypothesis.given>` to a non-test method which is > overridden from :class:`python:unittest.TestCase`, such as ``setUp``, > raises :attr:`a new health check <hypothesis.settings.not_a_test_method>`. > (:issue:`991`) >- Using :meth:`~python:unittest.TestCase.subTest` within a test decorated > with :func:`given <hypothesis.given>` would leak intermediate results > when tests were run under the :mod:`python:unittest` test runner. > Individual reporting of failing subtests is now disabled during a test > using :func:`given <hypothesis.given>`. (:issue:`1071`) >- :func:`given <hypothesis.given>` is still not a class decorator, but the > error message if you try using it on a class has been improved. >As a related improvement, using :class:`django:django.test.TestCase` with >:func:`given <hypothesis.given>` instead of >:class:`hypothesis.extra.django.TestCase` raises an explicit error instead >of running all examples in a single database transaction. >------------------- >### 3.47.0 >------------------- >:obj:`~hypothesis.settings.register_profile` now accepts keyword arguments >for specific settings, and the parent settings object is now optional. >Using a ``name`` for a registered profile which is not a string was never >suggested, but it is now also deprecated and will eventually be an error. >------------------- >### 3.46.2 >------------------- >This release removes an unnecessary branch from the code, and has no user-visible impact. >------------------- >### 3.46.1 >------------------- >This changes only the formatting of our docstrings and should have no user-visible effects. >------------------- >### 3.46.0 >------------------- >:func:`~hypothesis.strategies.characters` has improved docs about >what arguments are valid, and additional validation logic to raise a >clear error early (instead of e.g. silently ignoring a bad argument). >Categories may be specified as the Unicode 'general category' >(eg ``u'Nd'``), or as the 'major category' (eg ``[u'N', u'Lu']`` >is equivalent to ``[u'Nd', u'Nl', u'No', u'Lu']``). >In previous versions, general categories were supported and all other >input was silently ignored. Now, major categories are supported in >addition to general categories (which may change the behaviour of some >existing code), and all other input is deprecated. >------------------- >### 3.45.5 >------------------- >This patch improves strategy inference in :mod:`hypothesis.extra.django` >to account for some validators in addition to field type - see >:issue:`1116` for ongoing work in this space. >Specifically, if a :class:`~django:django.db.models.CharField` or >:class:`~django:django.db.models.TextField` has an attached >:class:`~django:django.core.validators.RegexValidator`, we now use >:func:`~hypothesis.strategies.from_regex` instead of >:func:`~hypothesis.strategies.text` as the underlying strategy. >This allows us to generate examples of the default >:class:`~django:django.contrib.auth.models.User` model, closing :issue:`1112`. >------------------- >### 3.45.4 >------------------- >This patch improves some internal debugging information, fixes >a typo in a validation error message, and expands the documentation >for new contributors. >------------------- >### 3.45.3 >------------------- >This patch may improve example shrinking slightly for some strategies. >------------------- >### 3.45.2 >------------------- >This release makes our docstring style more consistent, thanks to >:pypi:`flake8-docstrings`. There are no user-visible changes. >------------------- >### 3.45.1 >------------------- >This fixes an indentation issue in docstrings for >:func:`~hypothesis.strategies.datetimes`, :func:`~hypothesis.strategies.dates`, >:func:`~hypothesis.strategies.times`, and >:func:`~hypothesis.strategies.timedeltas`. >------------------- >### 3.45.0 >------------------- >This release fixes :func:`~hypothesis.strategies.builds` so that ``target`` >can be used as a keyword argument for passing values to the target. The target >itself can still be specified as a keyword argument, but that behavior is now >deprecated. The target should be provided as the first positional argument. >-------------------- >### 3.44.26 >-------------------- >This release fixes some formatting issues in the Hypothesis source code. >It should have no externally visible effects. >-------------------- >### 3.44.25 >-------------------- >This release changes the way in which Hypothesis tries to shrink the size of >examples. It probably won't have much impact, but might make shrinking faster >in some cases. It is unlikely but not impossible that it will change the >resulting examples. >-------------------- >### 3.44.24 >-------------------- >This release fixes dependency information when installing Hypothesis >from a binary "wheel" distribution. >- The ``install_requires`` for :pypi:`enum34` is resolved at install > time, rather than at build time (with potentially different results). >- Django has fixed their ``python_requires`` for versions 2.0.0 onward, > simplifying Python2-compatible constraints for downstream projects. >-------------------- >### 3.44.23 >-------------------- >This release improves shrinking in a class of pathological examples that you >are probably never hitting in practice. If you *are* hitting them in practice >this should be a significant speed up in shrinking. If you are not, you are >very unlikely to notice any difference. You might see a slight slow down and/or >slightly better falsifying examples. >-------------------- >### 3.44.22 >-------------------- >This release fixes a dependency problem. It was possible to install >Hypothesis with an old version of :pypi:`attrs`, which would throw a >``TypeError`` as soon as you tried to import hypothesis. Specifically, you >need attrs 16.0.0 or newer. >Hypothesis will now require the correct version of attrs when installing. >-------------------- >### 3.44.21 >-------------------- >This change adds some additional structural information that Hypothesis will >use to guide its search. >You mostly shouldn't see much difference from this. The two most likely effects >you would notice are: >1. Hypothesis stores slightly more examples in its database for passing tests. >2. Hypothesis *may* find new bugs that it was previously missing, but it > probably won't (this is a basic implementation of the feature that is > intended to support future work. Although it is useful on its own, it's not > *very* useful on its own). >-------------------- >### 3.44.20 >-------------------- >This is a small refactoring release that changes how Hypothesis tracks some >information about the boundary of examples in its internal representation. >You are unlikely to see much difference in behaviour, but memory usage and >run time may both go down slightly during normal test execution, and when >failing Hypothesis might print its failing example slightly sooner. >-------------------- >### 3.44.19 >-------------------- >This changes how we compute the default ``average_size`` for all collection >strategies. Previously setting a ``max_size`` without setting an >``average_size`` would have the seemingly paradoxical effect of making data >generation *slower*, because it would raise the average size from its default. >Now setting ``max_size`` will either leave the default unchanged or lower it >from its default. >If you are currently experiencing this problem, this may make your tests >substantially faster. If you are not, this will likely have no effect on you. >-------------------- >### 3.44.18 >-------------------- >This is a small refactoring release that changes how Hypothesis detects when >the structure of data generation depends on earlier values generated (e.g. when >using :ref:`flatmap <flatmap>` or :func:`~hypothesis.strategies.composite`). >It should not have any observable effect on behaviour. >-------------------- >### 3.44.17 >-------------------- >This release fixes a typo in internal documentation, and has no user-visible impact. >-------------------- That's it for now! Happy merging! 🤖

188: Scheduled weekly dependency update for week 13 r=mithrandi a=pyup-bot ### Update [cryptography](https://pypi.python.org/pypi/cryptography) from **2.1.4** to **2.2.2**. <details> <summary>Changelog</summary> ### 2.2.1 ``` ~~~~~~~~~~~~~~~~~~ * Reverted a change to ``GeneralNames`` which prohibited having zero elements, due to breakages. * Fixed a bug in :func:`~cryptography.hazmat.primitives.keywrap.aes_key_unwrap_with_padding` that caused it to raise ``InvalidUnwrap`` when key length modulo 8 was zero. .. _v2-2: ``` ### 2.2 ``` ~~~~~~~~~~~~~~~~ * **BACKWARDS INCOMPATIBLE:** Support for Python 2.6 has been dropped. * Resolved a bug in ``HKDF`` that incorrectly constrained output size. * Added :class:`~cryptography.hazmat.primitives.asymmetric.ec.BrainpoolP256R1`, :class:`~cryptography.hazmat.primitives.asymmetric.ec.BrainpoolP384R1`, and :class:`~cryptography.hazmat.primitives.asymmetric.ec.BrainpoolP512R1` to support inter-operating with systems like German smart meters. * Added token rotation support to :doc:`Fernet </fernet>` with :meth:`~cryptography.fernet.MultiFernet.rotate`. * Fixed a memory leak in :func:`~cryptography.hazmat.primitives.asymmetric.ec.derive_private_key`. * Added support for AES key wrapping with padding via :func:`~cryptography.hazmat.primitives.keywrap.aes_key_wrap_with_padding` and :func:`~cryptography.hazmat.primitives.keywrap.aes_key_unwrap_with_padding` . * Allow loading DSA keys with 224 bit ``q``. .. _v2-1-4: ``` </details> <details> <summary>Links</summary> - PyPI: https://pypi.python.org/pypi/cryptography - Changelog: https://pyup.io/changelogs/cryptography/ - Repo: https://github.com/pyca/cryptography </details> ### Update [hypothesis](https://pypi.python.org/pypi/hypothesis) from **3.48.0** to **3.53.0**. <details> <summary>Changelog</summary> ### 3.53.0 ``` ------------------- This release removes support for Django 1.8, which reached end of life on 2018-04-01. `You can see Django's release and support schedule `on the Django Project website <https://www.djangoproject.com/download/supported-versions>`_. ------------------- ``` ### 3.52.3 ``` ------------------- This patch fixes the :obj:`~hypothesis.settings.min_satisfying_examples` settings documentation, by explaining that example shrinking is tracked at the level of the underlying bytestream rather than the output value. The output from :func:`~hypothesis.find` in verbose mode has also been adjusted - see :ref:`the example session <verbose-output>` - to avoid duplicating lines when the example repr is constant, even if the underlying representation has been shrunken. ------------------- ``` ### 3.52.2 ``` ------------------- This release improves the output of failures with :ref:`rule based stateful testing <rulebasedstateful>` in two ways: * The output from it is now usually valid Python code. * When the same value has two different names because it belongs to two different bundles, it will now display with the name associated with the correct bundle for a rule argument where it is used. ------------------- ``` ### 3.52.1 ``` ------------------- This release improves the behaviour of :doc:`stateful testing <stateful>` in two ways: * Previously some runs would run no steps (:issue:`376`). This should no longer happen. * RuleBasedStateMachine tests which used bundles extensively would often shrink terribly. This should now be significantly improved, though there is likely a lot more room for improvement. This release also involves a low level change to how ranges of integers are handles which may result in other improvements to shrink quality in some cases. ------------------- ``` ### 3.52.0 ``` ------------------- This release deprecates use of :func:`settings(...) <hypothesis.settings>` as a decorator, on functions or methods that are not also decorated with :func:`given <hypothesis.given>`. You can still apply these decorators in any order, though you should only do so once each. Applying :func:`given <hypothesis.given>` twice was already deprecated, and applying :func:`settings(...) <hypothesis.settings>` twice is deprecated in this release and will become an error in a future version. Neither could ever be used twice to good effect.) Using :func:`settings(...) <hypothesis.settings>` as the sole decorator on a test is completely pointless, so this common usage error will become an error in a future version of Hypothesis. ------------------- ``` ### 3.51.0 ``` ------------------- This release deprecates the ``average_size`` argument to :func:`~hypothesis.strategies.lists` and other collection strategies. You should simply delete it wherever it was used in your tests, as it no longer has any effect. In early versions of Hypothesis, the ``average_size`` argument was treated as a hint about the distribution of examples from a strategy. Subsequent improvements to the conceptual model and the engine for generating and shrinking examples mean it is more effective to simply describe what constitutes a valid example, and let our internals handle the distribution. ------------------- ``` ### 3.50.3 ``` ------------------- This patch contains some internal refactoring so that we can run with warnings as errors in CI. ------------------- ``` ### 3.50.2 ``` ------------------- This has no user-visible changes except one slight formatting change to one docstring, to avoid a deprecation warning. ------------------- ``` ### 3.50.1 ``` ------------------- This patch fixes an internal error introduced in 3.48.0, where a check for the Django test runner would expose import-time errors in Django configuration (:issue:`1167`). ------------------- ``` ### 3.50.0 ``` ------------------- This release improves validation of numeric bounds for some strategies. - :func:`~hypothesis.strategies.integers` and :func:`~hypothesis.strategies.floats` now raise ``InvalidArgument`` if passed a ``min_value`` or ``max_value`` which is not an instance of :class:`~python:numbers.Real`, instead of various internal errors. - :func:`~hypothesis.strategies.floats` now converts its bounding values to the nearest float above or below the min or max bound respectively, instead of just casting to float. The old behaviour was incorrect in that you could generate ``float(min_value)``, even when this was less than ``min_value`` itself (possible with eg. fractions). - When both bounds are provided to :func:`~hypothesis.strategies.floats` but there are no floats in the interval, such as ``[(2**54)+1 .. (2**55)-1]``, InvalidArgument is raised. - :func:`~hypothesis.strategies.decimals` gives a more useful error message if passed a string that cannot be converted to :class:`~python:decimal.Decimal` in a context where this error is not trapped. Code that previously **seemed** to work may be explicitly broken if there were no floats between ``min_value`` and ``max_value`` (only possible with non-float bounds), or if a bound was not a :class:`~python:numbers.Real` number but still allowed in :obj:`python:math.isnan` (some custom classes with a ``__float__`` method). ------------------- ``` ### 3.49.1 ``` ------------------- This patch fixes our tests for Numpy dtype strategies on big-endian platforms, where the strategy behaved correctly but the test assumed that the native byte order was little-endian. There is no user impact unless you are running our test suite on big-endian platforms. Thanks to Graham Inggs for reporting :issue:`1164`. ------------------- ``` ### 3.49.0 ``` ------------------- This release deprecates passing ``elements=None`` to collection strategies, such as :func:`~hypothesis.strategies.lists`. Requiring ``lists(nothing())`` or ``builds(list)`` instead of ``lists()`` means slightly more typing, but also improves the consistency and discoverability of our API - as well as showing how to compose or construct strategies in ways that still work in more complex situations. Passing a nonzero max_size to a collection strategy where the elements strategy contains no values is now deprecated, and will be an error in a future version. The equivalent with ``elements=None`` is already an error. ------------------- ``` ### 3.48.1 ``` ------------------- This patch will minimize examples that would come out non-minimal in previous versions. Thanks to Kyle Reeve for this patch. ------------------- ``` </details> <details> <summary>Links</summary> - PyPI: https://pypi.python.org/pypi/hypothesis - Changelog: https://pyup.io/changelogs/hypothesis/ - Repo: https://github.com/HypothesisWorks/hypothesis/issues </details> ### Update [pbr](https://pypi.python.org/pypi/pbr) from **3.1.1** to **4.0.0**. *The bot wasn't able to find a changelog for this release. [Got an idea?](https://github.com/pyupio/changelogs/issues/new)* <details> <summary>Links</summary> - PyPI: https://pypi.python.org/pypi/pbr - Homepage: https://docs.openstack.org/pbr/latest/ </details>

193: Scheduled weekly dependency update for week 18 r=mithrandi a=pyup-bot ### Update [attrs](https://pypi.org/project/attrs) from **17.4.0** to **18.1.0**. <details> <summary>Changelog</summary> ### 18.1.0 ``` ------------------- Changes ^^^^^^^ - ``x=X(); x.cycle = x; repr(x)`` will no longer raise a ``RecursionError``, and will instead show as ``X(x=...)``. `95 <https://github.com/python-attrs/attrs/issues/95>`_ - ``attr.ib(factory=f)`` is now syntactic sugar for the common case of ``attr.ib(default=attr.Factory(f))``. `178 <https://github.com/python-attrs/attrs/issues/178>`_, `356 <https://github.com/python-attrs/attrs/issues/356>`_ - Added ``attr.field_dict()`` to return an ordered dictionary of ``attrs`` attributes for a class, whose keys are the attribute names. `290 <https://github.com/python-attrs/attrs/issues/290>`_, `349 <https://github.com/python-attrs/attrs/issues/349>`_ - The order of attributes that are passed into ``attr.make_class()`` or the ``these`` argument of ``attr.s()`` is now retained if the dictionary is ordered (i.e. ``dict`` on Python 3.6 and later, ``collections.OrderedDict`` otherwise). Before, the order was always determined by the order in which the attributes have been defined which may not be desirable when creating classes programatically. `300 <https://github.com/python-attrs/attrs/issues/300>`_, `339 <https://github.com/python-attrs/attrs/issues/339>`_, `343 <https://github.com/python-attrs/attrs/issues/343>`_ - In slotted classes, ``__getstate__`` and ``__setstate__`` now ignore the ``__weakref__`` attribute. `311 <https://github.com/python-attrs/attrs/issues/311>`_, `326 <https://github.com/python-attrs/attrs/issues/326>`_ - Setting the cell type is now completely best effort. This fixes ``attrs`` on Jython. We cannot make any guarantees regarding Jython though, because our test suite cannot run due to dependency incompatabilities. `321 <https://github.com/python-attrs/attrs/issues/321>`_, `334 <https://github.com/python-attrs/attrs/issues/334>`_ - If ``attr.s`` is passed a *these* argument, it will not attempt to remove attributes with the same name from the class body anymore. `322 <https://github.com/python-attrs/attrs/issues/322>`_, `323 <https://github.com/python-attrs/attrs/issues/323>`_ - The hash of ``attr.NOTHING`` is now vegan and faster on 32bit Python builds. `331 <https://github.com/python-attrs/attrs/issues/331>`_, `332 <https://github.com/python-attrs/attrs/issues/332>`_ - The overhead of instantiating frozen dict classes is virtually eliminated. `336 <https://github.com/python-attrs/attrs/issues/336>`_ - Generated ``__init__`` methods now have an ``__annotations__`` attribute derived from the types of the fields. `363 <https://github.com/python-attrs/attrs/issues/363>`_ - We have restructured the documentation a bit to account for ``attrs``' growth in scope. Instead of putting everything into the `examples <http://www.attrs.org/en/stable/examples.html>`_ page, we have started to extract narrative chapters. So far, we've added chapters on `initialization <http://www.attrs.org/en/stable/init.html>`_ and `hashing <http://www.attrs.org/en/stable/hashing.html>`_. Expect more to come! `369 <https://github.com/python-attrs/attrs/issues/369>`_, `370 <https://github.com/python-attrs/attrs/issues/370>`_ ---- ``` </details> <details> <summary>Links</summary> - PyPI: https://pypi.org/project/attrs - Changelog: https://pyup.io/changelogs/attrs/ - Homepage: http://www.attrs.org/ </details> ### Update [hypothesis](https://pypi.org/project/hypothesis) from **3.53.0** to **3.56.5**. *The bot wasn't able to find a changelog for this release. [Got an idea?](https://github.com/pyupio/changelogs/issues/new)* <details> <summary>Links</summary> - PyPI: https://pypi.org/project/hypothesis - Repo: https://github.com/HypothesisWorks/hypothesis/issues </details> ### Update [ipaddress](https://pypi.org/project/ipaddress) from **1.0.19** to **1.0.21**. *The bot wasn't able to find a changelog for this release. [Got an idea?](https://github.com/pyupio/changelogs/issues/new)* <details> <summary>Links</summary> - PyPI: https://pypi.org/project/ipaddress - Repo: https://github.com/phihag/ipaddress </details> ### Update [pbr](https://pypi.org/project/pbr) from **4.0.0** to **4.0.2**. *The bot wasn't able to find a changelog for this release. [Got an idea?](https://github.com/pyupio/changelogs/issues/new)* <details> <summary>Links</summary> - PyPI: https://pypi.org/project/pbr - Homepage: https://docs.openstack.org/pbr/latest/ </details> ### Update [twisted[tls]](https://pypi.org/project/twisted) from **17.9.0** to **18.4.0**. <details> <summary>Changelog</summary> ### 18.4.0 ``` =========================== Features -------- - The --port/--https arguments to web plugin are now deprecated, in favor of --listen. The --listen argument can be given multiple times to listen on multiple ports. (6670) - Twisted now requires zope.interface 4.4.2 or higher across all platforms and Python versions. (8149) - The osx_platform setuptools extra has been renamed to macos_platform, with the former name being a compatibility alias. (8848) - Zsh completions are now provided for the twist command. (9338) - twisted.internet.endpoints.HostnameEndpoint now has a __repr__ method which includes the host and port to which the endpoint connects. (9341) Bugfixes -------- - twistd now uses the UID's default GID to initialize groups when --uid is given but --gid is not. This prevents an unhandled TypeError from being raised when os.initgroups() is called. (4442) - twisted.protocols.basic.LineReceiver checks received lines' lengths against its MAX_LENGTH only after receiving a complete delimiter. A line ending in a multi-byte delimiter like '\r\n' might be split by the network, with the first part arriving before the rest; previously, LineReceiver erroneously disconnected if the first part, e.g. 'zzzz....\r' exceeded MAX_LENGTH. LineReceiver now checks received data against MAX_LENGTH plus the delimiter's length, allowing short reads to complete a line. (6556) - twisted.protocols.basic.LineOnlyReceiver disconnects the transport after receiving a line that exceeds MAX_LENGTH, like LineReceiver. (6557) - twisted.web.http.Request.getClientIP now returns the host part of the client's address when connected over IPv6. (7704) - twisted.application.service.IService is now documented as requiring the 'running', 'name' and 'parent' attributes (the documentation previously implied they were required, but was unclear). (7922) - twisted.web.wsgi.WSGIResource no longer raises an exception when a client connects over IPv6. (8241) - When using TLS enable automatic ECDH curve selection on OpenSSL 1.0.2+ instead of only supporting P-256 (9210) - twisted.trial._dist.worker and twisted.trial._dist.workertrial consistently pass bytes, not unicode to AMP. This fixes "trial -j" on Python 3. (9264) - twisted.trial.runner now uses the 'importlib' module instead of the 'imp' module on Python 3+. This eliminates DeprecationWarnings caused by importing 'imp' on Python 3. (9275) - twisted.web.client.HTTP11ClientProtocol now closes the connection when the server is sending a header line which is longer than he line limit of twisted.protocols.basic.LineReceiver.MAX_LENGTH. (9295) - twisted.python.failure now handles long stacktraces better; in particular it will log tracebacks for stack overflow errors. (9301) - The "--_shell-completion" argument to twistd now works on Python 3. (9303) - twisted.python.failure.Failure now raises the wrapped exception in Python3, and self (Failure) n Python2 when trap() is called without a matching exception (9307) - Writing large amounts of data no longer implies repeated, expensive copying under Python 3. Python 3's write speeds are now as fast as Python 2's. (9324) - twisted.protocols.postfix now properly encodes errors which are unicode strings to bytes. (9335) - twisted.protocols.policies.ProtocolWrapper and twisted.protocols.tls.TLSMemoryBIOProtocol no longer create circular references that keep protocol instances in memory after connection is closed. (9374) - twisted.conch.ssh.transport.SSHTransportBase no longer strips trailing spaces from the SSH version string of the connected peer. (9377) - `trial -j` no longer crashes on Python 2 on test failure messages containing non-ASCII bytes. (9378) - RSA keys replaced with 2048bit ones in twisted.conch.test.keydata in order to be compatible with OpenSSH 7.6. (9388) - AsyncioSelectorReactor uses the global policy's event loop. asyncio libraries that retrieve the running event loop with get_event_loop() will now receive the one used by AsyncioSelectorReactor. (9390) Improved Documentation ---------------------- - public attributes of `twisted.logger.Logger` are now documented as attributes. (8157) - List indentation formatting errors have been corrected throughout the documentation. (9256) Deprecations and Removals ------------------------- - twisted.protocols.basic.LineOnlyReceiver.lineLengthExceeded no longer returns twisted.internet.error.ConnectionLost. It instead directly disconnects the transport and returns None. (6557) - twisted.python.win32.getProgramsMenuPath and twisted.python.win32.getProgramFilesPath were deprecated in Twisted 15.3.0 and have now been removed. (9312) - Python 3.3 is no longer supported. (9352) Misc ---- - 7033, 8887, 9204, 9289, 9291, 9292, 9293, 9302, 9336, 9355, 9356, 9364, 9375, 9381, 9382, 9389, 9391, 9393, 9394, 9396 Conch ----- Bugfixes ~~~~~~~~ - twisted.plugins.cred_unix now properly converts a username and password from bytes to str on Python 3. In addition, passwords which are encrypted with SHA512 and SH256 are properly verified. This fixes running a conch server with: "twistd -n conch -d /etc/ssh/ --auth=unix". (9130) - In twisted.conch.scripts.conch, on Python 3 do not write bytes directly to sys.stderr. On Python 3, this fixes remote SSH execution of a command which fails. (9344) Deprecations and Removals ~~~~~~~~~~~~~~~~~~~~~~~~~ - twisted.conch.ssh.filetransfer.FileTransferClient.wasAFile attribute has been removed as it serves no purpose. (9362) - Removed deprecated support for PyCrypto key objects in conch (9368) Web --- Features ~~~~~~~~ - The new twisted.iweb.IRequest.getClientAddress returns the IAddress provider representing the client's address. Callers should check the type of the returned value before using it. (7707) - Eliminate use of twisted.python.log in twisted.web modules. (9280) Bugfixes ~~~~~~~~ - Scripts ending with .rpy, .epy, and .cgi now execute properly in Twisted Web on Python 3. (9271) - twisted.web.http.Request and twisted.web.server.Request are once again hashable on Python 2, fixing a regression introduced in Twisted 17.5.0. (9314) Improved Documentation ~~~~~~~~~~~~~~~~~~~~~~ - Correct reactor docstrings for twisted.web.client.Agent and twisted.web.client._StandardEndpointFactory to communicate interface requirements since 17.1. (9274) - The examples for the "Twisted Web in 60 Seconds" tutorial have been fixed to work on Python 3. (9285) Deprecations and Removals ~~~~~~~~~~~~~~~~~~~~~~~~~ - twisted.iweb.IRequest.getClientIP is deprecated. Use twisted.iweb.IRequest.getClientAddress instead (see 7707). (7705) - twisted.web.iweb.IRequest.getClient and its implementations (deprecated in 2552) have been removed. (9395) Mail ---- Bugfixes ~~~~~~~~ - twistd.mail.scripts.mailmail has been ported to Python 3. (8487) - twisted.mail.bounce now works on Python 3. (9260) - twisted.mail.pop3 and twisted.mail.pop3client now work on Python 3. (9269) - SMTP authentication in twisted.mail.smtp now works better on Python 3, due to improved improved bytes vs unicode handling. (9299) Misc ~~~~ - 9310 Words ----- No significant changes. Names ----- No significant changes. ``` </details> <details> <summary>Links</summary> - PyPI: https://pypi.org/project/twisted - Changelog: https://pyup.io/changelogs/twisted/ - Homepage: http://twistedmatrix.com/ - Bugtracker: https://twistedmatrix.com/trac/ </details> ### Update [zope.interface](https://pypi.org/project/zope.interface) from **4.4.3** to **4.5.0**. <details> <summary>Changelog</summary> ### 4.5.0 ``` ------------------ - Drop support for 3.3, avoid accidental dependence breakage via setup.py. See `PR 110 <https://github.com/zopefoundation/zope.interface/pull/110>`_. - Allow registering and unregistering instance methods as listeners. See `issue 12 <https://github.com/zopefoundation/zope.interface/issues/12>`_ and `PR 102 <https://github.com/zopefoundation/zope.interface/pull/102>`_. - Synchronize and simplify zope/__init__.py. See `issue 114 <https://github.com/zopefoundation/zope.interface/issues/114>`_ ``` </details> <details> <summary>Links</summary> - PyPI: https://pypi.org/project/zope.interface - Changelog: https://pyup.io/changelogs/zope.interface/ - Repo: https://github.com/zopefoundation/zope.interface </details>

209: Scheduled weekly dependency update for week 29 r=mithrandi a=pyup-bot ### Update [cryptography](https://pypi.org/project/cryptography) from **2.2.2** to **2.3**. <details> <summary>Changelog</summary> ### 2.3 ``` ~~~~~~~~~~~~~~~~ * **SECURITY ISSUE:** :meth:`~cryptography.hazmat.primitives.ciphers.AEADDecryptionContext.finalize_with_tag` allowed tag truncation by default which can allow tag forgery in some cases. The method now enforces the ``min_tag_length`` provided to the :class:`~cryptography.hazmat.primitives.ciphers.modes.GCM` constructor. * Added support for Python 3.7. * Added :meth:`~cryptography.fernet.Fernet.extract_timestamp` to get the authenticated timestamp of a :doc:`Fernet </fernet>` token. * Support for Python 2.7.x without ``hmac.compare_digest`` has been deprecated. We will require Python 2.7.7 or higher (or 2.7.6 on Ubuntu) in the next ``cryptography`` release. * Fixed multiple issues preventing ``cryptography`` from compiling against LibreSSL 2.7.x. * Added :class:`~cryptography.x509.CertificateRevocationList.get_revoked_certificate_by_serial_number` for quick serial number searches in CRLs. * The :class:`~cryptography.x509.RelativeDistinguishedName` class now preserves the order of attributes. Duplicate attributes now raise an error instead of silently discarding duplicates. * :func:`~cryptography.hazmat.primitives.keywrap.aes_key_unwrap` and :func:`~cryptography.hazmat.primitives.keywrap.aes_key_unwrap_with_padding` now raise :class:`~cryptography.hazmat.primitives.keywrap.InvalidUnwrap` if the wrapped key is an invalid length, instead of ``ValueError``. .. _v2-2-2: ``` </details> <details> <summary>Links</summary> - PyPI: https://pypi.org/project/cryptography - Changelog: https://pyup.io/changelogs/cryptography/ - Repo: https://github.com/pyca/cryptography </details> ### Update [eliot](https://pypi.org/project/eliot) from **1.3.0** to **1.5.0**. <details> <summary>Changelog</summary> </details> <details> <summary>Links</summary> - PyPI: https://pypi.org/project/eliot - Changelog: https://pyup.io/changelogs/eliot/ - Repo: https://github.com/ScatterHQ/eliot/ </details> ### Update [hypothesis](https://pypi.org/project/hypothesis) from **3.65.1** to **3.66.6**. *The bot wasn't able to find a changelog for this release. [Got an idea?](https://github.com/pyupio/changelogs/issues/new)* <details> <summary>Links</summary> - PyPI: https://pypi.org/project/hypothesis - Repo: https://github.com/HypothesisWorks/hypothesis/issues </details> ### Update [pbr](https://pypi.org/project/pbr) from **4.0.4** to **4.1.1**. *The bot wasn't able to find a changelog for this release. [Got an idea?](https://github.com/pyupio/changelogs/issues/new)* <details> <summary>Links</summary> - PyPI: https://pypi.org/project/pbr - Homepage: https://docs.openstack.org/pbr/latest/ </details> ### Update [prometheus-client](https://pypi.org/project/prometheus-client) from **0.2.0** to **0.3.0**. <details> <summary>Changelog</summary> ### 0.3.0 ``` [ENHANCEMENT] 4.5x speedup in parser 282 [ENHANCEMENT] Performance improvements for multiproc mode 266 [BUGFIX] Fix FD leak in multiproc mode 269 ``` </details> <details> <summary>Links</summary> - PyPI: https://pypi.org/project/prometheus-client - Changelog: https://pyup.io/changelogs/prometheus-client/ - Repo: https://github.com/prometheus/client_python </details> ### Update [pyrsistent](https://pypi.org/project/pyrsistent) from **0.14.3** to **0.14.4**. <details> <summary>Changelog</summary> ### 0.14.4 ``` * Fix 133, minor Python 3.7 compatibility issue. Pyrsistent is now officially Python 3.7 compliant! ``` </details> <details> <summary>Links</summary> - PyPI: https://pypi.org/project/pyrsistent - Changelog: https://pyup.io/changelogs/pyrsistent/ - Repo: http://github.com/tobgu/pyrsistent/ </details> ### Update [twisted[tls]](https://pypi.org/project/twisted) from **18.4.0** to **18.7.0**. <details> <summary>Changelog</summary> ### 18.7.0 ``` =========================== Features -------- - Cancelling a Deferred returned by twisted.internet.defer.inlineCallbacks now cancels the Deferred it is waiting on. (4632) - twisted.application.internet.ClientService now accepts a function to initialize or validate a connection before it is returned by the whenConnected method as the prepareConnection argument. (8375) - Traceback generated for twisted.internet.defer.inlineCallbacks now includes the full stack of inlineCallbacks generators between catcher and raiser (before it only contained raiser's stack). (9176) - Add optional cwd argument to twisted.runner.procmon.ProcMon.addProcess (9287) - twisted.python.failure.Failure tracebacks generated by coroutines scheduled with twisted.internet.defer.ensureDeferred - i.e. any Deferred-awaiting coroutine - now contain fewer extraneous frames from the trampoline implementation, and correctly indicate the source of exceptions raised in other call stacks - i.e. the function that raised the exception. In other words: if you 'await' a function that raises an exception, you'll be able to see where the error came from. (9459) Bugfixes -------- - On UNIX-like platforms, Twisted attempts to recover from EMFILE when accepting connections on TCP and UNIX ports by shedding incoming clients. (5368) - The documentation of IReactorTime.getDelayedCalls() has been corrected to indicate that the method returns a list, not a tuple. (9418) - "python -m twisted web --help" now refers to "--listen" instead of the non-existing "--http" (9434) - twisted.python.htmlizer.TokenPrinter now explicitly works on bytestrings. (9442) - twisted.enterprise.adbapi.ConnectionPool.runWithConnection and runInteraction now use the reactor that is passed to ConnectionPool's constructor. (9467) Improved Documentation ---------------------- - The Twisted Coding Standard now contains examples of how to mark up a feature as added in the next Twisted release. (9460) Deprecations and Removals ------------------------- - Deprecate direct introspection of ProcMon's processes: processes should not be directly accessed or pickled. (9287) - twisted.internet.address.IPv4Address._bwHack and twisted.internet.address.UNIXAddress._bwHack, as well as the parameters to the constructors, deprecated since Twisted 11.0, have been removed. (9450) Misc ---- - 7495, 9399, 9406, 9411, 9425, 9439, 9449, 9450, 9452 Conch ----- Features ~~~~~~~~ - twisted.conch.ssh.transport.SSHTransportBase now includes Twisted's version in the software version string it sends to the server, allowing servers to apply compatibility workarounds for bugs in particular client versions. (9424) Bugfixes ~~~~~~~~ - If the command run by twisted.conch.endpoints.SSHCommandClientEndpoint exits because of a delivered signal, the client protocol's connectionLost is now called with a ProcessTerminated exception instead of a ConnectionDone exception. (9412) - twisted.conch.ssh.transport.SSHTransportBase now correctly handles MSG_DEBUG with a false alwaysDisplay field on Python 2 (broken since 8.0.0). (9422) - twisted.conch.manhole.lastColorizedLine now does not throw a UnicodeDecodeError on non-ASCII input. (9442) Web --- Features ~~~~~~~~ - Added support for SameSite cookies in ``http.Request.addCookie``. (9387) Bugfixes ~~~~~~~~ - twisted.web.server.GzipEncoderFactory would sometimes fail to gzip requests if the Accept-Encoding header contained whitespace between the comma-separated acceptable encodings. It now trims whitespace before checking if gzip is an acceptable encoding. (9086) - twisted.web.static.File renders directory listings on Python 2, including those with text paths. (9438) - twisted.python.http.Request now correcly parses multipart bodies on Python 3.7. (9448) - twisted.web.http.combinedLogFormatter (used by t.w.http.Server and t.w.server.Site) no longer produces DeprecationWarning about Request.getClientIP. (9470) Misc ~~~~ - 9432, 9466, 9479, 9480 Mail ---- No significant changes. Words ----- No significant changes. Names ----- Misc ~~~~ - 9398 ``` </details> <details> <summary>Links</summary> - PyPI: https://pypi.org/project/twisted - Changelog: https://pyup.io/changelogs/twisted/ - Homepage: http://twistedmatrix.com/ - Bugtracker: https://twistedmatrix.com/trac/ </details> Co-authored-by: pyup-bot <github-bot@pyup.io>

[requires.io] dependency update

4de955c

mithrandi merged commit 2ff603e into master Apr 14, 2016

mithrandi deleted the requires-io-master branch April 14, 2016 08:07

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[requires.io] dependency update on master branch #39

[requires.io] dependency update on master branch #39

mithrandi commented Apr 14, 2016

codecov-io commented Apr 14, 2016

mithrandi commented Apr 14, 2016

[requires.io] dependency update on master branch #39

[requires.io] dependency update on master branch #39

Conversation

mithrandi commented Apr 14, 2016

codecov-io commented Apr 14, 2016

Current coverage is 100.00%

mithrandi commented Apr 14, 2016

Current coverage is `100.00%`