Streaming XML-RPC?

[Jim Dennis]

In article <slrnaaf8bk.ok0.mlh at vier.idi.ntnu.no>, Magnus Lie Hetland wrote:
>In article <a81584$2gr2$1 at news.idiom.com>, Jim Dennis wrote:
>>In article <slrnaa1gb9.87e.mlh at vier.idi.ntnu.no>, Magnus Lie Hetland wrote:
>>>In article <mailman.1017105342.20070.python-list at python.org>, Skip

>>>Montanaro wrote:
>>>> Don>   Are there any decent (finished/tested) Jabber libraries for Python?

>>>>Don't know what its status is, but there is jabberpy:
>>>> http://jabberpy.sourceforge.net/
>>> It's LGPL, which may make it unsuitable for some projects (like the
>>> standard Python library). But it seems to support the basic protocol.
>> Why would LGPL be allergic to the Python License?
> I don't think it is, but AFAIK you couldn't include GPL or LGPL
> software in the Python standard library, for instance. (But then
> again, if that were an issue, the authors would probably donate the
> code to the PSF anyway...)

 IANAL, but:

 I thought that PSF and Guido came up with a GPL compatible license.
 Since I'm not releasing any code that mixes GPL and Python code
 I haven't scrutinized the licenses in detail.  So I don't know which
 versions of Python are covered by GPL compatible licenses, nor am I
 sure that the two licenses *are* actually compatible.

 However, it seems that the LGPL should be freely linkable even to 
 proprietary or other non-GPL code.  I was under the impression that
 this was the whole point of the *L*GPL.