|
@@
-1,74
+1,77
b''
|
|
1
|
IPython is licensed under the terms of the new or revised BSD license, as follows:
|
|
1
|
IPython is licensed under the terms of the new or revised BSD license, as follows:
|
|
2
|
|
|
2
|
|
|
3
|
Copyright (c) 2008, IPython Development Team
|
|
3
|
Copyright (c) 2008, IPython Development Team
|
|
4
|
|
|
4
|
|
|
5
|
All rights reserved.
|
|
5
|
All rights reserved.
|
|
6
|
|
|
6
|
|
|
7
|
Redistribution and use in source and binary forms, with or without modification,
|
|
7
|
Redistribution and use in source and binary forms, with or without modification,
|
|
8
|
are permitted provided that the following conditions are met:
|
|
8
|
are permitted provided that the following conditions are met:
|
|
9
|
|
|
9
|
|
|
10
|
Redistributions of source code must retain the above copyright notice, this list of
|
|
10
|
Redistributions of source code must retain the above copyright notice, this list of
|
|
11
|
conditions and the following disclaimer.
|
|
11
|
conditions and the following disclaimer.
|
|
12
|
|
|
12
|
|
|
13
|
Redistributions in binary form must reproduce the above copyright notice, this list
|
|
13
|
Redistributions in binary form must reproduce the above copyright notice, this list
|
|
14
|
of conditions and the following disclaimer in the documentation and/or other
|
|
14
|
of conditions and the following disclaimer in the documentation and/or other
|
|
15
|
materials provided with the distribution.
|
|
15
|
materials provided with the distribution.
|
|
16
|
|
|
16
|
|
|
17
|
Neither the name of the IPython Development Team nor the names of its contributors
|
|
17
|
Neither the name of the IPython Development Team nor the names of its contributors
|
|
18
|
may be used to endorse or promote products derived from this software without
|
|
18
|
may be used to endorse or promote products derived from this software without
|
|
19
|
specific prior written permission.
|
|
19
|
specific prior written permission.
|
|
20
|
|
|
20
|
|
|
21
|
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY
|
|
21
|
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY
|
|
22
|
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
|
|
22
|
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
|
|
23
|
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
|
|
23
|
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
|
|
24
|
IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
|
|
24
|
IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
|
|
25
|
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
|
|
25
|
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
|
|
26
|
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
|
|
26
|
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
|
|
27
|
PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
|
|
27
|
PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
|
|
28
|
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
|
|
28
|
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
|
|
29
|
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
|
|
29
|
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
|
|
30
|
POSSIBILITY OF SUCH DAMAGE.
|
|
30
|
POSSIBILITY OF SUCH DAMAGE.
|
|
31
|
|
|
31
|
|
|
32
|
About the IPython Development Team
|
|
32
|
About the IPython Development Team
|
|
33
|
----------------------------------
|
|
33
|
----------------------------------
|
|
34
|
|
|
34
|
|
|
|
|
|
35
|
Fernando Perez began IPython in 2001 based on code from Janko Hauser <jhauser@zscout.de>
|
|
|
|
|
36
|
and Nathaniel Gray <n8gray@caltech.edu>. Fernando is still the project lead.
|
|
|
|
|
37
|
|
|
35
|
The IPython Development Team is the set of all contributors to the IPython project.
|
|
38
|
The IPython Development Team is the set of all contributors to the IPython project.
|
|
36
|
This includes all of the IPython subprojects. Here is a list of the currently active contributors:
|
|
39
|
This includes all of the IPython subprojects. Here is a list of the currently active contributors:
|
|
37
|
|
|
40
|
|
|
38
|
* Matthieu Brucher
|
|
41
|
* Matthieu Brucher
|
|
39
|
* Ondrej Certik
|
|
42
|
* Ondrej Certik
|
|
40
|
* Laurent Dufrechou
|
|
43
|
* Laurent Dufrechou
|
|
41
|
* Robert Kern
|
|
44
|
* Robert Kern
|
|
42
|
* Brian E. Granger
|
|
45
|
* Brian E. Granger
|
|
43
|
* Fernando Perez (project leader)
|
|
46
|
* Fernando Perez (project leader)
|
|
44
|
* Benjamin Ragan-Kelley
|
|
47
|
* Benjamin Ragan-Kelley
|
|
45
|
* Ville M. Vainio
|
|
48
|
* Ville M. Vainio
|
|
46
|
* Gael Varoququx
|
|
49
|
* Gael Varoququx
|
|
47
|
* Stefan van der Walt
|
|
50
|
* Stefan van der Walt
|
|
48
|
* Tech-X Corporation
|
|
51
|
* Tech-X Corporation
|
|
49
|
* Barry Wark
|
|
52
|
* Barry Wark
|
|
50
|
|
|
53
|
|
|
51
|
If your name is missing, please add it.
|
|
54
|
If your name is missing, please add it.
|
|
52
|
|
|
55
|
|
|
53
|
Our Copyright Policy
|
|
56
|
Our Copyright Policy
|
|
54
|
--------------------
|
|
57
|
--------------------
|
|
55
|
|
|
58
|
|
|
56
|
IPython uses a shared copyright model. Each contributor maintains copyright over
|
|
59
|
IPython uses a shared copyright model. Each contributor maintains copyright over
|
|
57
|
their contributions to IPython. But, it is important to note that these
|
|
60
|
their contributions to IPython. But, it is important to note that these
|
|
58
|
contributions are typically only changes to the repositories. Thus, the IPython
|
|
61
|
contributions are typically only changes to the repositories. Thus, the IPython
|
|
59
|
source code, in its entirety is not the copyright of any single person or
|
|
62
|
source code, in its entirety is not the copyright of any single person or
|
|
60
|
institution. Instead, it is the collective copyright of the entire IPython
|
|
63
|
institution. Instead, it is the collective copyright of the entire IPython
|
|
61
|
Development Team. If individual contributors want to maintain a record of what
|
|
64
|
Development Team. If individual contributors want to maintain a record of what
|
|
62
|
changes/contributions they have specific copyright on, they should indicate their
|
|
65
|
changes/contributions they have specific copyright on, they should indicate their
|
|
63
|
copyright in the commit message of the change, when they commit the change to
|
|
66
|
copyright in the commit message of the change, when they commit the change to
|
|
64
|
one of the IPython repositories.
|
|
67
|
one of the IPython repositories.
|
|
65
|
|
|
68
|
|
|
66
|
With this in mind, the following banner should be used in any source code file to
|
|
69
|
With this in mind, the following banner should be used in any source code file to
|
|
67
|
indicate the copyright and license terms:
|
|
70
|
indicate the copyright and license terms:
|
|
68
|
|
|
71
|
|
|
69
|
#-------------------------------------------------------------------------------
|
|
72
|
#-------------------------------------------------------------------------------
|
|
70
|
# Copyright (C) 2008 The IPython Development Team
|
|
73
|
# Copyright (C) 2008 The IPython Development Team
|
|
71
|
#
|
|
74
|
#
|
|
72
|
# Distributed under the terms of the BSD License. The full license is in
|
|
75
|
# Distributed under the terms of the BSD License. The full license is in
|
|
73
|
# the file COPYING, distributed as part of this software.
|
|
76
|
# the file COPYING, distributed as part of this software.
|
|
74
|
#-------------------------------------------------------------------------------
No newline at end of file
|
|
77
|
#-------------------------------------------------------------------------------
|