Skip to content
This repository was archived by the owner on Mar 9, 2026. It is now read-only.

Commit 1069d36

Browse files
exodrifterexodrifter
committed
Add Python 2.6.9 README, LICENSE, and Lib/ folder
Also added an example that uses a python library. minusnode.gif cannot be read by Unity 5.3.0f4, but was included without modification anyway.
1 parent da0a49b commit 1069d36

3,559 files changed

Lines changed: 570281 additions & 0 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎Examples/Library.cs‎

Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,30 @@
1+
using UnityEngine;
2+
using IronPython.Hosting;
3+
4+
namespace Exodrifter.UnityPython.Examples
5+
{
6+
public class Library : MonoBehaviour
7+
{
8+
void Start()
9+
{
10+
var engine = Python.CreateEngine();
11+
var scope = engine.CreateScope();
12+
13+
// Add the python library path to the engine. Note that this will
14+
// not work for builds; you will need to manually place the python
15+
// library files in a place that your code can find it at runtime.
16+
var paths = engine.GetSearchPaths();
17+
paths.Add(Application.dataPath + "/Python/Lib");
18+
engine.SetSearchPaths (paths);
19+
20+
string code = @"
21+
import os
22+
filename = os.path.abspath ('test.txt');";
23+
24+
var source = engine.CreateScriptSourceFromString(code);
25+
source.Execute(scope);
26+
27+
Debug.Log(scope.GetVariable<string>("filename"));
28+
}
29+
}
30+
}

‎Examples/Library.cs.meta‎

Lines changed: 12 additions & 0 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

‎LICENSE_Python.txt‎

