[lxml-dev] specifying lxml as a dependency?

[Chris Withers]

Ian Bicking wrote:
> Chris Withers wrote:
>> Hi All,
>>
>> I'm just about to start moving Twiddler from ElementTree to lxml and 
>> I'm wondering how to specify lxml as a requirement in Twiddler's 
>> setup.py?
>>
>> Do I just do the normal setuptools dance or is there more to it than 
>> that?
>>
>> If I specify lxml as a requirement, how do lxml's requirements for 
>> libxml2 and libxlst get satisfied?
> 
> Just as 'lxml'.  On Windows it'll pull the binary egg.  

...and that binary egg includes libxml2 and libxlst?

> Maybe a Mac egg 
> is doable now?  I think there are still some difficulties to moving 
> libraries around. 

I haven't followed the lxml Mac story at all, so this is all a little 
lost on me...

> Linux binary eggs are too problematic to be worth 
> trying.  The system will have to have libxml2/libxslt and the -dev 
> packages (on Linux), 

Okay, so the user will have to get libxml2 and libxslt on the system 
"somehow" (ie: os package manager, source install, etc) *before* 
easy_install'ing lxml?
What happens if they forget and easy_install lxml without libxml2 or 
libxslt?

> and they could do "STATIC_DEPS=true easy_install 
> Twiddler" to build a static lxml on Macs 

Where would "STATIC_DEPS=true easy_install Twiddler" go?

> (with the trunk, which itself 
> is a little harder to build, but hopefully there will be an easier 
> release before too long).

Not sure what this means. What's the difference between the trunk and 
the last release on PyPI?

cheers,

Chris

-- 
Simplistix - Content Management, Zope & Python Consulting
            - http://www.simplistix.co.uk