Python's CRT licensing on Windows <-- FUD

Fredrik Lundh fredrik at
Wed Oct 25 17:50:57 CEST 2006

sturlamolden wrote:

 > On Windows, the standard Python 2.4 distro is compiled with Microsoft
 > Visual C++ 2003 and is shipped with msvcr71.dll as a part of the binary
 > installer. That is ok, as those who has a license for Microsoft Visual
 > C++ 2003 is allowed to redistribute msvcr71.dll. Without a license for
 > Microsoft Visual C++ 2003 one it not allowed to redistribute this DLL.

that's a myth, based on a flawed reading of the MS license.  to repeat
myself from various other fora:

   "As long as you're using a standard Python build, you don't need to
   buy VC7 to [legally redistribute the C runtime]. The team
   use a properly licensed VC7 to build Python, which turns Python into
   "licensee software" and you into a "distributor" doing "further
   distribution" of Python to end users (with your own stuff added on
   top, of course).  And further distribution is perfectly okay, as long
   as you only ship the MS components together with proper "licensee
   software" (=Python), and that all parties respect the relevant
   portions of the original EULA (this basically means that you cannot
   use tricks to circumvent the MS EULA, e.g. by attempting to relicense
   the MS DLL's under less restrictive licenses or "viral" licenses.  The
   same applies to all other licensed components, of course. You cannot
   relicense the Python core either.)."

   "(If in doubt, consult a real lawyer. If you do, make sure that he/she
   understands the various levels here -- i.e. that "you" in the MS
   EULA applies to the Python developers, not yourself)."


More information about the Python-list mailing list