Lines changed: 282 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,282 @@
1+
A. HISTORY OF THE SOFTWARE
2+
==========================
3+
4+
Python was created in the early 1990s by Guido van Rossum at Stichting
5+
Mathematisch Centrum (CWI, see http://www.cwi.nl) in the Netherlands
6+
as a successor of a language called ABC. Guido remains Python's
7+
principal author, although it includes many contributions from others.
8+
9+
In 1995, Guido continued his work on Python at the Corporation for
10+
National Research Initiatives (CNRI, see http://www.cnri.reston.va.us)
11+
in Reston, Virginia where he released several versions of the
12+
software.
13+
14+
In May 2000, Guido and the Python core development team moved to
15+
BeOpen.com to form the BeOpen PythonLabs team. In October of the same
16+
year, the PythonLabs team moved to Digital Creations (now Zope
17+
Corporation, see http://www.zope.com). In 2001, the Python Software
18+
Foundation (PSF, see http://www.python.org/psf/) was formed, a
19+
non-profit organization created specifically to own Python-related
20+
Intellectual Property. Zope Corporation is a sponsoring member of
21+
the PSF.
22+
23+
All Python releases are Open Source (see http://www.opensource.org for
24+
the Open Source Definition). Historically, most, but not all, Python
25+
releases have also been GPL-compatible; the table below summarizes
26+
the various releases.
27+
28+
Release Derived Year Owner GPL-
29+
from compatible? (1)
30+
31+
0.9.0 thru 1.2 1991-1995 CWI yes
32+
1.3 thru 1.5.2 1.2 1995-1999 CNRI yes
33+
1.6 1.5.2 2000 CNRI no
34+
2.0 1.6 2000 BeOpen.com no
35+
1.6.1 1.6 2001 CNRI yes (2)
36+
2.1 2.0+1.6.1 2001 PSF no
37+
2.0.1 2.0+1.6.1 2001 PSF yes
38+
2.1.1 2.1+2.0.1 2001 PSF yes
39+
2.2 2.1.1 2001 PSF yes
40+
2.1.2 2.1.1 2002 PSF yes
41+
2.1.3 2.1.2 2002 PSF yes
42+
2.2.1 2.2 2002 PSF yes
43+
2.2.2 2.2.1 2002 PSF yes
44+
2.2.3 2.2.2 2003 PSF yes
45+
2.3 2.2.2 2002-2003 PSF yes
46+
2.3.1 2.3 2002-2003 PSF yes
47+
2.3.2 2.3.1 2002-2003 PSF yes
48+
2.3.3 2.3.2 2002-2003 PSF yes
49+
2.3.4 2.3.3 2004 PSF yes
50+
2.3.5 2.3.4 2005 PSF yes
51+
2.4 2.3 2004 PSF yes
52+
2.4.1 2.4 2005 PSF yes
53+
2.4.2 2.4.1 2005 PSF yes
54+
2.4.3 2.4.2 2006 PSF yes
55+
2.4.4 2.4.3 2006 PSF yes
56+
2.5 2.4 2006 PSF yes
57+
2.5.1 2.5 2007 PSF yes
58+
2.5.2 2.5.1 2008 PSF yes
59+
2.5.3 2.5.2 2008 PSF yes
60+
2.6 2.5 2008 PSF yes
61+
2.6.1 2.6 2008 PSF yes
62+
2.6.2 2.6.1 2009 PSF yes
63+
2.6.3 2.6.2 2009 PSF yes
64+
2.6.4 2.6.3 2009 PSF yes
65+
2.6.5 2.6.4 2010 PSF yes
66+
2.6.6 2.6.5 2010 PSF yes
67+
2.6.7 2.6.6 2011 PSF yes
68+
2.6.8 2.6.7 2012 PSF yes
69+
2.6.9 2.6.8 2013 PSF yes
70+
71+
Footnotes:
72+
73+
(1) GPL-compatible doesn't mean that we're distributing Python under
74+
the GPL. All Python licenses, unlike the GPL, let you distribute
75+
a modified version without making your changes open source. The
76+
GPL-compatible licenses make it possible to combine Python with
77+
other software that is released under the GPL; the others don't.
78+
79+
(2) According to Richard Stallman, 1.6.1 is not GPL-compatible,
80+
because its license has a choice of law clause. According to
81+
CNRI, however, Stallman's lawyer has told CNRI's lawyer that 1.6.1
82+
is "not incompatible" with the GPL.
83+
84+
Thanks to the many outside volunteers who have worked under Guido's
85+
direction to make these releases possible.
86+
87+
88+
B. TERMS AND CONDITIONS FOR ACCESSING OR OTHERWISE USING PYTHON
89+
===============================================================
90+
91+
PYTHON SOFTWARE FOUNDATION LICENSE VERSION 2
92+
--------------------------------------------
93+
94+
1. This LICENSE AGREEMENT is between the Python Software Foundation
95+
("PSF"), and the Individual or Organization ("Licensee") accessing and
96+
otherwise using this software ("Python") in source or binary form and
97+
its associated documentation.
98+
99+
2. Subject to the terms and conditions of this License Agreement, PSF hereby
100+
grants Licensee a nonexclusive, royalty-free, world-wide license to reproduce,
101+
analyze, test, perform and/or display publicly, prepare derivative works,
102+
distribute, and otherwise use Python alone or in any derivative version,
103+
provided, however, that PSF's License Agreement and PSF's notice of copyright,
104+
i.e., "Copyright (c) 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010
105+
Python Software Foundation; All Rights Reserved" are retained in Python alone or
106+
in any derivative version prepared by Licensee.
107+
108+
3. In the event Licensee prepares a derivative work that is based on
109+
or incorporates Python or any part thereof, and wants to make
110+
the derivative work available to others as provided herein, then
111+
Licensee hereby agrees to include in any such work a brief summary of
112+
the changes made to Python.
113+
114+
4. PSF is making Python available to Licensee on an "AS IS"
115+
basis. PSF MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR
116+
IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, PSF MAKES NO AND
117+
DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS
118+
FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON WILL NOT
119+
INFRINGE ANY THIRD PARTY RIGHTS.
120+
121+
5. PSF SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON
122+
FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS
123+
A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON,
124+
OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF.
125+
126+
6. This License Agreement will automatically terminate upon a material
127+
breach of its terms and conditions.
128+
129+
7. Nothing in this License Agreement shall be deemed to create any
130+
relationship of agency, partnership, or joint venture between PSF and
131+
Licensee. This License Agreement does not grant permission to use PSF
132+
trademarks or trade name in a trademark sense to endorse or promote
133+
products or services of Licensee, or any third party.
134+
135+
8. By copying, installing or otherwise using Python, Licensee
136+
agrees to be bound by the terms and conditions of this License
137+
Agreement.
138+
139+
140+
BEOPEN.COM LICENSE AGREEMENT FOR PYTHON 2.0
141+
-------------------------------------------
142+
143+
BEOPEN PYTHON OPEN SOURCE LICENSE AGREEMENT VERSION 1
144+
145+
1. This LICENSE AGREEMENT is between BeOpen.com ("BeOpen"), having an
146+
office at 160 Saratoga Avenue, Santa Clara, CA 95051, and the
147+
Individual or Organization ("Licensee") accessing and otherwise using
148+
this software in source or binary form and its associated
149+
documentation ("the Software").
150+
151+
2. Subject to the terms and conditions of this BeOpen Python License
152+
Agreement, BeOpen hereby grants Licensee a non-exclusive,
153+
royalty-free, world-wide license to reproduce, analyze, test, perform
154+
and/or display publicly, prepare derivative works, distribute, and
155+
otherwise use the Software alone or in any derivative version,
156+
provided, however, that the BeOpen Python License is retained in the
157+
Software, alone or in any derivative version prepared by Licensee.
158+
159+
3. BeOpen is making the Software available to Licensee on an "AS IS"
160+
basis. BEOPEN MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR
161+
IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, BEOPEN MAKES NO AND
162+
DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS
163+
FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE WILL NOT
164+
INFRINGE ANY THIRD PARTY RIGHTS.
165+
166+
4. BEOPEN SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF THE
167+
SOFTWARE FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS
168+
AS A RESULT OF USING, MODIFYING OR DISTRIBUTING THE SOFTWARE, OR ANY
169+
DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF.
170+
171+
5. This License Agreement will automatically terminate upon a material
172+
breach of its terms and conditions.
173+
174+
6. This License Agreement shall be governed by and interpreted in all
175+
respects by the law of the State of California, excluding conflict of
176+
law provisions. Nothing in this License Agreement shall be deemed to
177+
create any relationship of agency, partnership, or joint venture
178+
between BeOpen and Licensee. This License Agreement does not grant
179+
permission to use BeOpen trademarks or trade names in a trademark
180+
sense to endorse or promote products or services of Licensee, or any
181+
third party. As an exception, the "BeOpen Python" logos available at
182+
http://www.pythonlabs.com/logos.html may be used according to the
183+
permissions granted on that web page.
184+
185+
7. By copying, installing or otherwise using the software, Licensee
186+
agrees to be bound by the terms and conditions of this License
187+
Agreement.
188+
189+
190+
CNRI LICENSE AGREEMENT FOR PYTHON 1.6.1
191+
---------------------------------------
192+
193+
1. This LICENSE AGREEMENT is between the Corporation for National
194+
Research Initiatives, having an office at 1895 Preston White Drive,
195+
Reston, VA 20191 ("CNRI"), and the Individual or Organization
196+
("Licensee") accessing and otherwise using Python 1.6.1 software in
197+
source or binary form and its associated documentation.
198+
199+
2. Subject to the terms and conditions of this License Agreement, CNRI
200+
hereby grants Licensee a nonexclusive, royalty-free, world-wide
201+
license to reproduce, analyze, test, perform and/or display publicly,
202+
prepare derivative works, distribute, and otherwise use Python 1.6.1
203+
alone or in any derivative version, provided, however, that CNRI's
204+
License Agreement and CNRI's notice of copyright, i.e., "Copyright (c)
205+
1995-2001 Corporation for National Research Initiatives; All Rights
206+
Reserved" are retained in Python 1.6.1 alone or in any derivative
207+
version prepared by Licensee. Alternately, in lieu of CNRI's License
208+
Agreement, Licensee may substitute the following text (omitting the
209+
quotes): "Python 1.6.1 is made available subject to the terms and
210+
conditions in CNRI's License Agreement. This Agreement together with
211+
Python 1.6.1 may be located on the Internet using the following
212+
unique, persistent identifier (known as a handle): 1895.22/1013. This
213+
Agreement may also be obtained from a proxy server on the Internet
214+
using the following URL: http://hdl.handle.net/1895.22/1013".
215+
216+
3. In the event Licensee prepares a derivative work that is based on
217+
or incorporates Python 1.6.1 or any part thereof, and wants to make
218+
the derivative work available to others as provided herein, then
219+
Licensee hereby agrees to include in any such work a brief summary of
220+
the changes made to Python 1.6.1.
221+
222+
4. CNRI is making Python 1.6.1 available to Licensee on an "AS IS"
223+
basis. CNRI MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR
224+
IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, CNRI MAKES NO AND
225+
DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS
226+
FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON 1.6.1 WILL NOT
227+
INFRINGE ANY THIRD PARTY RIGHTS.
228+
229+
5. CNRI SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON
230+
1.6.1 FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS
231+
A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON 1.6.1,
232+
OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF.
233+
234+
6. This License Agreement will automatically terminate upon a material
235+
breach of its terms and conditions.
236+
237+
7. This License Agreement shall be governed by the federal
238+
intellectual property law of the United States, including without
239+
limitation the federal copyright law, and, to the extent such
240+
U.S. federal law does not apply, by the law of the Commonwealth of
241+
Virginia, excluding Virginia's conflict of law provisions.
242+
Notwithstanding the foregoing, with regard to derivative works based
243+
on Python 1.6.1 that incorporate non-separable material that was
244+
previously distributed under the GNU General Public License (GPL), the
245+
law of the Commonwealth of Virginia shall govern this License
246+
Agreement only as to issues arising under or with respect to
247+
Paragraphs 4, 5, and 7 of this License Agreement. Nothing in this
248+
License Agreement shall be deemed to create any relationship of
249+
agency, partnership, or joint venture between CNRI and Licensee. This
250+
License Agreement does not grant permission to use CNRI trademarks or
251+
trade name in a trademark sense to endorse or promote products or
252+
services of Licensee, or any third party.
253+
254+
8. By clicking on the "ACCEPT" button where indicated, or by copying,
255+
installing or otherwise using Python 1.6.1, Licensee agrees to be
256+
bound by the terms and conditions of this License Agreement.
257+
258+
ACCEPT
259+
260+
261+
CWI LICENSE AGREEMENT FOR PYTHON 0.9.0 THROUGH 1.2
262+
--------------------------------------------------
263+
264+
Copyright (c) 1991 - 1995, Stichting Mathematisch Centrum Amsterdam,
265+
The Netherlands. All rights reserved.
266+
267+
Permission to use, copy, modify, and distribute this software and its
268+
documentation for any purpose and without fee is hereby granted,
269+
provided that the above copyright notice appear in all copies and that
270+
both that copyright notice and this permission notice appear in
271+
supporting documentation, and that the name of Stichting Mathematisch
272+
Centrum or CWI not be used in advertising or publicity pertaining to
273+
distribution of the software without specific, written prior
274+
permission.
275+
276+
STICHTING MATHEMATISCH CENTRUM DISCLAIMS ALL WARRANTIES WITH REGARD TO
277+
THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND
278+
FITNESS, IN NO EVENT SHALL STICHTING MATHEMATISCH CENTRUM BE LIABLE
279+
FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
280+
WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
281+
ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT
282+
OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

‎LICENSE_Python.txt.meta‎

Lines changed: 8 additions & 0 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

‎Lib.meta‎

Lines changed: 9 additions & 0 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

0 commit comments

Comments
 (0)