[IronPython] Distributing a commercial application which hosts IronPython 2

[Michael Foord]

Jimmy Schementi wrote:
> Angus,
>
> You can definitely redistribute IronPython assemblies in your 
> application, and that’s the best way to use IronPython on both the 
> desktop and Silverlight. I’d simply have a “IronPython” folder in your 
> app, and in there you put the assemblies and the license.txt, 
> containing the Ms-Pl text. Resolver Systems does this with their 
> products, so maybe Michael Foord can give you some advise.

We pretty much do exactly as Jimmy says.

We have all our app assemblies in one folder (including the IronPython 
ones), and then compiled Python files (actually 'exe's I think) in the 
Python package structure. We then have a licenses folder with all 
relevant licenses and a mention of the IronPython license in our about 
dialog I believe.

Michael Foord

>
> The Ms-Pl license that IronPython uses is “non-infectious” ... as in 
> other code that uses does not need to conform to the same license. 
> Reciprocal licenses, like the Ms-Rl or the GPL, require anything using 
> the code to have the same license.
>
> ~Jimmy
>
> On 6/1/08 6:09 PM, "Angus Gratton" <angus at finalbuilder.com> wrote:
>
>     Hi folks,
>
>     (Sorry if this is an inappropriate place to ask this question. I
>     searched the archives, but prior license discussions all seem to refer
>     to the old license.)
>
>     What is the "best" way to distribute a commercial application which
>     hosts IronPython 2? Is this even possible?
>
>     My original plan was just to require users to install IronPython
>     first,
>     and reference the assemblies from the IronPython installation.
>     However,
>     because IronPython doesn't install anything to the GAC, and because of
>     .NET Framework limitations about loading assemblies from outside the
>     AppDomain's base directory, this is impractical.
>
>     It doesn't seem like Silverlight installs anything to the GAC, either.
>
>     From reading the MS Public License, it looks like it might be possible
>     to distribute the IronPython and DLR assemblies along with our
>     application, explicitly under the MS-PL. While concurrently the
>     commercial/proprietary parts of the application (including our hosting
>     code) are distributed under our closed license. Is that correct? I
>     can't
>     seem to find a clear answer anywhere. Are there any examples of how to
>     correctly structure a license agreement, in this case?
>
>     I would very much like to allow people to use IronPython from our
>     application (I'm very impressed with both the language implementation,
>     the performance, and the hosting API), I'm just unsure how to do it.
>
>     Thanks in advance.
>
>     --
>     Regards,
>
>     Angus Gratton
>     VSoft Technologies
>     http://www.finalbuilder.com/
>     ----------------------------------------
>     Automate your Build Process with FinalBuilder
>
>     _______________________________________________
>     Users mailing list
>     Users at lists.ironpython.com
>     http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Users mailing list
> Users at lists.ironpython.com
> http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
>   


-- 
http://www.ironpythoninaction.com/
http://www.theotherdelia.co.uk/
http://www.voidspace.org.uk/
http://www.ironpython.info/
http://www.resolverhacks.net/