Did the lxml project indicate they will provide a new release soon that incorporates these fixes?

I tried to build the latest development code from source, but run into many issues (lxml build server down, source package missing the pre-generated C code etc. etc.), and customer company policy wouldn't allow using a development version in production anyway.

The lxml 3.5.0 does not install with pypy-5.0.0 (it used to with pypy-4.0.1, though it was too buggy to be useful), and the lxml-cffi no longer installs.

On 08-03-16 15:26, Armin Rigo wrote:
Hi Matti,

On 8 March 2016 at 15:15, matti picus <matti.pi...@gmail.com> wrote:
We could package it and upload as rc1, but version_info will not have rc1
unless we rerun the builds. Confusing.
  I prefer to apologize if we get it wrong and release a 5.0.1 bugfix
+1.  Go ahead as far as I'm concerned.

About the release notice: "As a result, lxml with its cython compiled
component passes all tests on PyPy" is not clear until the next
official lxml is released.  The current lxml 3.5.0 still contains a
partially buggy workaround that tries to make it work on previous
versions of cpyext.  The trunk version at https://github.com/lxml/lxml
has got this code removed, and that's the version that works.

I'll make the ppc releases once the other releases are out.


A bientôt,

Armin
_______________________________________________
pypy-dev mailing list
pypy-dev@python.org
https://mail.python.org/mailman/listinfo/pypy-dev

_______________________________________________
pypy-dev mailing list
pypy-dev@python.org
https://mail.python.org/mailman/listinfo/pypy-dev

Reply via email to