[Ironpython-users] external libraries
jschementi at gmail.com
Tue Aug 2 18:04:29 CEST 2011
The projects have multiple licenses because of external dependencies.
In general, if we can keep the compiler and library implementations
Apache 2 that'd be great. If we do need to bring in something with a
different license, it should be it's own assembly.
On Tue, Aug 2, 2011 at 11:53 AM, Slide <slide.o.mix at gmail.com> wrote:
> No, I was actually thinking of pulling something in from Mono which has
> nothing to do with zlib or zipimport :-) I am planning on reusing the
> existing decompression that is currently used in the zlib module for
> zipimport (which is coming along nicely by the way).
> On Tue, Aug 2, 2011 at 8:41 AM, Jeff Hardy <jdhardy at gmail.com> wrote:
>> Unfortunately, I'm not entirely sure. We do include the Python & Ruby
>> stdlibs, which have their own licenses, and zlib.net, which is
>> MIT/BSD. I'm going to hazard a guess that you're thinking of #ZipLib,
>> which is GPL + Classpath, which isn't as scary as it sounds, but still
>> makes me slightly nervous. I'd prefer to avoid it if possible. At the
>> very least, it might be an external, optional dependency.
>> On that note, I did happen across
>> that you might find interesting.
>> - Jeff
>> On Mon, Aug 1, 2011 at 9:30 PM, Slide <slide.o.mix at gmail.com> wrote:
>> > What are the guidelines for bringing in part or all of an external
>> > library?
>> > What licenses are compatible with the rest of the IP source code so it
>> > won't
>> > be tainted by anything?
>> > Thanks,
>> > slide
>> > --
>> > slide-o-blog
>> > http://slide-o-blog.blogspot.com/
>> > _______________________________________________
>> > Ironpython-users mailing list
>> > Ironpython-users at python.org
>> > http://mail.python.org/mailman/listinfo/ironpython-users
> Ironpython-users mailing list
> Ironpython-users at python.org
More information about the Ironpython-users