Python许可证(2.3) [英] Python license (2.3)

查看:147
本文介绍了Python许可证(2.3)的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我已经使用python 2.3创建了一个派生自Queue模块的模块

。我想为其他人提供这个模块(称为

tube)。但是不清楚

我怎么能按照python

许可证来做这件事。


首先看来我必须对我的模块与原版的不同之处进行分析。


第二,似乎我必须在

我的代码:


版权所有(c)2001,2002 Python软件基金会;

保留所有权利


我理解正确吗?


因为我不介意第一个但我不太开心

with第二。还有其他我需要的东西

要小心吗?


-

Antoon Pardon

解决方案

Antoon Pardon写道:

我已经使用python 2.3创建了一个从Queue模块派生的模块。我想让这个模块(称为
tube)可供其他人使用。但是我不清楚如何按照python
许可证来做这件事。

首先,我似乎必须对如何做我的模块与原版不同。

这似乎主要适用于因为这是Python发行版的衍生产品

。因此,您的描述可能会受到限制

以删除剩余的分发。然后是具体的细节

您的更改使Queue成为管。

第二,似乎我必须在
我的代码中包含以下内容:

Copyright(c)2001,2002 Python Software Foundation;
保留所有权利

我是否理解正确?

我相信。

因为我不介意第一个但我不太高兴
第二个。还有其他我需要注意的事项吗?



由于PSF拥有您从中获得的原创作品的版权,

你有已经同意在任何分布式衍生作品中这样做:

http://www.python.org/2.3/license.html


清楚地说但是提供了PSF的许可证协议和

PSF的版权声明,即Copyright(c)2001,2002,2003 Python

Software Foundation;保留所有权利保留在Python 2.3

单独或由被许可方准备的任何衍生版本中。​​""


我们应该等到你发布管然后删除*您的*归属

申请代码为我们自己的代码?


问候

Steve

-

Steve Holden +1 703 861 4237 +1 800 494 3119

Holden Web LLC http://www.holdenweb.com/

Python Web Programming http://pydish.holdenweb.com/


Op 2005-04 -12,Steve Holden schreef< st *** @ holdenweb.com>:

Antoon Pardon写道:

我已经创建了一个派生自Queue模块的模块<与python 2.3。我想让这个模块(称为
tube)可供其他人使用。但是我不清楚如何按照python
许可证来做这件事。

首先,我似乎必须对如何做我的模块与原版不同。


这似乎主要适用于因为它是Python发行版的衍生产品。因此,您的描述可能会被限制为删除其余的分发。然后是您的更改的具体细节,使Queue成为管。

其次,似乎我必须在我的代码中包含以下内容:

Copyright(c)2001,2002 Python Software Foundation;
保留所有权利

我理解正确吗?


我相信。

因为我不介意第一个,但我不太高兴
第二个。还有其他我需要注意的事项吗?


由于PSF拥有您从中获得原创作品的版权,
您已经同意在任何分发版中执行此操作衍生作品:

http://www.python .org / 2.3 / license.html

清楚地说但是提供了PSF的许可协议和PSF的通知版权所有,即Copyright(c)2001,2002,2003 Python
Software Foundation;保留所有权利仅在Python 2.3中保留,或者在被许可方准备的任何衍生版本中保留。""

我们应该等到您发布管道然后删除*您的*归属将代码声称为我们自己的代码?




哦,我知道,我必须在我自己的旁边包含该属性。

我不知何故认为我必须将我的版权移交给Python软件基金会。


我可以使用哪些许可证?在某个地方他们说你可以将python

代码与GPL代码结合起来。这是否意味着生成的代码具有

以将GPL许可证作为PSF许可证,因为两者似乎都希望衍生作品使用相同的许可证。


-

Antoon Pardon


2005年4月12日星期二09:51,Antoon Pardon写道:

似乎我必须在我的代码中包含以下内容:

Copyright(c)2001,2002 Python Software Foundation;
All保留的权利

我是否理解正确?




您当然可以*添加*您自己的版权声明:


" Copyright(c)2001,2002 Python Software Foundation;

保留所有权利

版权所有(c)2005 Antoon Pardon;

保留所有权利


-----开始PGP签名-----

版本:GnuPG v1.2.4( GNU / Linux)

iD8DBQBCW8w0Y6W16wIJgxQRAoaZAKCliuTwT8WuD92 + zX3U9A IvC pvaGgCffM0B

Kch1nH7PzJtD1NbAvS / vvtg =

= ciFp

----- END PGP SIGNATURE -----


I have made a module derived from the Queue module deliverd
with python 2.3. I would like to make this module (called
tube) available for other people. However it is not clear
to me how I can do this in accordance with the python
license.

First of all it seems I have to make a sumary of how
my module differs from the original.

Second it seems I have to include the following in
my code:

"Copyright (c) 2001, 2002 Python Software Foundation;
All Rights Reserved"

Do I understand correctly?

Because I don''t mind the first but I''m not so happy
with the second. Are there other things I have to
watch out for?

--
Antoon Pardon

解决方案

Antoon Pardon wrote:

I have made a module derived from the Queue module deliverd
with python 2.3. I would like to make this module (called
tube) available for other people. However it is not clear
to me how I can do this in accordance with the python
license.

First of all it seems I have to make a sumary of how
my module differs from the original.
That would seem to apply primarily because this is a derivative product
of a Python distribution. Therefore, your description could be limited
to "removed the rest of the distribution" followed by specific details
of your changes making Queue into tube.
Second it seems I have to include the following in
my code:

"Copyright (c) 2001, 2002 Python Software Foundation;
All Rights Reserved"

Do I understand correctly?
I believe so.
Because I don''t mind the first but I''m not so happy
with the second. Are there other things I have to
watch out for?


Since the PSF copyrighted the original work from which you are deriving,
you have already agreed to do this in any distributed derived work:

http://www.python.org/2.3/license.html

clearly says """provided, however, that PSF''s License Agreement and
PSF''s notice of copyright, i.e., "Copyright (c) 2001, 2002, 2003 Python
Software Foundation; All Rights Reserved" are retained in Python 2.3
alone or in any derivative version prepared by Licensee."""

Should we wait until you publish tube and then remove *your* attribution
to claim the code as our own?

regards
Steve
--
Steve Holden +1 703 861 4237 +1 800 494 3119
Holden Web LLC http://www.holdenweb.com/
Python Web Programming http://pydish.holdenweb.com/


Op 2005-04-12, Steve Holden schreef <st***@holdenweb.com>:

Antoon Pardon wrote:

I have made a module derived from the Queue module deliverd
with python 2.3. I would like to make this module (called
tube) available for other people. However it is not clear
to me how I can do this in accordance with the python
license.

First of all it seems I have to make a sumary of how
my module differs from the original.


That would seem to apply primarily because this is a derivative product
of a Python distribution. Therefore, your description could be limited
to "removed the rest of the distribution" followed by specific details
of your changes making Queue into tube.

Second it seems I have to include the following in
my code:

"Copyright (c) 2001, 2002 Python Software Foundation;
All Rights Reserved"

Do I understand correctly?


I believe so.

Because I don''t mind the first but I''m not so happy
with the second. Are there other things I have to
watch out for?


Since the PSF copyrighted the original work from which you are deriving,
you have already agreed to do this in any distributed derived work:

http://www.python.org/2.3/license.html

clearly says """provided, however, that PSF''s License Agreement and
PSF''s notice of copyright, i.e., "Copyright (c) 2001, 2002, 2003 Python
Software Foundation; All Rights Reserved" are retained in Python 2.3
alone or in any derivative version prepared by Licensee."""

Should we wait until you publish tube and then remove *your* attribution
to claim the code as our own?



Oh I see, I just have to include that attribution, next to my own.
I somehow got the idea that I had to hand over my copyright to
the Python Software Foundation.

What licence can I use? Somewhere they say you can combine python
code with GPL code. Does that mean that the resulting code has
to have both the GPL license as the PSF license, as both seem
to want that derived work uses the same license.

--
Antoon Pardon


On Tuesday 12 April 2005 09:51, Antoon Pardon wrote:

It seems I have to include the following in
my code:

"Copyright (c) 2001, 2002 Python Software Foundation;
All Rights Reserved"

Do I understand correctly?



You are of course allowed to *add* your own copyright statement:

"Copyright (c) 2001, 2002 Python Software Foundation;
All Rights Reserved
Copyright (c) 2005 Antoon Pardon;
All Rights Reserved"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQBCW8w0Y6W16wIJgxQRAoaZAKCliuTwT8WuD92+zX3U9A IvCpvaGgCffM0B
Kch1nH7PzJtD1NbAvS/vvtg=
=ciFp
-----END PGP SIGNATURE-----


这篇关于Python许可证(2.3)的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