[lxml-dev] lhtml

[Ian Bicking]

Martijn Faassen wrote:
> Ian Bicking wrote:
>> Stefan Behnel wrote:
> [snip]
>>> Note that lxml already has quite a number of modules like lxml.sax and
>>> lxml.objectify, so lxml.html would nicely fit in here.
>> I had thought about that, but I don't know if it should have the same 
>> release schedule...?  It's a somewhat random collection of functions 
>> that we've written here and there in other modules.  I can clean them 
>> up, of course, but exactly what functionality is in there has been an 
>> on-demand sort of thing.  Which is to say, it's young.
> 
> If you're willing to help getting releases out of the door, I could 
> imagine we let the html functionality drive the release schedule for a 
> while. It is not like we have a lot of other features lined up right 
> now, so this would be a good way to actually drive a few new releases. 
> What do you think, Stefan?

Well, maybe I'm thinking of more common releases, but maybe also less 
common releases.  In that, I don't know exactly what all should be in 
the module to start with, and what kind of design review should go into 
those modules.

>> OTOH, we could distribute it as a namespace package with its own release 
>> cycle but still in lxml.html.
> 
> I think this is possible as 'lxml' itself is currently an empty 
> namespace package (empty __init__.py). It does contain a lot of modules 
> though. Does the whole namespace package installation machinery in 
> setuptools still work in this case?

Yes.  I don't quite understand the details, but I think lxml.__path__ 
points to the directories for both packages, and it searches both in 
turn.  So both can have an arbitrary number of modules under lxml and in 
each distribution.


-- 
Ian Bicking | ianb at colorstudy.com | http://blog.ianbicking.org
             | Write code, do good | http://topp.openplans.org/careers