(original) (raw)

[From nobody Sun Sep 26 20:31:45 2004 Message-ID: 41570A56.2040703@mn.rr.com Date: Sun, 26 Sep 2004 13:28:38 -0500 From: J Raynor raynorj@mn.rr.com User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040803 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jeff Epler jepler@unpythonic.net Subject: Re: [Python-Dev] using openssh's pty code References: 41566546.7020601@mn.rr.com 20040926133257.GA2645@unpythonic.net In-Reply-To: 20040926133257.GA2645@unpythonic.net Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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. I don't think not being familiar with the openssh code could be an issue. If I'm not familiar enough with it, I simply won't be able to submit a patch and the entire issue dies. Jeff Epler wrote: >A year or so ago, it was suggested that we take some code from glib for >string-to-float conversion(?). As far as I remember, after the license >issues were resolved, the remaining issue was that the contributor was >not himself familiar with the code. I don't know what eventually >happened. You might look for this thread in python-dev archives. I >think this is an entry point into that thread: > http://mail.python.org/pipermail/python-dev/2003-August/037744.html > >Jeff > > ]