Re: [Savannah-hackers] submission of XIE - savannah.nongnu.org

[Sylvain Beucler]

xml.parsers.expat actually is pyexpat. However, the license notice
from the PyXML project refers to outdated license back from the time
of "BeOpen", which mislead me. So pyexpat is now under the latest
Python license, which is compatible with the GNU GPL.

-- 
Sylvain

On Tue, Nov 16, 2004 at 09:05:58AM -0500, Alex Turner wrote:
> Fair enough - I am comitted to using Free Software for this project. 
> The current release of python includes the package xml.parsers.expat. 
> Is this the same thing as PyExpat, or because it's part of the core
> package, is it covered under the python license which is GPL
> compatible?
> 
> Thanks for your time and insight,
> 
> Alex
> 
> 
> On Mon, 15 Nov 2004 21:21:18 +0100, Sylvain Beucler <address@hidden> wrote:
> > Hi,
> > 
> > Note that PyXML is a suite a XML tools, some of them under acceptable
> > licenses. For example, xmlproc, "a validating XML parser", is released
> > under a free software license; same for 4DOM, qp_xml, and some other
> > tools cited in their "LICENCE" file.
> > 
> > Xerces is released under the Apache License, version 2, which is
> > unfortunately also incompatible with the GNU GPL.
> > http://www.gnu.org/licenses/license-list.html
> > 
> > I know that Expat is a non-validating parser released under a GNU
> > GPL-compatible license (do not confuse it with PyExpat, which is one
> > of the problematic tools in pyxml).
> > 
> > An option you may consider is contacting the author(s) of the software
> > you want to use and ask him/them to release it under a license
> > compatible with the GNU GPL.
> > 
> > --
> > Sylvain
> > 
> > 
> > 
> > On Mon, Nov 15, 2004 at 10:05:30AM -0500, Alex Turner wrote:
> > > I did a little bit of digging, and I couldn't find an alternative XML
> > > parser for python.  Do you know of one?
> > >
> > > I am also writting a C++ version that uses Xerces - do you know if
> > > xerces is GPL compatible?  If that were the case then I could just
> > > abandon the python version as I'm having serious performance issues
> > > anyhow.
> > >
> > > Thanks,
> > >
> > > Alex
> > >
> > >
> > > On Thu, 11 Nov 2004 21:15:59 +0100, Sylvain Beucler <address@hidden> 
> > > wrote:
> > > > Hi,
> > > >
> > > > I'm evaluating the project you submitted for approval in Savannah.
> > > >
> > > > > plexq <address@hidden> described the package as follows:
> > > > > License: gpl
> > > > > Other License:
> > > > > Package: XIE
> > > > > System name: xie
> > > > > Type: non-GNU
> > > > >
> > > > > Description:
> > > > > XIE is the XML Internet Engine.  It is designed to be used either as
> > > > > an apache module or a stand-alone system to generate content.  It
> > > > > bares a passing resemblance to Cold Fusion in syntax.  The system is
> > > > > currently written in Python, and support embeded python in xie
> > > > > scripts.
> > > > >
> > > > > Other Software Required:
> > > > > python-2.2 or greater
> > > > > pyxml
> > > > > pygres
> > > > > mod_python
> > > >
> > > > Regarding pyxml, there is an issue: parts of the code are released
> > > > under different licenses, one governed by the laws of the "State of
> > > > Virginia" (parts under CNRI OSLA), and the other by the laws of the
> > > > "State of California" (PyExpat), and the GPL does not permit this, so
> > > > pyxml is incompatible with the GNU GPL. The part under the ZPL v1 are
> > > > also GPL-incompatible (though if they eventually upgrade to ZPL v2,
> > > > this will not be the case anymore). We recommand that you remove this
> > > > dependency. Feel free to ask us any question regarding this issue.
> > > >
> > > > Also, please reply and include a (perhaps temporary) URL pointing to
> > > > the source code.  The description you gave when registering will not
> > > > be read by the general public.  If you are still concerned with
> > > > privacy, however, you can forward the code to me by email
> > > > (address@hidden).
> > > >
> > > > We wish to review your source code, even if it is not functional, to
> > > > catch potential legal issues early.
> > > >
> > > > For example, to release your program properly under the GPL you must
> > > > include a copyright notice and permission-to-copy statements at the
> > > > beginning of every file of source code.  This is explained in
> > > > http://www.gnu.org/licenses/gpl-howto.html.  Our review would help
> > > > catch potential omissions such as these.