Stefan Behnel a écrit :
How do we make sure people don't run into this one again? Get a patch accepted by Pyrex?
Like that's ever gonna happen ... :)
Actually we should start releasing with the generated .c code included so people won't need Pyrex anymore. That'll be the best approach for at least people using the release.
etree.c is currently included when you run python setup.py sdist or anything in that line, so it will be in 0.9 and work around all bugs that normal users can encounter from that side. And developers who want to contribute to lxml can well read some documentation first...
You should add the bug fix above to the Pyrex section of installation.html on the web page.
+1 and even host a temporary branch/fork of Pyrex with all the necessary patches included in the lxml repos for the convenience of lxml hackers. Once the patches are included in upstream Pyrex we can get rid of the local branch. -- Olivier