[lxml-dev] 2.0 release plans

Stefan Behnel stefan_ml at behnel.de
Wed Oct 24 11:57:56 CEST 2007


jholg at gmx.de wrote:
> With the high quality I've come to know of lxml I wouldn't be really afraid to base that on a 2.0alpha or beta; however, I'd like to know if major changes are still waiting to happen for 2.0.

Another thing: I've started reworking the slicing code this weekend, but I'm
not sure it'll work out. I'm trying to get rid of the __{get|set|del}slice__()
methods (which will disappear in Py3 anyway), and to enable extended slicing.
I hope it'll meet your quality expectations, "__setitem__(slice)" is a pretty
tough algorithm...

If I can manage to get it running, I'd also try to adapt objectify in that
regard. But that's left to decide.


> To be on the safe side, I could also backport the functionality I need to the 1.3 series (maybe make it publicly available if anyone is interested).

I wouldn't mind that. We could even ship a patch with the next 1.3 release, or
start an intermediate 1.4 series with safe patches that change behaviour. I
hope I get 2.0 out of the door soon enough, though, so that this won't be
necessary.

Stefan


More information about the lxml-dev mailing list