This repository was archived by the owner on Aug 4, 2018. It is now read-only.
Merged
Conversation
Closed
Member
|
bors r+ |
1 similar comment
Member
|
bors r+ |
Contributor
Merge conflict (retrying...) |
1 similar comment
Contributor
Merge conflict (retrying...) |
bors-fusion bot
added a commit
that referenced
this pull request
Nov 17, 2017
117: Update lxml to 4.1.1 r=mithrandi a=pyup-bot There's a new version of [lxml](https://pypi.python.org/pypi/lxml) available. You are currently using **3.8.0**. I have updated it to **4.1.1** These links might come in handy: <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> ### Changelog > >### 4.1.1 >================== >* Rebuild with Cython 0.27.3 to improve support for Py3.7. >### 4.1.0 >================== >Features added >-------------- >* ElementPath supports text predicates for current node, like "[.='text']". >* ElementPath allows spaces in predicates. >* Custom Element classes and XPath functions can now be registered with a > decorator rather than explicit dict assignments. >* Static Linux wheels are now built with link time optimisation (LTO) enabled. > This should have a beneficial impact on the overall performance by providing > a tighter compiler integration between lxml and libxml2/libxslt. >Bugs fixed >---------- >* LP1722776: Requesting non-Element objects like comments from a document with > ``PythonElementClassLookup`` could fail with a TypeError. >### 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. *Got merge conflicts? Close this PR and delete the branch. I'll create a new PR for you.* Happy merging! 🤖
Contributor
Build succeeded |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
There's a new version of lxml available.
You are currently using 3.8.0. I have updated it to 4.1.1
These links might come in handy: PyPI | Changelog | Homepage | Bugtracker
Changelog
Got merge conflicts? Close this PR and delete the branch. I'll create a new PR for you.
Happy merging! 🤖
This change is