Martin v. Löwis [EMAIL PROTECTED] added the comment:
This is now fixed in r66460 and r66462; the text that gets included is
in Tools/msi/crtlicense.txt.
--
keywords: -easy
resolution: - fixed
status: open - closed
___
Python tracker [EMAIL
Martin v. Löwis [EMAIL PROTECTED] added the comment:
Van, your recommendation is much appreciated. I'll add your text to the
LICENSE file of the next release candidates.
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3617
Neil Hodgson [EMAIL PROTECTED] added the comment:
The recommended addition includes the 'excluded license' section which
appears unnecessary as Python does not distribute any source code
redistributables, only the .DLL file which is a binary executable.
Including this is likely to confuse
Van Lindberg [EMAIL PROTECTED] added the comment:
Neil, you are right. I was thinking about linking to the binary dll
(which some people think might impose licensing restrictions under some
circumstances), but the text does refer to the source code.
As Python does not distribute any source code
Changes by Barry A. Warsaw [EMAIL PROTECTED]:
--
priority: normal - release blocker
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3617
___
___
Van Lindberg [EMAIL PROTECTED] added the comment:
Sorry for the long comment. There are two parts to this comment. First,
my recommendation, and second, the somewhat tedious analysis of the
Microsoft EULAs. The second part is the verbiage to justify the first.
Recommendation
==
To
Marc-Andre Lemburg [EMAIL PROTECTED] added the comment:
Thank you, Van, for this comprehensive analysis.
By including your text we'll also bypass the issues with finding the
EULA file in the Visual Studio installation.
The text should be easy to add as extra file and we can then reference
this
Van Lindberg [EMAIL PROTECTED] added the comment:
The important part is that we point out the Microsoft redistributables
are subject to Microsoft's restrictions; we don't need to point to a
specific EULA URL. People installing Python will agree to the license
terms as they apply to the different
Changes by Travis N. Vaught [EMAIL PROTECTED]:
--
nosy: +tvaught
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3617
___
___
Python-bugs-list mailing
Changes by Barry A. Warsaw [EMAIL PROTECTED]:
--
priority: deferred blocker - release blocker
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3617
___
Martin v. Löwis [EMAIL PROTECTED] added the comment:
I don't think this needs to be resolved before 2.6, not without a
pronouncement from a lawyer advising the PSF. Layman's analyses of legal
issues are void.
Thus lowering the priority.
--
nosy: +loewis
priority: release blocker -
Marc-Andre Lemburg [EMAIL PROTECTED] added the comment:
On 2008-09-09 17:54, Martin v. Löwis wrote:
Martin v. Löwis [EMAIL PROTECTED] added the comment:
I don't think this needs to be resolved before 2.6, not without a
pronouncement from a lawyer advising the PSF. Layman's analyses of legal
Martin v. Löwis [EMAIL PROTECTED] added the comment:
Rather than arguing about the necessity of including the license
of a 3rd party file that we intend to include in a wide-spread
software release, wouldn't it be easier to just add the file
and be done with it, like I suggested at the very
Marc-Andre Lemburg [EMAIL PROTECTED] added the comment:
On 2008-09-09 23:09, Martin v. Löwis wrote:
Martin v. Löwis [EMAIL PROTECTED] added the comment:
Rather than arguing about the necessity of including the license
of a 3rd party file that we intend to include in a wide-spread
software
Martin v. Löwis [EMAIL PROTECTED] added the comment:
We've had the same issue with the OpenSSL license and the other
3rd party packages which come with the Python Windows installer.
No, the issue was completely different. Those licenses literally
say include a copy of the license text (e.g.
Marc-Andre Lemburg [EMAIL PROTECTED] added the comment:
Here's a patch that adds the MS EULA to the MSI installer.
I couldn't test this, since I don't have a Python build environment on
Windows, but it should be more or less working.
--
keywords: +patch
Added file:
Marc-Andre Lemburg [EMAIL PROTECTED] added the comment:
On 2008-09-10 00:15, Martin v. Löwis wrote:
Martin v. Löwis [EMAIL PROTECTED] added the comment:
We've had the same issue with the OpenSSL license and the other
3rd party packages which come with the Python Windows installer.
No,
Marc-Andre Lemburg [EMAIL PROTECTED] added the comment:
Raising priority since this needs to be resolved prior to the final
release of Python 2.6/3.0.
Regarding finding the eula.txt in the VS2008 installation, there doesn't
appear to be a generic way. The eula.txt is stored in a folder named
Marc-Andre Lemburg [EMAIL PROTECTED] added the comment:
Mark Hammond wrote:
Mark Hammond [EMAIL PROTECTED] added the comment:
Obviously IANAL, but my reading of eula.txt included with VS9 seems less
restrictive than the 2003 one. It has 2 clauses that seem relevant:
* [you must] require
Mark Hammond [EMAIL PROTECTED] added the comment:
MAL:
This was already discussed on the PSF members mailing list.
Yeah, but not specifically about VS2008 which this bug seemed to be
specifically targetting. FWIW, this appears like *less* of a problem
for 2.6 than for 2.4 and 2.5 as it
Marc-Andre Lemburg [EMAIL PROTECTED] added the comment:
Attaching the VS7.1 EULA. This is only relevant for Python 2.5... should
we do another patch level release.
--
versions: +Python 2.5
Added file: http://bugs.python.org/file11188/eula.txt
___
Marc-Andre Lemburg [EMAIL PROTECTED] added the comment:
Mark Hammond wrote:
MAL:
Note that I'm not suggesting to dive into all this. We
should simply put the EULA into the installer package
and be done with it :-)
I can't argue with that - including the relevant EULA certainly would be
Marc-Andre Lemburg [EMAIL PROTECTED] added the comment:
Adding the EULA should be easy... the MSI installer code already adds
the other licenses for OpenSSL, etc. to the license text in
Tools/msi/msi.py (took me a while to find that file, since I would have
expected this to live under PCbuild/).
New submission from Marc-Andre Lemburg [EMAIL PROTECTED]:
Since we are shipping the msvcr90.dll (+ assemblies) together with the
Python installer for Windows, we need to include the MS EULA for VS2008
in the third-party licenses section as this is the license that covers
the VS DLLs.
--
Marc-Andre Lemburg [EMAIL PROTECTED] added the comment:
Note that there are a few gotchas in the MS EULA, such as disallowing to
ship the DLLs with GPLed Python products or requiring that the PSF
prevents further redistribution of the DLLs unless used in conjunction
with Python.
--
Changes by Thomas Heller [EMAIL PROTECTED]:
--
nosy: +theller
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3617
___
___
Python-bugs-list mailing list
Mark Hammond [EMAIL PROTECTED] added the comment:
Obviously IANAL, but my reading of eula.txt included with VS9 seems less
restrictive than the 2003 one. It has 2 clauses that seem relevant:
* [you must] require distributors and external end users to agree to
terms that protect it at least as
27 matches
Mail list logo
