[Fwd: Re: [Python-Dev] using openssh's pty code]

[J Raynor]

The code that I would borrow from openssh basically states that you can 
use it if you include in your derived work the copyright notice and 
disclaimer found in the file you want to borrow from.  This sounds like 
it would pose no problems for incorporating into python, but I'm no 
expert on this, so I thought I'd ask.

Looking at some of the python source, I can see that there are several 
files that contain just such notices.  For example, from the Modules 
directory:

addrinfo.h
md5.h
regexpr.h
timing.h
_bsddb.c
getaddrinfo.c
_localemodule.c
parsermodule.c
syslogmodule.c


Perhaps my original question led you to believe that the openssh license 
was unusual, or had problematic clauses in it.  Given the somewhat 
clarified description above of what's required to borrow openssh code, 
do you still have reservations about receiving patches containing it?



Martin v. Löwis wrote:
>> Well, I'm not sure how that applies.  I didn't see any mention of 
>> licenses in the thread you pointed me to, but even if that thread (or 
>> some other one) showed that it was ok to use glib code in python, that 
>> doesn't mean I can put openssh code into python because the glib and 
>> openssh licenses are different.
> 
> 
> My personal view is that we can only accept code contributions from
> the original author, in general. There have been exceptions in the
> past, when we have shipped a wrapper for a library along with the
> source code of the library, however, there should be a very good reason
> for that, e.g. that the functionality in the library is unique.
> 
> In the specific case, I do believe it would be better to write
> a pty module from scratch instead of adjusting openssh code.
> 
> Regards,
> Martin
>