M
Markus Schaber
Hi,
First, sorry for sending an HTML message to the list, this was not
intended.
I now found out that http://docs.python.org/release/2.6.6/license.html
does actually explain which part of the software is covered by which
part of the license, but contains a different subset of licenses than
the LICENSE.txt - two of the differences are the Berkeley part, and the
windows binary build part.
This is just adding somewhat more confusion...
Thanks,
Markus
Original Message:
Betreff: Pure python standard library and License
Hi,
We want to include IronPython in one of our products, including the pure
Python part of the python standard library. It seems that the IronPython
installer packagers simply copied the pure python part of the standard
library (the directory tree of .py files which is installed by cPython
and IronPython installers in the lib/ subdirectory) from cPython.
Now, this directory comes with a LICENSE.txt which contains a
conglomerate of several licenses, and for us (and our Lawyers), it is
not entirely clear which part of the license applies to the pure Python
part of the standard library, and which applies to other files (like the
Berkeley Database license).
Our current understanding is that all the .py files which do not contain
any explicit mentioning of a license are covered by the Python licenses
(the first three licenses of the LICENSE.txt), and that e. G. the
Berkeley Database License only applies to the bsddb module which is
implemented in C, and thus is currently neither included with nor usable
from IronPython.
Is there anyone who can confirm this interpretation?
Maybe the LICENSE.txt should clarify somehow which of the licenses
applies to which part of the software.
Best regards
Markus Schaber
___________________________
We software Automation.
3S-Smart Software Solutions GmbH
Markus Schaber | Developer
Memminger Str. 151 | 87439 Kempten | Germany | Tel. +49-831-54031-0 |
Fax +49-831-54031-50
Email: (e-mail address removed) | Web: http://www.3s-software.com
CoDeSys internet forum: http://forum.3s-software.com
Download CoDeSys sample projects:
http://www.3s-software.com/index.shtml?sample_projects
Managing Directors: Dipl.Inf. Dieter Hess, Dipl.Inf. Manfred Werner |
Trade register: Kempten HRB 6186 | Tax ID No.: DE 167014915
First, sorry for sending an HTML message to the list, this was not
intended.
I now found out that http://docs.python.org/release/2.6.6/license.html
does actually explain which part of the software is covered by which
part of the license, but contains a different subset of licenses than
the LICENSE.txt - two of the differences are the Berkeley part, and the
windows binary build part.
This is just adding somewhat more confusion...
Thanks,
Markus
Original Message:
Betreff: Pure python standard library and License
Hi,
We want to include IronPython in one of our products, including the pure
Python part of the python standard library. It seems that the IronPython
installer packagers simply copied the pure python part of the standard
library (the directory tree of .py files which is installed by cPython
and IronPython installers in the lib/ subdirectory) from cPython.
Now, this directory comes with a LICENSE.txt which contains a
conglomerate of several licenses, and for us (and our Lawyers), it is
not entirely clear which part of the license applies to the pure Python
part of the standard library, and which applies to other files (like the
Berkeley Database license).
Our current understanding is that all the .py files which do not contain
any explicit mentioning of a license are covered by the Python licenses
(the first three licenses of the LICENSE.txt), and that e. G. the
Berkeley Database License only applies to the bsddb module which is
implemented in C, and thus is currently neither included with nor usable
from IronPython.
Is there anyone who can confirm this interpretation?
Maybe the LICENSE.txt should clarify somehow which of the licenses
applies to which part of the software.
Best regards
Markus Schaber
___________________________
We software Automation.
3S-Smart Software Solutions GmbH
Markus Schaber | Developer
Memminger Str. 151 | 87439 Kempten | Germany | Tel. +49-831-54031-0 |
Fax +49-831-54031-50
Email: (e-mail address removed) | Web: http://www.3s-software.com
CoDeSys internet forum: http://forum.3s-software.com
Download CoDeSys sample projects:
http://www.3s-software.com/index.shtml?sample_projects
Managing Directors: Dipl.Inf. Dieter Hess, Dipl.Inf. Manfred Werner |
Trade register: Kempten HRB 6186 | Tax ID No.: DE 167014915