A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/2010-January/097084.html below:

[Python-Dev] Backported faster RLock to Python 2.6.

[Python-Dev] Backported faster RLock to Python 2.6. [Python-Dev] Backported faster RLock to Python 2.6.Michael Foord fuzzyman at voidspace.org.uk
Thu Jan 7 14:15:09 CET 2010
On 07/01/2010 13:11, Lennart Regebro wrote:
> On Thu, Jan 7, 2010 at 13:23, Nick Coghlan<ncoghlan at gmail.com>  wrote:
>    
>> As Simon pointed out, while some organisations do work that way, the PSF
>> isn't one of them.
>>
>> The PSF only requires that the code be contributed under a license that
>> then allows us to turn around and redistribute it under a different open
>> source license without requesting additional permission from the
>> copyright holder.
>>      
> Even if the contributed code as in this case is a method in an
> existing file? How does that work, how do they keep ownership of one
> method in the threading.py method? :-)
>
>    

When contributing code to Python all work remains copyright the original 
author. The combined work is copyright *everyone*. The PSF has a license 
to distribute it, which is all that is important.

How you meaningfully exercise your ownership over chunks of code is left 
for the reader to determine...

(i.e. copyright and ownership are legal terms that don't necessarily 
mean anything *practical* in these situations.)

Michael


-- 
http://www.ironpythoninaction.com/
http://www.voidspace.org.uk/blog



More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4