Hey Stefan, Stefan Behnel wrote:
Martijn Faassen wrote:
*Does* the setup.py just work on windows? xslt-config must be installed on the path, and things just work then?
There are instructions on how to install those on the libxml2-for-Windows homepage. Remember that you don't normally need to build lxml, so the PATH doesn't matter. lxml is a C-extension, that's not as easy as a Python script. That's why we try to keep users from having to build it themselves. People who want the one-command install should just go with easy_install, which works perfectly on any half-way well-configured system. All that's needed in addition is installing the libxml2/etc. libraries (as their homepage describes).
Right, we should separate the compilation discussion from the installation discussion. If you want to install lxml on Windows, use a compiled version. Let's talk about compilation here. The question remains whether setup.py just works on Windows or whether the people who built the windows versions had to hack it. If the latter, it'd be nice to document these instructions for future reference. If everything does work with the plain setup.py, we should figure out what tripped up David as he apparently needed to hack things.
In addition, these instructions allow you, as far as I understand, to create a *static* version of lxml, including libxml2 and the like.
I really don't mind a static version, despite the ugliness-factor. As I already stated a while ago, Windows heavily lacks any package management. (That's an absolute killer argument against Windows BTW, but, well, it's Windows...)
Compiling a static version is easy, it's just that the way to do is not portable, so we can't put it into setup.py.
Right, so people typically have to hack their setup.py to do so, I guess. We can still document it somewhere.
* what was it that tripped up David?
The main problem seemed to be that he didn't find the binaries - which might have been because of the outdated install docs and because we don't have a Windows egg for 0.9.2 yet. I'm sorry for that.
Perhaps David can provide a windows installer for 0.9.2 that includes the static libraries?
* I'd like to publish the static version of lxml for Windows, as that makes deploying lxml on Windows that much more easy.
Sure, if someone provides a static egg - one more to put on cheeseshop.
Windows installer should be easy. But eggs? Is it possible to have a static egg and a non-static egg both? How would people choose? Should we switch to the static procedure on windows altogether? What do people think? Regards, Martijn