Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Scheduled weekly dependency update for week 40 #155

Merged
merged 9 commits into from
Oct 2, 2017

Conversation

pyup-bot
Copy link
Contributor

@pyup-bot pyup-bot commented Oct 2, 2017

Updates

Here's a list of all the updates bundled in this pull request. I've added some links to make it easier for you to find all the information you need.

asn1crypto 0.22.0 » 0.23.0 PyPI | Changelog | Repo
cffi 1.10.0 » 1.11.0 PyPI | Changelog | Docs
lxml 3.8.0 » 4.0.0 PyPI | Changelog | Homepage | Bugtracker
pyasn1-modules 0.1.1 » 0.1.4 PyPI | Changelog | Repo
pyasn1 0.3.3 » 0.3.6 PyPI | Changelog | Repo
pyopenssl 17.2.0 » 17.3.0 PyPI | Changelog | Homepage | Docs
six 1.10.0 » 1.11.0 PyPI | Changelog | Homepage | Docs
twisted[conch,tls] 17.5.0 » 17.9.0 PyPI | Changelog | Homepage | Bugtracker
zope.interface 4.4.2 » 4.4.3 PyPI | Changelog | Repo

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

cffi 1.10.0 -> 1.11.0

1.11

=====

  • Support the modern standard types char16_t and char32_t.
    These work like wchar_t: they represent one unicode character, or
    when used as charN_t * or charN_t[] they represent a unicode
    string. The difference with wchar_t is that they have a known,
    fixed size. They should work at all places that used to work with
    wchar_t (please report an issue if I missed something). Note
    that with set_source(), you need to make sure that these types are
    actually defined by the C source you provide (if used in cdef()).
  • Support the C99 types float _Complex and double _Complex.
    Note that libffi doesn't support them, which means that in the ABI
    mode you still cannot call C functions that take complex numbers
    directly as arguments or return type.
  • Fixed a rare race condition when creating multiple FFI instances
    from multiple threads. (Note that you aren't meant to create many
    FFI instances: in inline mode, you should write ffi = cffi.FFI() at module level just after import cffi; and in
    out-of-line mode you don't instantiate FFI explicitly at all.)
  • Windows: using callbacks can be messy because the CFFI internal error
    messages show up to stderr---but stderr goes nowhere in many
    applications. This makes it particularly hard to get started with the
    embedding mode. (Once you get started, you can at least use
    ffi.def_extern(onerror=...) and send the error logs where it
    makes sense for your application, or record them in log files, and so
    on.) So what is new in CFFI is that now, on Windows CFFI will try to
    open a non-modal MessageBox (in addition to sending raw messages to
    stderr). The MessageBox is only visible if the process stays alive:
    typically, console applications that crash close immediately, but that
    is also the situation where stderr should be visible anyway.
  • Progress on support for callbacks in NetBSD__.
  • Functions returning booleans would in some case still return 0 or 1
    instead of False or True. Fixed.
  • ffi.gc()__ now takes an optional third parameter, which gives an
    estimate of the size (in bytes) of the object. So far, this is only
    used by PyPy, to make the next GC occur more quickly (issue 320).
    In the future, this might have an effect on CPython too (provided
    the CPython issue 31105
    is addressed).
  • Add a note to the documentation: the ABI mode gives function objects
    that are slower to call than the API mode does. For some reason it
    is often thought to be faster. It is not!

.. __: https://bitbucket.org/cffi/cffi/issues/321/cffi-191-segmentation-fault-during-self
.. __: ref.htmlffi-gc
.. __: https://bitbucket.org/cffi/cffi/issues/320/improve-memory_pressure-management
.. __: http://bugs.python.org/issue31105

1.10.1

=======

lxml 3.8.0 -> 4.0.0

4.0.0

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

Features added

  • The ElementPath implementation is now compiled using Cython,
    which speeds up the .find*() methods quite significantly.
  • The modules lxml.builder, lxml.html.diff and lxml.html.clean
    are also compiled using Cython in order to speed them up.
  • xmlfile() supports async coroutines using async with and await.
  • iterwalk() has a new method skip_subtree() that prevents walking into
    the descendants of the current element.
  • RelaxNG.from_rnc_string() accepts a base_url argument to
    allow relative resource lookups.
  • The XSLT result object has a new method .write_output(file) that serialises
    output data into a file according to the <xsl:output> configuration.

Bugs fixed

  • GH251: HTML comments were handled incorrectly by the soupparser.
    Patch by mozbugbox.
  • LP1654544: The html5parser no longer passes the useChardet option
    if the input is a Unicode string, unless explicitly requested. When parsing
    files, the default is to enable it when a URL or file path is passed (because
    the file is then opened in binary mode), and to disable it when reading from
    a file(-like) object.

Note: This is a backwards incompatible change of the default configuration.
If your code parses byte strings/streams and depends on character detection,
please pass the option guess_charset=True explicitly, which already worked
in older lxml versions.

  • LP1703810: etree.fromstring() failed to parse UTF-32 data with BOM.
  • LP1526522: Some RelaxNG errors were not reported in the error log.
  • LP1567526: Empty and plain text input raised a TypeError in soupparser.
  • LP1710429: Uninitialised variable usage in HTML diff.
  • LP1415643: The closing tags context manager in xmlfile() could continue
    to output end tags even after writing failed with an exception.
  • LP1465357: xmlfile.write() now accepts and ignores None as input argument.
  • Compilation under Py3.7-pre failed due to a modified function signature.

Other changes

  • The main module source files were renamed from lxml.*.pyx to plain
    *.pyx (e.g. etree.pyx) to simplify their handling in the build
    process. Care was taken to keep the old header files as fallbacks for
    code that compiles against the public C-API of lxml, but it might still
    be worth validating that third-party code does not notice this change.

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! 🤖


This change is Reviewable

@mithrandi
Copy link
Member

bors r+

@codecov
Copy link

codecov bot commented Oct 2, 2017

Codecov Report

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

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #155   +/-   ##
=======================================
  Coverage   93.84%   93.84%           
=======================================
  Files          14       14           
  Lines        1072     1072           
  Branches       65       65           
=======================================
  Hits         1006     1006           
  Misses         53       53           
  Partials       13       13

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6a89bbb...560a0cd. Read the comment docs.

bors-fusion bot added a commit that referenced this pull request Oct 2, 2017
155: 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">&raquo;</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>cffi</b></td>
<td align="center">1.10.0</td>
<td align="center">&raquo;</td>
<td align="center">1.11.0</td>
<td>
     <a href="https://pypi.python.org/pypi/cffi">PyPI</a> | <a href="https://pyup.io/changelogs/cffi/">Changelog</a> | <a href="http://cffi.readthedocs.org">Docs</a> 

</td>

<tr>
<td><b>lxml</b></td>
<td align="center">3.8.0</td>
<td align="center">&raquo;</td>
<td align="center">4.0.0</td>
<td>
     <a href="https://pypi.python.org/pypi/lxml">PyPI</a> | <a href="https://pyup.io/changelogs/lxml/">Changelog</a> | <a href="http://lxml.de/">Homepage</a> | <a href="https://bugs.launchpad.net/lxml">Bugtracker</a> 

</td>

<tr>
<td><b>pyasn1-modules</b></td>
<td align="center">0.1.1</td>
<td align="center">&raquo;</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">&raquo;</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">&raquo;</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">&raquo;</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[conch,tls]</b></td>
<td align="center">17.5.0</td>
<td align="center">&raquo;</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">&raquo;</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







### cffi 1.10.0 -> 1.11.0

>### 1.11

>=====

>* Support the modern standard types ``char16_t`` and ``char32_t``.
>  These work like ``wchar_t``: they represent one unicode character, or
>  when used as ``charN_t *`` or ``charN_t[]`` they represent a unicode
>  string.  The difference with ``wchar_t`` is that they have a known,
>  fixed size.  They should work at all places that used to work with
>  ``wchar_t`` (please report an issue if I missed something).  Note
>  that with ``set_source()``, you need to make sure that these types are
>  actually defined by the C source you provide (if used in ``cdef()``).

>* Support the C99 types ``float _Complex`` and ``double _Complex``.
>  Note that libffi doesn&#39;t support them, which means that in the ABI
>  mode you still cannot call C functions that take complex numbers
>  directly as arguments or return type.

>* Fixed a rare race condition when creating multiple ``FFI`` instances
>  from multiple threads.  (Note that you aren&#39;t meant to create many
>  ``FFI`` instances: in inline mode, you should write ``ffi =
>  cffi.FFI()`` at module level just after ``import cffi``; and in
>  out-of-line mode you don&#39;t instantiate ``FFI`` explicitly at all.)

>* Windows: using callbacks can be messy because the CFFI internal error
>  messages show up to stderr---but stderr goes nowhere in many
>  applications.  This makes it particularly hard to get started with the
>  embedding mode.  (Once you get started, you can at least use
>  ``ffi.def_extern(onerror=...)`` and send the error logs where it
>  makes sense for your application, or record them in log files, and so
>  on.)  So what is new in CFFI is that now, on Windows CFFI will try to
>  open a non-modal MessageBox (in addition to sending raw messages to
>  stderr).  The MessageBox is only visible if the process stays alive:
>  typically, console applications that crash close immediately, but that
>  is also the situation where stderr should be visible anyway.

>* Progress on support for `callbacks in NetBSD`__.

>* Functions returning booleans would in some case still return 0 or 1
>  instead of False or True.  Fixed.

>* `ffi.gc()`__ now takes an optional third parameter, which gives an
>  estimate of the size (in bytes) of the object.  So far, this is only
>  used by PyPy, to make the next GC occur more quickly (`issue 320`__).
>  In the future, this might have an effect on CPython too (provided
>  the CPython `issue 31105`__ is addressed).

>* Add a note to the documentation: the ABI mode gives function objects
>  that are *slower* to call than the API mode does.  For some reason it
>  is often thought to be faster.  It is not!

>.. __: https://bitbucket.org/cffi/cffi/issues/321/cffi-191-segmentation-fault-during-self
>.. __: ref.htmlffi-gc
>.. __: https://bitbucket.org/cffi/cffi/issues/320/improve-memory_pressure-management
>.. __: http://bugs.python.org/issue31105




>### 1.10.1

>=======







### lxml 3.8.0 -> 4.0.0

>### 4.0.0

>==================

>Features added
>--------------

>* The ElementPath implementation is now compiled using Cython,
>  which speeds up the ``.find*()`` methods quite significantly.

>* The modules ``lxml.builder``, ``lxml.html.diff`` and ``lxml.html.clean``
>  are also compiled using Cython in order to speed them up.

>* ``xmlfile()`` supports async coroutines using ``async with`` and ``await``.

>* ``iterwalk()`` has a new method ``skip_subtree()`` that prevents walking into
>  the descendants of the current element.

>* ``RelaxNG.from_rnc_string()`` accepts a ``base_url`` argument to
>  allow relative resource lookups.

>* The XSLT result object has a new method ``.write_output(file)`` that serialises
>  output data into a file according to the ``&lt;xsl:output&gt;`` configuration.

>Bugs fixed
>----------

>* GH251: HTML comments were handled incorrectly by the soupparser.
>  Patch by mozbugbox.

>* LP1654544: The html5parser no longer passes the ``useChardet`` option
>  if the input is a Unicode string, unless explicitly requested.  When parsing
>  files, the default is to enable it when a URL or file path is passed (because
>  the file is then opened in binary mode), and to disable it when reading from
>  a file(-like) object.

>  Note: This is a backwards incompatible change of the default configuration.
>  If your code parses byte strings/streams and depends on character detection,
>  please pass the option ``guess_charset=True`` explicitly, which already worked
>  in older lxml versions.

>* LP1703810: ``etree.fromstring()`` failed to parse UTF-32 data with BOM.

>* LP1526522: Some RelaxNG errors were not reported in the error log.

>* LP1567526: Empty and plain text input raised a TypeError in soupparser.

>* LP1710429: Uninitialised variable usage in HTML diff.

>* LP1415643: The closing tags context manager in ``xmlfile()`` could continue
>  to output end tags even after writing failed with an exception.

>* LP1465357: ``xmlfile.write()`` now accepts and ignores None as input argument.

>* Compilation under Py3.7-pre failed due to a modified function signature.

>Other changes
>-------------

>* The main module source files were renamed from ``lxml.*.pyx`` to plain
>  ``*.pyx`` (e.g. ``etree.pyx``) to simplify their handling in the build
>  process.  Care was taken to keep the old header files as fallbacks for
>  code that compiles against the public C-API of lxml, but it might still
>  be worth validating that third-party code does not notice this change.








### pyopenssl 17.2.0 -> 17.3.0

>### 17.3.0

>-------------------


>Backward-incompatible changes:
>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

>- Dropped support for Python 3.3.
>  `677 &lt;https://github.com/pyca/pyopenssl/pull/677&gt;`_
>- 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 &lt;https://github.com/pyca/pyopenssl/pull/675&gt;`_


>Deprecations:
>^^^^^^^^^^^^^

>- Deprecated ``OpenSSL.tsafe``.
>  `673 &lt;https://github.com/pyca/pyopenssl/pull/673&gt;`_

>Changes:
>^^^^^^^^

>- Fixed a memory leak in ``OpenSSL.crypto.CRL``.
>  `690 &lt;https://github.com/pyca/pyopenssl/pull/690&gt;`_
>- Fixed a memory leak when verifying certificates with ``OpenSSL.crypto.X509StoreContext``.
>  `691 &lt;https://github.com/pyca/pyopenssl/pull/691&gt;`_


>----








### 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
>  &lt;https://github.com/zopefoundation/zope.interface/issues/98&gt;`_.
>- Fix the possibility of a rare crash in the C extension when
>  deallocating items. See `issue 100
>  &lt;https://github.com/zopefoundation/zope.interface/issues/100&gt;`_.











That's it for now!

Happy merging! 🤖
@bors-fusion
Copy link
Contributor

bors-fusion bot commented Oct 2, 2017

Build succeeded

@bors-fusion bors-fusion bot merged commit 560a0cd into master Oct 2, 2017
@bors-fusion bors-fusion bot deleted the pyup-scheduled-update-10-02-2017 branch October 2, 2017 16:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants