From Christina.Zanette at bryancave.com Fri Sep 13 16:27:12 2013 From: Christina.Zanette at bryancave.com (Zanette, Christina) Date: Fri, 13 Sep 2013 14:27:12 +0000 Subject: [Python-legal-sig] Export Python software Message-ID: Good afternoon, I have a client who plans to export Python software, specifically version 2.7.5., from the United States to another country. I am trying to determine the correct Export Control Classification Number and authority for export for Python software. Could you kindly confirm that this software contains or otherwise uses encryption (or other information security, e.g. hashing)? If yes, could you please describe the encryption, including algorithms, key length, etc? I believe the software may be classified as ECCN 5D002, however I would appreciate your confirmation for the two questions stated above. In addition, is there a CCATS or encryption registration associated with this software? Finally, if this product is 5D002, can you confirm if it qualifies for a license exception (for instance license exception ENC (Encryption Commodities, Software and Technology), under the requirements of (b)(1) - self classification, (b)(2) - Encryption restricted; or (b)(3) encryption unrestricted? Many thanks in advance for any assistance you can provide. Regards, Christina Zanette Bryan Cave LLP Christina.zanette at bryancave.com 1155 F Street, NW Washington, DC 20004 Tel: 202.508.6145 Fax: 202.220.7445 ________________________________ This electronic message is from a law firm. It may contain confidential or privileged information. If you received this transmission in error, please reply to the sender to advise of the error and delete this transmission and any attachments. IRS Circular 230 Disclosure: To ensure compliance with requirements imposed by the IRS, we inform you that any U.S. federal tax advice contained in this communication (including any attachments) is not intended or written to be used, and cannot be used, for the purpose of (i) avoiding penalties under the Internal Revenue Code or (ii) promoting, marketing, or recommending to another party any transaction or matter addressed herein. bcllp2013 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mal at python.org Fri Sep 13 17:36:58 2013 From: mal at python.org (M.-A. Lemburg) Date: Fri, 13 Sep 2013 17:36:58 +0200 Subject: [Python-legal-sig] Export Python software In-Reply-To: References: Message-ID: <5233311A.1050309@python.org> Good afternoon, I am sorry, but we cannot provide legal advice on this matter. This is the information we have on the topic of export rules, but it is somewhat outdated with respect to the US export laws: https://wiki.python.org/moin/PythonSoftwareFoundationLicenseFaq#Is_Python_subject_to_export_laws.3F Python 2.7.5 source code only contains hashing algorithms, no encryption algorithms. It does contain wrapper code that allows using OpenSSL, if available. The Windows installers we ship also include the OpenSSL libraries, which includes hashes and ciphers among other things. Regards, -- Marc-Andre Lemburg Director Python Software Foundation http://www.python.org/psf/ On 13.09.2013 16:27, Zanette, Christina wrote: > > Good afternoon, > > I have a client who plans to export Python software, specifically version 2.7.5., from the United States to another country. I am trying to determine the correct Export Control Classification Number and authority for export for Python software. > > Could you kindly confirm that this software contains or otherwise uses encryption (or other information security, e.g. hashing)? If yes, could you please describe the encryption, including algorithms, key length, etc? I believe the software may be classified as ECCN 5D002, however I would appreciate your confirmation for the two questions stated above. > > In addition, is there a CCATS or encryption registration associated with this software? Finally, if this product is 5D002, can you confirm if it qualifies for a license exception (for instance license exception ENC (Encryption Commodities, Software and Technology), under the requirements of (b)(1) - self classification, (b)(2) - Encryption restricted; or (b)(3) encryption unrestricted? > > Many thanks in advance for any assistance you can provide. > > Regards, > > Christina Zanette > Bryan Cave LLP > Christina.zanette at bryancave.com > 1155 F Street, NW > Washington, DC 20004 > Tel: 202.508.6145 > Fax: 202.220.7445 > > > ________________________________ > > This electronic message is from a law firm. It may contain confidential or privileged information. If you received this transmission in error, please reply to the sender to advise of the error and delete this transmission and any attachments. > > IRS Circular 230 Disclosure: To ensure compliance with requirements imposed by the IRS, we inform you that any U.S. federal tax advice contained in this communication (including any attachments) is not intended or written to be used, and cannot be used, for the purpose of (i) avoiding penalties under the Internal Revenue Code or (ii) promoting, marketing, or recommending to another party any transaction or matter addressed herein. > bcllp2013 > > > > _______________________________________________ > Python-legal-sig mailing list > Python-legal-sig at python.org > https://mail.python.org/mailman/listinfo/python-legal-sig > From mal at egenix.com Fri Sep 13 18:12:12 2013 From: mal at egenix.com (M.-A. Lemburg) Date: Fri, 13 Sep 2013 18:12:12 +0200 Subject: [Python-legal-sig] Export Python software In-Reply-To: References: Message-ID: <5233395C.9080805@egenix.com> Good afternoon, I am sorry, but we cannot provide legal advice on this matter. This is the information we have on the topic of export rules, but it is somewhat outdated with respect to the US export laws: https://wiki.python.org/moin/PythonSoftwareFoundationLicenseFaq#Is_Python_subject_to_export_laws.3F Python 2.7.5 source code only contains hashing algorithms, no encryption algorithms. It does contain wrapper code that allows using OpenSSL, if available. The Windows installers we ship also include the OpenSSL libraries, which includes hashes and ciphers among other things. Regards, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Sep 13 2013) >>> Python Projects, Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope/Plone.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2013-09-11: Released eGenix PyRun 1.3.0 ... http://egenix.com/go49 2013-09-04: Released eGenix pyOpenSSL 0.13.2 ... http://egenix.com/go48 2013-09-20: PyCon UK 2013, Coventry, UK ... 7 days to go eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/ On 13.09.2013 16:27, Zanette, Christina wrote: > > Good afternoon, > > I have a client who plans to export Python software, specifically version 2.7.5., from the United States to another country. I am trying to determine the correct Export Control Classification Number and authority for export for Python software. > > Could you kindly confirm that this software contains or otherwise uses encryption (or other information security, e.g. hashing)? If yes, could you please describe the encryption, including algorithms, key length, etc? I believe the software may be classified as ECCN 5D002, however I would appreciate your confirmation for the two questions stated above. > > In addition, is there a CCATS or encryption registration associated with this software? Finally, if this product is 5D002, can you confirm if it qualifies for a license exception (for instance license exception ENC (Encryption Commodities, Software and Technology), under the requirements of (b)(1) - self classification, (b)(2) - Encryption restricted; or (b)(3) encryption unrestricted? > > Many thanks in advance for any assistance you can provide. > > Regards, > > Christina Zanette > Bryan Cave LLP > Christina.zanette at bryancave.com > 1155 F Street, NW > Washington, DC 20004 > Tel: 202.508.6145 > Fax: 202.220.7445 > > > ________________________________ > > This electronic message is from a law firm. It may contain confidential or privileged information. If you received this transmission in error, please reply to the sender to advise of the error and delete this transmission and any attachments. > > IRS Circular 230 Disclosure: To ensure compliance with requirements imposed by the IRS, we inform you that any U.S. federal tax advice contained in this communication (including any attachments) is not intended or written to be used, and cannot be used, for the purpose of (i) avoiding penalties under the Internal Revenue Code or (ii) promoting, marketing, or recommending to another party any transaction or matter addressed herein. > bcllp2013 > > > > _______________________________________________ > Python-legal-sig mailing list > Python-legal-sig at python.org > https://mail.python.org/mailman/listinfo/python-legal-sig > From victor.stinner at gmail.com Mon Sep 23 10:15:46 2013 From: victor.stinner at gmail.com (Victor Stinner) Date: Mon, 23 Sep 2013 10:15:46 +0200 Subject: [Python-legal-sig] Include BSD code into Python? Message-ID: Hi, I would like to reuse code from the libcfu project in Python: http://sourceforge.net/projects/libcfu/ Here is the license: --- Creation date: 2005-06-24 21:22:40 Authors: Don Change log: Copyright (c) 2005 Don Owens All rights reserved. This code is released under the BSD license: Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: * Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. * Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. * Neither the name of the author nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. --- Can you confirm me that this BSD 3-clauses license is compatible with the Python license? I'm using libcfu hash table in my new tracemalloc module (PEP 454): http://hg.python.org/features/tracemalloc/file/ac693c811b1d/Modules/_tracemalloc.c#l1 I heavily modified the code of the hash table, but I would like to keep the original author and the copyright notice. I contacted the author (Don Owens aka regexguy): me>> I would like to know if the BSD 3-clause license if me>> compatible with me>> the Python license don> I believe so. It basically allows you to use the code any way you want, don> as long as you include the copyright notice and attribution in the code. Victor From techtonik at gmail.com Tue Sep 24 18:20:55 2013 From: techtonik at gmail.com (anatoly techtonik) Date: Tue, 24 Sep 2013 19:20:55 +0300 Subject: [Python-legal-sig] Include BSD code into Python? In-Reply-To: References: Message-ID: On Mon, Sep 23, 2013 at 11:15 AM, Victor Stinner wrote: > > Can you confirm me that this BSD 3-clauses license is compatible with > the Python license? > > I'm using libcfu hash table in my new tracemalloc module (PEP 454): > > http://hg.python.org/features/tracemalloc/file/ac693c811b1d/Modules/_tracemalloc.c#l1 > > I heavily modified the code of the hash table, but I would like to > keep the original author and the copyright notice. > > I contacted the author (Don Owens aka regexguy): > > me>> I would like to know if the BSD 3-clause license if > me>> compatible with > me>> the Python license > > don> I believe so. It basically allows you to use the code any way you > want, > don> as long as you include the copyright notice and attribution in the > code. > Not only in the code. Compiled CPython binaries should be accompanied with other way of expressing that CPython includes this work. This clause says this explicitly. * Redistributions in binary form must reproduce the above > copyright notice, this list of conditions and the following > disclaimer in the documentation and/or other materials provided > with the distribution. > -- anatoly t. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben+python at benfinney.id.au Wed Sep 25 01:29:22 2013 From: ben+python at benfinney.id.au (Ben Finney) Date: Wed, 25 Sep 2013 09:29:22 +1000 Subject: [Python-legal-sig] Include BSD code into Python? References: Message-ID: <7wfvstvlwt.fsf@benfinney.id.au> Victor Stinner writes: > Can you confirm me that this BSD 3-clauses license is compatible with > the Python license? Yes, it is compatible. This means that it is feasible to derive a work from both the current Python and the work you're referring to, and distribute the result as free software. Of course, all the terms of all the licenses must be simultaneously satisfied when distributing that derived work. > I'm using libcfu hash table in my new tracemalloc module (PEP 454): > http://hg.python.org/features/tracemalloc/file/ac693c811b1d/Modules/_tracemalloc.c#l1 > > I heavily modified the code of the hash table, but I would like to > keep the original author and the copyright notice. It's good that you would like that, because that's one of the terms you need to satisfy in order to have license to distribute the work :-) > I contacted the author (Don Owens aka regexguy): > > me>> I would like to know if the BSD 3-clause license if > me>> compatible with > me>> the Python license > > don> I believe so. It basically allows you to use the code any way you want, > don> as long as you include the copyright notice and attribution in the code. Yes, where ?the code? is any form of the code: i.e., distributing the work in source form or binary form or any other form. To redistribute the work under that license, the work's license text would need to be included as part of the distributed derived work. In practice, that would mean CPython would need to incude the ?libcfu? copyright holder's name and the work's license text in every copy distributed thereafter, or there would be no license to distribute the resulting work. Whether that's acceptable to the PSF is a separate matter. -- \ ?Kissing a smoker is like licking an ashtray.? ?anonymous | `\ | _o__) | Ben Finney From jnoller at gmail.com Wed Sep 25 01:32:08 2013 From: jnoller at gmail.com (Jesse Noller) Date: Tue, 24 Sep 2013 18:32:08 -0500 Subject: [Python-legal-sig] Include BSD code into Python? In-Reply-To: <7wfvstvlwt.fsf@benfinney.id.au> References: <7wfvstvlwt.fsf@benfinney.id.au> Message-ID: Maintaining the original copyright in python core is fine. Lots of files have that, and BSD headers > On Sep 24, 2013, at 6:29 PM, Ben Finney wrote: > > Victor Stinner writes: > >> Can you confirm me that this BSD 3-clauses license is compatible with >> the Python license? > > Yes, it is compatible. This means that it is feasible to derive a work > from both the current Python and the work you're referring to, and > distribute the result as free software. > > Of course, all the terms of all the licenses must be simultaneously > satisfied when distributing that derived work. > >> I'm using libcfu hash table in my new tracemalloc module (PEP 454): >> http://hg.python.org/features/tracemalloc/file/ac693c811b1d/Modules/_tracemalloc.c#l1 >> >> I heavily modified the code of the hash table, but I would like to >> keep the original author and the copyright notice. > > It's good that you would like that, because that's one of the terms you > need to satisfy in order to have license to distribute the work :-) > >> I contacted the author (Don Owens aka regexguy): >> >> me>> I would like to know if the BSD 3-clause license if >> me>> compatible with >> me>> the Python license >> >> don> I believe so. It basically allows you to use the code any way you want, >> don> as long as you include the copyright notice and attribution in the code. > > Yes, where ?the code? is any form of the code: i.e., distributing the > work in source form or binary form or any other form. To redistribute > the work under that license, the work's license text would need to be > included as part of the distributed derived work. > > In practice, that would mean CPython would need to incude the ?libcfu? > copyright holder's name and the work's license text in every copy > distributed thereafter, or there would be no license to distribute the > resulting work. > > Whether that's acceptable to the PSF is a separate matter. > > -- > \ ?Kissing a smoker is like licking an ashtray.? ?anonymous | > `\ | > _o__) | > Ben Finney > > _______________________________________________ > Python-legal-sig mailing list > Python-legal-sig at python.org > https://mail.python.org/mailman/listinfo/python-legal-sig From techtonik at gmail.com Wed Sep 25 12:57:00 2013 From: techtonik at gmail.com (anatoly techtonik) Date: Wed, 25 Sep 2013 13:57:00 +0300 Subject: [Python-legal-sig] Include BSD code into Python? In-Reply-To: References: <7wfvstvlwt.fsf@benfinney.id.au> Message-ID: On Wed, Sep 25, 2013 at 2:32 AM, Jesse Noller wrote: > Maintaining the original copyright in python core is fine. Lots of files > have that, and BSD headers Yes, look at LICENSE.txt distributed with CPython version - there is a lot of BSD licenses. -- anatoly t. -------------- next part -------------- An HTML attachment was scrubbed... URL: From victor.stinner at gmail.com Wed Sep 25 12:56:31 2013 From: victor.stinner at gmail.com (Victor Stinner) Date: Wed, 25 Sep 2013 12:56:31 +0200 Subject: [Python-legal-sig] Include BSD code into Python? In-Reply-To: References: <7wfvstvlwt.fsf@benfinney.id.au> Message-ID: 2013/9/25 Jesse Noller : > Maintaining the original copyright in python core is fine. Lots of files have that, and BSD headers Ok, but where should we include the copyright notice for binary Python? In the documentation? I see that the following page contains many licenses: http://docs.python.org/dev/license.html Is it the right place to copy the copyright notice? Victor > >> On Sep 24, 2013, at 6:29 PM, Ben Finney wrote: >> >> Victor Stinner writes: >> >>> Can you confirm me that this BSD 3-clauses license is compatible with >>> the Python license? >> >> Yes, it is compatible. This means that it is feasible to derive a work >> from both the current Python and the work you're referring to, and >> distribute the result as free software. >> >> Of course, all the terms of all the licenses must be simultaneously >> satisfied when distributing that derived work. >> >>> I'm using libcfu hash table in my new tracemalloc module (PEP 454): >>> http://hg.python.org/features/tracemalloc/file/ac693c811b1d/Modules/_tracemalloc.c#l1 >>> >>> I heavily modified the code of the hash table, but I would like to >>> keep the original author and the copyright notice. >> >> It's good that you would like that, because that's one of the terms you >> need to satisfy in order to have license to distribute the work :-) >> >>> I contacted the author (Don Owens aka regexguy): >>> >>> me>> I would like to know if the BSD 3-clause license if >>> me>> compatible with >>> me>> the Python license >>> >>> don> I believe so. It basically allows you to use the code any way you want, >>> don> as long as you include the copyright notice and attribution in the code. >> >> Yes, where ?the code? is any form of the code: i.e., distributing the >> work in source form or binary form or any other form. To redistribute >> the work under that license, the work's license text would need to be >> included as part of the distributed derived work. >> >> In practice, that would mean CPython would need to incude the ?libcfu? >> copyright holder's name and the work's license text in every copy >> distributed thereafter, or there would be no license to distribute the >> resulting work. >> >> Whether that's acceptable to the PSF is a separate matter. >> >> -- >> \ ?Kissing a smoker is like licking an ashtray.? ?anonymous | >> `\ | >> _o__) | >> Ben Finney >> >> _______________________________________________ >> Python-legal-sig mailing list >> Python-legal-sig at python.org >> https://mail.python.org/mailman/listinfo/python-legal-sig > _______________________________________________ > Python-legal-sig mailing list > Python-legal-sig at python.org > https://mail.python.org/mailman/listinfo/python-legal-sig From jnoller at gmail.com Wed Sep 25 13:38:07 2013 From: jnoller at gmail.com (Jesse Noller) Date: Wed, 25 Sep 2013 06:38:07 -0500 Subject: [Python-legal-sig] Include BSD code into Python? In-Reply-To: References: <7wfvstvlwt.fsf@benfinney.id.au> Message-ID: <1759EA10-54BD-4A47-9716-C6312B7A40BF@gmail.com> > On Sep 25, 2013, at 5:56 AM, Victor Stinner wrote: > > 2013/9/25 Jesse Noller : >> Maintaining the original copyright in python core is fine. Lots of files have that, and BSD headers > > Ok, but where should we include the copyright notice for binary > Python? In the documentation? I see that the following page contains > many licenses: > > http://docs.python.org/dev/license.html > > Is it the right place to copy the copyright notice? > > Victor Yup; somewhere near the bottom should be fine unless I'm missing the sort order on the ones after the python license > >> >>> On Sep 24, 2013, at 6:29 PM, Ben Finney wrote: >>> >>> Victor Stinner writes: >>> >>>> Can you confirm me that this BSD 3-clauses license is compatible with >>>> the Python license? >>> >>> Yes, it is compatible. This means that it is feasible to derive a work >>> from both the current Python and the work you're referring to, and >>> distribute the result as free software. >>> >>> Of course, all the terms of all the licenses must be simultaneously >>> satisfied when distributing that derived work. >>> >>>> I'm using libcfu hash table in my new tracemalloc module (PEP 454): >>>> http://hg.python.org/features/tracemalloc/file/ac693c811b1d/Modules/_tracemalloc.c#l1 >>>> >>>> I heavily modified the code of the hash table, but I would like to >>>> keep the original author and the copyright notice. >>> >>> It's good that you would like that, because that's one of the terms you >>> need to satisfy in order to have license to distribute the work :-) >>> >>>> I contacted the author (Don Owens aka regexguy): >>>> >>>> me>> I would like to know if the BSD 3-clause license if >>>> me>> compatible with >>>> me>> the Python license >>>> >>>> don> I believe so. It basically allows you to use the code any way you want, >>>> don> as long as you include the copyright notice and attribution in the code. >>> >>> Yes, where ?the code? is any form of the code: i.e., distributing the >>> work in source form or binary form or any other form. To redistribute >>> the work under that license, the work's license text would need to be >>> included as part of the distributed derived work. >>> >>> In practice, that would mean CPython would need to incude the ?libcfu? >>> copyright holder's name and the work's license text in every copy >>> distributed thereafter, or there would be no license to distribute the >>> resulting work. >>> >>> Whether that's acceptable to the PSF is a separate matter. >>> >>> -- >>> \ ?Kissing a smoker is like licking an ashtray.? ?anonymous | >>> `\ | >>> _o__) | >>> Ben Finney >>> >>> _______________________________________________ >>> Python-legal-sig mailing list >>> Python-legal-sig at python.org >>> https://mail.python.org/mailman/listinfo/python-legal-sig >> _______________________________________________ >> Python-legal-sig mailing list >> Python-legal-sig at python.org >> https://mail.python.org/mailman/listinfo/python-legal-sig > _______________________________________________ > Python-legal-sig mailing list > Python-legal-sig at python.org > https://mail.python.org/mailman/listinfo/python-legal-sig From mal at egenix.com Wed Sep 25 14:04:05 2013 From: mal at egenix.com (M.-A. Lemburg) Date: Wed, 25 Sep 2013 14:04:05 +0200 Subject: [Python-legal-sig] Include BSD code into Python? In-Reply-To: References: <7wfvstvlwt.fsf@benfinney.id.au> Message-ID: <5242D135.5000304@egenix.com> On 25.09.2013 12:56, Victor Stinner wrote: > 2013/9/25 Jesse Noller : >> Maintaining the original copyright in python core is fine. Lots of files have that, and BSD headers > > Ok, but where should we include the copyright notice for binary > Python? In the documentation? I see that the following page contains > many licenses: > > http://docs.python.org/dev/license.html > > Is it the right place to copy the copyright notice? Yes. BTW: I think we should have the same text in the main LICENSE file, since that's being pulled in by the Windows installer. The LICENSE file is currently missing the section with the 3rd party licenses listed in the docs. Perhaps just adding a link at the end of the file, pointing to the above URL would be good. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Sep 25 2013) >>> Python Projects, Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope/Plone.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2013-09-28: PyDDF Sprint ... 3 days to go 2013-10-14: PyCon DE 2013, Cologne, Germany ... 19 days to go ::::: Try our mxODBC.Connect Python Database Interface for free ! :::::: eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/ From victor.stinner at gmail.com Wed Sep 25 13:56:57 2013 From: victor.stinner at gmail.com (Victor Stinner) Date: Wed, 25 Sep 2013 13:56:57 +0200 Subject: [Python-legal-sig] Include BSD code into Python? In-Reply-To: <1759EA10-54BD-4A47-9716-C6312B7A40BF@gmail.com> References: <7wfvstvlwt.fsf@benfinney.id.au> <1759EA10-54BD-4A47-9716-C6312B7A40BF@gmail.com> Message-ID: Ok, I added the copyright notice there: http://www.haypocalc.com/tmp/tracemalloc/license.html#cfuhash (tracemalloc PEP is not accepted yet, so I compiled and copied the doc to my webserver) Commit: http://hg.python.org/features/tracemalloc/rev/23a9bd1b085c Thanks. Victor 2013/9/25 Jesse Noller : > > >> On Sep 25, 2013, at 5:56 AM, Victor Stinner wrote: >> >> 2013/9/25 Jesse Noller : >>> Maintaining the original copyright in python core is fine. Lots of files have that, and BSD headers >> >> Ok, but where should we include the copyright notice for binary >> Python? In the documentation? I see that the following page contains >> many licenses: >> >> http://docs.python.org/dev/license.html >> >> Is it the right place to copy the copyright notice? >> >> Victor > > Yup; somewhere near the bottom should be fine unless I'm missing the sort order on the ones after the python license > >> >>> >>>> On Sep 24, 2013, at 6:29 PM, Ben Finney wrote: >>>> >>>> Victor Stinner writes: >>>> >>>>> Can you confirm me that this BSD 3-clauses license is compatible with >>>>> the Python license? >>>> >>>> Yes, it is compatible. This means that it is feasible to derive a work >>>> from both the current Python and the work you're referring to, and >>>> distribute the result as free software. >>>> >>>> Of course, all the terms of all the licenses must be simultaneously >>>> satisfied when distributing that derived work. >>>> >>>>> I'm using libcfu hash table in my new tracemalloc module (PEP 454): >>>>> http://hg.python.org/features/tracemalloc/file/ac693c811b1d/Modules/_tracemalloc.c#l1 >>>>> >>>>> I heavily modified the code of the hash table, but I would like to >>>>> keep the original author and the copyright notice. >>>> >>>> It's good that you would like that, because that's one of the terms you >>>> need to satisfy in order to have license to distribute the work :-) >>>> >>>>> I contacted the author (Don Owens aka regexguy): >>>>> >>>>> me>> I would like to know if the BSD 3-clause license if >>>>> me>> compatible with >>>>> me>> the Python license >>>>> >>>>> don> I believe so. It basically allows you to use the code any way you want, >>>>> don> as long as you include the copyright notice and attribution in the code. >>>> >>>> Yes, where ?the code? is any form of the code: i.e., distributing the >>>> work in source form or binary form or any other form. To redistribute >>>> the work under that license, the work's license text would need to be >>>> included as part of the distributed derived work. >>>> >>>> In practice, that would mean CPython would need to incude the ?libcfu? >>>> copyright holder's name and the work's license text in every copy >>>> distributed thereafter, or there would be no license to distribute the >>>> resulting work. >>>> >>>> Whether that's acceptable to the PSF is a separate matter. >>>> >>>> -- >>>> \ ?Kissing a smoker is like licking an ashtray.? ?anonymous | >>>> `\ | >>>> _o__) | >>>> Ben Finney >>>> >>>> _______________________________________________ >>>> Python-legal-sig mailing list >>>> Python-legal-sig at python.org >>>> https://mail.python.org/mailman/listinfo/python-legal-sig >>> _______________________________________________ >>> Python-legal-sig mailing list >>> Python-legal-sig at python.org >>> https://mail.python.org/mailman/listinfo/python-legal-sig >> _______________________________________________ >> Python-legal-sig mailing list >> Python-legal-sig at python.org >> https://mail.python.org/mailman/listinfo/python-legal-sig > _______________________________________________ > Python-legal-sig mailing list > Python-legal-sig at python.org > https://mail.python.org/mailman/listinfo/python-legal-sig From techtonik at gmail.com Wed Sep 25 15:14:04 2013 From: techtonik at gmail.com (anatoly techtonik) Date: Wed, 25 Sep 2013 16:14:04 +0300 Subject: [Python-legal-sig] Include BSD code into Python? In-Reply-To: <5242D135.5000304@egenix.com> References: <7wfvstvlwt.fsf@benfinney.id.au> <5242D135.5000304@egenix.com> Message-ID: On Wed, Sep 25, 2013 at 3:04 PM, M.-A. Lemburg wrote: > On 25.09.2013 12:56, Victor Stinner wrote: > > 2013/9/25 Jesse Noller : > >> Maintaining the original copyright in python core is fine. Lots of > files have that, and BSD headers > > > > Ok, but where should we include the copyright notice for binary > > Python? In the documentation? I see that the following page contains > > many licenses: > > > > http://docs.python.org/dev/license.html > > > > Is it the right place to copy the copyright notice? > > Yes. > > BTW: I think we should have the same text in the main LICENSE > file, since that's being pulled in by the Windows installer. > > The LICENSE file is currently missing the section with the 3rd party > licenses listed in the docs. Perhaps just adding a link at the > end of the file, pointing to the above URL would be good. > It makes sense to do vice versa - maintain additional LICENSE.ext file and include that into docs/ on doc building phase. Then alternative implementations of Python can also catch up with requirements and see what are major things to be ported to get Python running on target platforms. -- anatoly t. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mal at egenix.com Wed Sep 25 16:01:41 2013 From: mal at egenix.com (M.-A. Lemburg) Date: Wed, 25 Sep 2013 16:01:41 +0200 Subject: [Python-legal-sig] Include BSD code into Python? In-Reply-To: References: <7wfvstvlwt.fsf@benfinney.id.au> <5242D135.5000304@egenix.com> Message-ID: <5242ECC5.1080802@egenix.com> On 25.09.2013 15:14, anatoly techtonik wrote: > On Wed, Sep 25, 2013 at 3:04 PM, M.-A. Lemburg wrote: > >> On 25.09.2013 12:56, Victor Stinner wrote: >>> 2013/9/25 Jesse Noller : >>>> Maintaining the original copyright in python core is fine. Lots of >> files have that, and BSD headers >>> >>> Ok, but where should we include the copyright notice for binary >>> Python? In the documentation? I see that the following page contains >>> many licenses: >>> >>> http://docs.python.org/dev/license.html >>> >>> Is it the right place to copy the copyright notice? >> >> Yes. >> >> BTW: I think we should have the same text in the main LICENSE >> file, since that's being pulled in by the Windows installer. >> >> The LICENSE file is currently missing the section with the 3rd party >> licenses listed in the docs. Perhaps just adding a link at the >> end of the file, pointing to the above URL would be good. >> > > It makes sense to do vice versa - maintain additional LICENSE.ext file > and include that into docs/ on doc building phase. Then alternative > implementations of Python can also catch up with requirements and > see what are major things to be ported to get Python running on target > platforms. Well, the license.rst isn't all that readable as main license file, so it's probably better to include the 3rd party licenses by reference rather than verbatim. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Sep 25 2013) >>> Python Projects, Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope/Plone.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2013-09-28: PyDDF Sprint ... 3 days to go 2013-10-14: PyCon DE 2013, Cologne, Germany ... 19 days to go ::::: Try our mxODBC.Connect Python Database Interface for free ! :::::: eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/