I'm in favor of 2.1 (pending any work Tomaz brought up for lxml). On Tue, Jun 27, 2017 at 6:32 AM, Tomaz Muraus <to...@apache.org> wrote:
> Sorry for a late response. > > I would be curious to know a bit more about the lxml issue (sorry if I > missed a Github issue or similar, feel free to point me to it). > > I definitely used lxml in the past with some drivers, notably AWS because > it offered quite substantial performance and memory usage improvements when > working with large xml responses so I'm curious to know what / where is not > working. > > I know there were some lxml test case failures in the past, but at some > point all of those were resolved and passing. > > Besides that, I'm all for v.2.10 once we resolve the lxml issue. > > On Sat, Jun 24, 2017 at 12:00 PM, anthony shaw <anthonys...@apache.org> > wrote: > > > It's been 2 months since the last release, we've had tons of PR's, lots > of > > bug fixes and also a new driver for Google Container Engine (exciting!) > > > > We're slowly getting packages for RedHat, Centos, Fedora (rpm based) > > updated to 2.0, some were as old as 0.20.0 > > https://bodhi.fedoraproject.org/updates/FEDORA-2017-6d6c5cd543 > > > > Also, the Debian package management team have given me some feedback to > > help get the 2.0 packages into debian and ubuntu. > > > > So, it's time we released 2.1, there would be 1 big change, to disable > LXML > > by default. Although, from testing that I've done- it doesn't work > properly > > anyway- so we're just preventing it from crashing when used in a > virtualenv > > where lxml exists. > > > > https://github.com/apache/libcloud/blob/trunk/CHANGES. > > rst#changes-in-current-version-of-apache-libcloud > > >
