[lxml-dev] Failure with custom resolvers and relative xsl:import

John Lovell jlovell at esd189.org
Tue Aug 19 18:16:32 CEST 2008


I wound up using tlslite the only issue was Windows for which there
wasn't an installer for Python 2.5 and it seemed I needed a version of
DevStudio (that I don't have) to build one.  I tried manually copying
the files and still no joy.  Anyway, back to lxml stuff.

John W. Lovell
Web Applications Engineer
Northwest Educational Service District
1601 R Avenue
Anacortes, WA 98221
(360) 299-4086
jlovell at nwesd.org
 
www.nwesd.org
Together We Can ...


-----Original Message-----
From: Stefan Behnel [mailto:stefan_ml at behnel.de] 
Sent: Tuesday, August 19, 2008 9:02 AM
To: Mike Meyer
Cc: John Lovell; ML-Lxml-dev
Subject: Re: [lxml-dev] Failure with custom resolvers and relative
xsl:import

Mike Meyer wrote:
> If your build includes SSL support, then https is in the standard 
> library. If not, then not.

Ah, sure, that's a portability issue then.


> Unfortunately, the same is *not* true for server side SSL.

... for which there is tlslite, at least I know that one. From a quick
look at their web site, it's supposed to work with httplib also. I never
used it either, but a couple of blog entries seem to be happy with it.

Stefan



More information about the lxml-dev mailing list