Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #101413 > unrolled thread

Re: licenses

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: licenses Ben Finney <ben+python@benfinney.id.au> - 2016-01-10 08:50 +1100
    Re: licenses Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2016-01-10 10:22 +0100

#101413 — Re: licenses

"Martinez, Jorge Alberto (GE Aviation)" <JorgeAlberto.Martinez@ge.com>
writes:

> We develop applications here with Python and I want to know if there's
> issues by using. We use NumPy, PyDaqMx, Py Visa

Those are all free software: meaning, every recipient has freedom to
execute, modify, and/or redistribute the work. So long as the code base
you derive from them is also free software, you will not need to take
special care.

If you intend to make a proprietary work (restricting the freedom of
recipients further), you should consult your lawyer about how to go
about that legally.

> How can we cover this licensing?

The simplest way – no need to get lawyers involved – to comply is to
grant a free-software license (e.g. GNU GPL) to all recipients of your
work.

When you want to derive from an existing work but restrict freedom of
your recipients, that's when you need to pay a lawyer for advice. So I
advise you don't make such a restrictive work.

-- 
 \      “The way to build large Python applications is to componentize |
  `\             and loosely-couple the hell out of everything.” —Aahz |
_o__)                                                                  |
Ben Finney

[toc] | [next] | [standalone]

#101431

Ben Finney wrote:

> "Martinez, Jorge Alberto (GE Aviation)" […] writes:
>> We develop applications here with Python and I want to know if there's
>> issues by using. We use NumPy, PyDaqMx, Py Visa
> 
> Those are all free software: meaning, every recipient has freedom to
> execute, modify, and/or redistribute the work.

Correct.

> So long as the code base you derive from them is also free software, you 
> will not need to take special care.

No, not all free software licenses (FSLs) are compatible with each other.  
Most notably, not all FSLs are compatible with the GNU General Public 
License (GPL), which also is a FSL.

Software licenses are distinguished whether they are closed source or open 
source licenses, free or unfree, and enforce copyright or copyleft (the GPL 
are/does the latter, respectively).  Also, patent issues have to be 
considered: Some free software licenses, like the Apache License, include 
stipulations that the grated patent license is void if the licensee sues the 
licenser for patent infringement; other licenses do not.

A quick Google search shows:

- NumPy is licensed under the “BSD-new license”.

  <https://en.wikipedia.org/wiki/NumPy>

- PyDAQmx can be licensed under either

  ,-<https://github.com/clade/PyDAQmx/blob/master/README>
  |
  | (1) The BSD license. 
  | (2) Any other license, as long as it is obtained from the original 
  |     author.

- PyVISA is licensed under “The MIT License” (X11 License)

  <https://github.com/hgrecco/pyvisa/blob/master/LICENSE>

See also:

<https://en.wikipedia.org/wiki/Comparison_of_free_and_open-source_software_licenses>
<http://www.gnu.org/licenses/license-recommendations.html>

IANAL.

-- 
PointedEars

Twitter: @PointedEars2
Please do not cc me. / Bitte keine Kopien per E-Mail.

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web