[lxml-dev] setup.py and buildout

[Martijn Faassen]

Ian Bicking wrote:
> Luke Tucker wrote:
>> I wound up pushing parts/libxslt/bin onto the front of PATH with a
>> recipe before calling lxmls setup, but there may be cleaner ways. 
>> There is a separate issue I mentioned in "lxml setup.py exslt link flag"
>> related to doing this but I haven't gotten back to this yet to write a
>> patch. 
> 
> Why doesn't xml-config go in the top-level bin/ directory?  It seems 
> like that path should also be on the front of PATH in general when 
> building a buildout.  (Though I don't know if buildout does that currently.)

Hm, currently the 'bin' is only for scripts that are the *result* (and 
goal) of the buildout. The goal of the buildout is not to install the 
libxml2 tools, but it's to install lxml. libxml2 is only a step along 
the way for this. I also don't believe buildout does anything to PATH 
whatsoever (or that it by itself should - it goes out of its way to be 
very explicit about paths everywhere after all).

I think it would help us a lot if lxml's setup.py simply accepted an 
option that identifies which xslt-config to use. This could be easily be 
configured from the buildout.

Note that lxml's setup does something (what I don't know) when it's 
called with --rpath, another thing that buildout calls. Does it do the 
right thing?

Regards,

Martijn