From 410825ac8b0f3427f0b163ca2354c289e21ac0ff Mon Sep 17 00:00:00 2001 From: Fred Drake Date: Sat, 27 Sep 2003 07:11:17 +0000 Subject: Move content input files shared among the documents into a new directory (commontex/), leaving only style support files in texinputs/. This makes texinputs/ part of the formatting tools while commontex/ is strictly part of the actual documentation. --- Doc/Makefile | 9 +- Doc/Makefile.deps | 20 +-- Doc/commontex/boilerplate.tex | 11 ++ Doc/commontex/copyright.tex | 14 ++ Doc/commontex/license.tex | 280 ++++++++++++++++++++++++++++++++++++++++ Doc/commontex/reportingbugs.tex | 61 +++++++++ Doc/commontex/typestruct.h | 76 +++++++++++ Doc/texinputs/boilerplate.tex | 11 -- Doc/texinputs/copyright.tex | 14 -- Doc/texinputs/license.tex | 279 --------------------------------------- Doc/texinputs/reportingbugs.tex | 61 --------- Doc/texinputs/typestruct.h | 76 ----------- 12 files changed, 460 insertions(+), 452 deletions(-) create mode 100644 Doc/commontex/boilerplate.tex create mode 100644 Doc/commontex/copyright.tex create mode 100644 Doc/commontex/license.tex create mode 100644 Doc/commontex/reportingbugs.tex create mode 100644 Doc/commontex/typestruct.h delete mode 100644 Doc/texinputs/boilerplate.tex delete mode 100644 Doc/texinputs/copyright.tex delete mode 100644 Doc/texinputs/license.tex delete mode 100644 Doc/texinputs/reportingbugs.tex delete mode 100644 Doc/texinputs/typestruct.h diff --git a/Doc/Makefile b/Doc/Makefile index 34bd632..2ea8180 100644 --- a/Doc/Makefile +++ b/Doc/Makefile @@ -71,6 +71,13 @@ RELEASE=2.4a0 PYTHON= python DVIPS= dvips -N0 -t $(PAPER) +PWD=$(shell pwd) + +# (The trailing colon in the value is needed; TeX places it's default +# set of paths at the location of the empty string in the path list.) +# +TEXINPUTS=$(PWD)/commontex: + # This is ugly! The issue here is that there are two different levels # in the directory tree at which we execute mkhowto, so we can't # define it just once using a relative path (at least not with the @@ -78,7 +85,7 @@ DVIPS= dvips -N0 -t $(PAPER) # $(shell) function here to work around that restriction by # identifying mkhowto using an absolute path. # -MKHOWTO= $(PYTHON) $(shell pwd)/tools/mkhowto +MKHOWTO= TEXINPUTS=$(TEXINPUTS) $(PYTHON) $(PWD)/tools/mkhowto MKDVI= $(MKHOWTO) --paper=$(PAPER) --dvi MKHTML= $(MKHOWTO) --html --about html/stdabout.dat \ diff --git a/Doc/Makefile.deps b/Doc/Makefile.deps index faa2129..b7724da 100644 --- a/Doc/Makefile.deps +++ b/Doc/Makefile.deps @@ -5,9 +5,9 @@ COMMONSTYLES= texinputs/python.sty \ INDEXSTYLES=texinputs/python.ist -COMMONTEX= texinputs/copyright.tex \ - texinputs/license.tex \ - texinputs/boilerplate.tex +COMMONTEX=commontex/copyright.tex \ + commontex/license.tex \ + commontex/boilerplate.tex MANSTYLES= texinputs/fncychap.sty \ texinputs/manual.cls \ @@ -29,8 +29,8 @@ APIFILES= $(MANSTYLES) $(INDEXSTYLES) $(COMMONTEX) \ api/refcounting.tex \ api/utilities.tex \ api/veryhigh.tex \ - texinputs/typestruct.h \ - texinputs/reportingbugs.tex + commontex/typestruct.h \ + commontex/reportingbugs.tex # These files are generated from those listed above, and are used to # generate the typeset versions of the manuals. The list is defined @@ -47,10 +47,10 @@ ANNOAPIFILES= $(MANSTYLES) $(INDEXSTYLES) $(COMMONTEX) api/refcounts.dat \ paper-$(PAPER)/refcounting.tex \ paper-$(PAPER)/utilities.tex \ paper-$(PAPER)/veryhigh.tex \ - texinputs/reportingbugs.tex + commontex/reportingbugs.tex DOCFILES= $(HOWTOSTYLES) \ - texinputs/boilerplate.tex \ + commontex/boilerplate.tex \ texinputs/ltxmarkup.sty \ doc/doc.tex @@ -65,8 +65,8 @@ EXTFILES= ext/ext.tex $(MANSTYLES) $(INDEXSTYLES) $(COMMONTEX) \ ext/noddy3.c \ ext/noddy4.c \ ext/run-func.c \ - texinputs/typestruct.h \ - texinputs/reportingbugs.tex + commontex/typestruct.h \ + commontex/reportingbugs.tex TUTFILES= tut/tut.tex tut/glossary.tex $(MANSTYLES) $(COMMONTEX) @@ -84,7 +84,7 @@ REFFILES= $(MANSTYLES) $(INDEXSTYLES) $(COMMONTEX) \ # LaTeX source files for the Python Library Reference LIBFILES= $(MANSTYLES) $(INDEXSTYLES) $(COMMONTEX) \ - texinputs/reportingbugs.tex \ + commontex/reportingbugs.tex \ lib/lib.tex \ lib/asttable.tex \ lib/compiler.tex \ diff --git a/Doc/commontex/boilerplate.tex b/Doc/commontex/boilerplate.tex new file mode 100644 index 0000000..434feaa --- /dev/null +++ b/Doc/commontex/boilerplate.tex @@ -0,0 +1,11 @@ +\author{Guido van Rossum\\ + Fred L. Drake, Jr., editor} +\authoraddress{ + \strong{PythonLabs}\\ + Email: \email{docs@python.org} +} + +\date{\today} % XXX update before final release! +\release{2.4} % software release, not documentation +\setreleaseinfo{a0} % empty for final release +\setshortversion{2.4} % major.minor only for software diff --git a/Doc/commontex/copyright.tex b/Doc/commontex/copyright.tex new file mode 100644 index 0000000..e7b8280 --- /dev/null +++ b/Doc/commontex/copyright.tex @@ -0,0 +1,14 @@ +Copyright \copyright{} 2001, 2002, 2003 Python Software Foundation. +All rights reserved. + +Copyright \copyright{} 2000 BeOpen.com. +All rights reserved. + +Copyright \copyright{} 1995-2000 Corporation for National Research Initiatives. +All rights reserved. + +Copyright \copyright{} 1991-1995 Stichting Mathematisch Centrum. +All rights reserved. + +See the end of this document for complete license and permissions +information. diff --git a/Doc/commontex/license.tex b/Doc/commontex/license.tex new file mode 100644 index 0000000..263d4f9 --- /dev/null +++ b/Doc/commontex/license.tex @@ -0,0 +1,280 @@ +\section{History of the software} + +Python was created in the early 1990s by Guido van Rossum at Stichting +Mathematisch Centrum (CWI, see \url{http://www.cwi.nl/}) in the Netherlands +as a successor of a language called ABC. Guido remains Python's +principal author, although it includes many contributions from others. + +In 1995, Guido continued his work on Python at the Corporation for +National Research Initiatives (CNRI, see \url{http://www.cnri.reston.va.us/}) +in Reston, Virginia where he released several versions of the +software. + +In May 2000, Guido and the Python core development team moved to +BeOpen.com to form the BeOpen PythonLabs team. In October of the same +year, the PythonLabs team moved to Digital Creations (now Zope +Corporation; see \url{http://www.zope.com/}). In 2001, the Python +Software Foundation (PSF, see \url{http://www.python.org/psf/}) was +formed, a non-profit organization created specifically to own +Python-related Intellectual Property. Zope Corporation is a +sponsoring member of the PSF. + +All Python releases are Open Source (see +\url{http://www.opensource.org/} for the Open Source Definition). +Historically, most, but not all, Python releases have also been +GPL-compatible; the table below summarizes the various releases. + +\begin{tablev}{c|c|c|c|c}{textrm}% + {Release}{Derived from}{Year}{Owner}{GPL compatible?} + \linev{0.9.0 thru 1.2}{n/a}{1991-1995}{CWI}{yes} + \linev{1.3 thru 1.5.2}{1.2}{1995-1999}{CNRI}{yes} + \linev{1.6}{1.5.2}{2000}{CNRI}{no} + \linev{2.0}{1.6}{2000}{BeOpen.com}{no} + \linev{1.6.1}{1.6}{2001}{CNRI}{no} + \linev{2.1}{2.0+1.6.1}{2001}{PSF}{no} + \linev{2.0.1}{2.0+1.6.1}{2001}{PSF}{yes} + \linev{2.1.1}{2.1+2.0.1}{2001}{PSF}{yes} + \linev{2.2}{2.1.1}{2001}{PSF}{yes} + \linev{2.1.2}{2.1.1}{2002}{PSF}{yes} + \linev{2.1.3}{2.1.2}{2002}{PSF}{yes} + \linev{2.2.1}{2.2}{2002}{PSF}{yes} + \linev{2.2.2}{2.2.1}{2002}{PSF}{yes} + \linev{2.2.3}{2.2.2}{2002-2003}{PSF}{yes} + \linev{2.3}{2.2.2}{2002-2003}{PSF}{yes} + \linev{2.3.1}{2.3}{2002-2003}{PSF}{yes} + \linev{2.3.2}{2.3.1}{2003}{PSF}{yes} +\end{tablev} + +\note{GPL-compatible doesn't mean that we're distributing +Python under the GPL. All Python licenses, unlike the GPL, let you +distribute a modified version without making your changes open source. +The GPL-compatible licenses make it possible to combine Python with +other software that is released under the GPL; the others don't.} + +Thanks to the many outside volunteers who have worked under Guido's +direction to make these releases possible. + + +\section{Terms and conditions for accessing or otherwise using Python} + +\centerline{\strong{PSF LICENSE AGREEMENT FOR PYTHON \version}} + +\begin{enumerate} +\item +This LICENSE AGREEMENT is between the Python Software Foundation +(``PSF''), and the Individual or Organization (``Licensee'') accessing +and otherwise using Python \version{} software in source or binary +form and its associated documentation. + +\item +Subject to the terms and conditions of this License Agreement, PSF +hereby grants Licensee a nonexclusive, royalty-free, world-wide +license to reproduce, analyze, test, perform and/or display publicly, +prepare derivative works, distribute, and otherwise use Python +\version{} alone or in any derivative version, provided, however, that +PSF's License Agreement and PSF's notice of copyright, i.e., +``Copyright \copyright{} 2001-2003 Python Software Foundation; All +Rights Reserved'' are retained in Python \version{} alone or in any +derivative version prepared by Licensee. + +\item +In the event Licensee prepares a derivative work that is based on +or incorporates Python \version{} or any part thereof, and wants to +make the derivative work available to others as provided herein, then +Licensee hereby agrees to include in any such work a brief summary of +the changes made to Python \version. + +\item +PSF is making Python \version{} available to Licensee on an ``AS IS'' +basis. PSF MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR +IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, PSF MAKES NO AND +DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS +FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON \version{} WILL +NOT INFRINGE ANY THIRD PARTY RIGHTS. + +\item +PSF SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON +\version{} FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR +LOSS AS A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON +\version, OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE +POSSIBILITY THEREOF. + +\item +This License Agreement will automatically terminate upon a material +breach of its terms and conditions. + +\item +Nothing in this License Agreement shall be deemed to create any +relationship of agency, partnership, or joint venture between PSF and +Licensee. This License Agreement does not grant permission to use PSF +trademarks or trade name in a trademark sense to endorse or promote +products or services of Licensee, or any third party. + +\item +By copying, installing or otherwise using Python \version, Licensee +agrees to be bound by the terms and conditions of this License +Agreement. +\end{enumerate} + + +\centerline{\strong{BEOPEN.COM LICENSE AGREEMENT FOR PYTHON 2.0}} + +\centerline{\strong{BEOPEN PYTHON OPEN SOURCE LICENSE AGREEMENT VERSION 1}} + +\begin{enumerate} +\item +This LICENSE AGREEMENT is between BeOpen.com (``BeOpen''), having an +office at 160 Saratoga Avenue, Santa Clara, CA 95051, and the +Individual or Organization (``Licensee'') accessing and otherwise +using this software in source or binary form and its associated +documentation (``the Software''). + +\item +Subject to the terms and conditions of this BeOpen Python License +Agreement, BeOpen hereby grants Licensee a non-exclusive, +royalty-free, world-wide license to reproduce, analyze, test, perform +and/or display publicly, prepare derivative works, distribute, and +otherwise use the Software alone or in any derivative version, +provided, however, that the BeOpen Python License is retained in the +Software, alone or in any derivative version prepared by Licensee. + +\item +BeOpen is making the Software available to Licensee on an ``AS IS'' +basis. BEOPEN MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR +IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, BEOPEN MAKES NO AND +DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS +FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE WILL NOT +INFRINGE ANY THIRD PARTY RIGHTS. + +\item +BEOPEN SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF THE +SOFTWARE FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS +AS A RESULT OF USING, MODIFYING OR DISTRIBUTING THE SOFTWARE, OR ANY +DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF. + +\item +This License Agreement will automatically terminate upon a material +breach of its terms and conditions. + +\item +This License Agreement shall be governed by and interpreted in all +respects by the law of the State of California, excluding conflict of +law provisions. Nothing in this License Agreement shall be deemed to +create any relationship of agency, partnership, or joint venture +between BeOpen and Licensee. This License Agreement does not grant +permission to use BeOpen trademarks or trade names in a trademark +sense to endorse or promote products or services of Licensee, or any +third party. As an exception, the ``BeOpen Python'' logos available +at http://www.pythonlabs.com/logos.html may be used according to the +permissions granted on that web page. + +\item +By copying, installing or otherwise using the software, Licensee +agrees to be bound by the terms and conditions of this License +Agreement. +\end{enumerate} + + +\centerline{\strong{CNRI LICENSE AGREEMENT FOR PYTHON 1.6.1}} + +\begin{enumerate} +\item +This LICENSE AGREEMENT is between the Corporation for National +Research Initiatives, having an office at 1895 Preston White Drive, +Reston, VA 20191 (``CNRI''), and the Individual or Organization +(``Licensee'') accessing and otherwise using Python 1.6.1 software in +source or binary form and its associated documentation. + +\item +Subject to the terms and conditions of this License Agreement, CNRI +hereby grants Licensee a nonexclusive, royalty-free, world-wide +license to reproduce, analyze, test, perform and/or display publicly, +prepare derivative works, distribute, and otherwise use Python 1.6.1 +alone or in any derivative version, provided, however, that CNRI's +License Agreement and CNRI's notice of copyright, i.e., ``Copyright +\copyright{} 1995-2001 Corporation for National Research Initiatives; +All Rights Reserved'' are retained in Python 1.6.1 alone or in any +derivative version prepared by Licensee. Alternately, in lieu of +CNRI's License Agreement, Licensee may substitute the following text +(omitting the quotes): ``Python 1.6.1 is made available subject to the +terms and conditions in CNRI's License Agreement. This Agreement +together with Python 1.6.1 may be located on the Internet using the +following unique, persistent identifier (known as a handle): +1895.22/1013. This Agreement may also be obtained from a proxy server +on the Internet using the following URL: +\url{http://hdl.handle.net/1895.22/1013}.'' + +\item +In the event Licensee prepares a derivative work that is based on +or incorporates Python 1.6.1 or any part thereof, and wants to make +the derivative work available to others as provided herein, then +Licensee hereby agrees to include in any such work a brief summary of +the changes made to Python 1.6.1. + +\item +CNRI is making Python 1.6.1 available to Licensee on an ``AS IS'' +basis. CNRI MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR +IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, CNRI MAKES NO AND +DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS +FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON 1.6.1 WILL NOT +INFRINGE ANY THIRD PARTY RIGHTS. + +\item +CNRI SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON +1.6.1 FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS +A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON 1.6.1, +OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF. + +\item +This License Agreement will automatically terminate upon a material +breach of its terms and conditions. + +\item +This License Agreement shall be governed by the federal +intellectual property law of the United States, including without +limitation the federal copyright law, and, to the extent such +U.S. federal law does not apply, by the law of the Commonwealth of +Virginia, excluding Virginia's conflict of law provisions. +Notwithstanding the foregoing, with regard to derivative works based +on Python 1.6.1 that incorporate non-separable material that was +previously distributed under the GNU General Public License (GPL), the +law of the Commonwealth of Virginia shall govern this License +Agreement only as to issues arising under or with respect to +Paragraphs 4, 5, and 7 of this License Agreement. Nothing in this +License Agreement shall be deemed to create any relationship of +agency, partnership, or joint venture between CNRI and Licensee. This +License Agreement does not grant permission to use CNRI trademarks or +trade name in a trademark sense to endorse or promote products or +services of Licensee, or any third party. + +\item +By clicking on the ``ACCEPT'' button where indicated, or by copying, +installing or otherwise using Python 1.6.1, Licensee agrees to be +bound by the terms and conditions of this License Agreement. +\end{enumerate} + +\centerline{ACCEPT} + + + +\centerline{\strong{CWI LICENSE AGREEMENT FOR PYTHON 0.9.0 THROUGH 1.2}} + +Copyright \copyright{} 1991 - 1995, Stichting Mathematisch Centrum +Amsterdam, The Netherlands. All rights reserved. + +Permission to use, copy, modify, and distribute this software and its +documentation for any purpose and without fee is hereby granted, +provided that the above copyright notice appear in all copies and that +both that copyright notice and this permission notice appear in +supporting documentation, and that the name of Stichting Mathematisch +Centrum or CWI not be used in advertising or publicity pertaining to +distribution of the software without specific, written prior +permission. + +STICHTING MATHEMATISCH CENTRUM DISCLAIMS ALL WARRANTIES WITH REGARD TO +THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND +FITNESS, IN NO EVENT SHALL STICHTING MATHEMATISCH CENTRUM BE LIABLE +FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT +OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. diff --git a/Doc/commontex/reportingbugs.tex b/Doc/commontex/reportingbugs.tex new file mode 100644 index 0000000..6db43de --- /dev/null +++ b/Doc/commontex/reportingbugs.tex @@ -0,0 +1,61 @@ +\label{reporting-bugs} + +Python is a mature programming language which has established a +reputation for stability. In order to maintain this reputation, the +developers would like to know of any deficiencies you find in Python +or its documentation. + +Before submitting a report, you will be required to log into SourceForge; +this will make it possible for the developers to contact you +for additional information if needed. It is not possible to submit a +bug report anonymously. + +All bug reports should be submitted via the Python Bug Tracker on +SourceForge (\url{http://sourceforge.net/bugs/?group_id=5470}). The +bug tracker offers a Web form which allows pertinent information to be +entered and submitted to the developers. + +The first step in filing a report is to determine whether the problem +has already been reported. The advantage in doing so, aside from +saving the developers time, is that you learn what has been done to +fix it; it may be that the problem has already been fixed for the next +release, or additional information is needed (in which case you are +welcome to provide it if you can!). To do this, search the bug +database using the search box near the bottom of the page. + +If the problem you're reporting is not already in the bug tracker, go +back to the Python Bug Tracker +(\url{http://sourceforge.net/bugs/?group_id=5470}). Select the +``Submit a Bug'' link at the top of the page to open the bug reporting +form. + +The submission form has a number of fields. The only fields that are +required are the ``Summary'' and ``Details'' fields. For the summary, +enter a \emph{very} short description of the problem; less than ten +words is good. In the Details field, describe the problem in detail, +including what you expected to happen and what did happen. Be sure to +include the version of Python you used, whether any extension modules +were involved, and what hardware and software platform you were using +(including version information as appropriate). + +The only other field that you may want to set is the ``Category'' +field, which allows you to place the bug report into a broad category +(such as ``Documentation'' or ``Library''). + +Each bug report will be assigned to a developer who will determine +what needs to be done to correct the problem. You will +receive an update each time action is taken on the bug. + + +\begin{seealso} + \seetitle[http://www-mice.cs.ucl.ac.uk/multimedia/software/documentation/ReportingBugs.html]{How + to Report Bugs Effectively}{Article which goes into some + detail about how to create a useful bug report. This + describes what kind of information is useful and why it is + useful.} + + \seetitle[http://www.mozilla.org/quality/bug-writing-guidelines.html]{Bug + Writing Guidelines}{Information about writing a good bug + report. Some of this is specific to the Mozilla project, but + describes general good practices.} +\end{seealso} diff --git a/Doc/commontex/typestruct.h b/Doc/commontex/typestruct.h new file mode 100644 index 0000000..0afe375 --- /dev/null +++ b/Doc/commontex/typestruct.h @@ -0,0 +1,76 @@ +typedef struct _typeobject { + PyObject_VAR_HEAD + char *tp_name; /* For printing, in format "." */ + int tp_basicsize, tp_itemsize; /* For allocation */ + + /* Methods to implement standard operations */ + + destructor tp_dealloc; + printfunc tp_print; + getattrfunc tp_getattr; + setattrfunc tp_setattr; + cmpfunc tp_compare; + reprfunc tp_repr; + + /* Method suites for standard classes */ + + PyNumberMethods *tp_as_number; + PySequenceMethods *tp_as_sequence; + PyMappingMethods *tp_as_mapping; + + /* More standard operations (here for binary compatibility) */ + + hashfunc tp_hash; + ternaryfunc tp_call; + reprfunc tp_str; + getattrofunc tp_getattro; + setattrofunc tp_setattro; + + /* Functions to access object as input/output buffer */ + PyBufferProcs *tp_as_buffer; + + /* Flags to define presence of optional/expanded features */ + long tp_flags; + + char *tp_doc; /* Documentation string */ + + /* Assigned meaning in release 2.0 */ + /* call function for all accessible objects */ + traverseproc tp_traverse; + + /* delete references to contained objects */ + inquiry tp_clear; + + /* Assigned meaning in release 2.1 */ + /* rich comparisons */ + richcmpfunc tp_richcompare; + + /* weak reference enabler */ + long tp_weaklistoffset; + + /* Added in release 2.2 */ + /* Iterators */ + getiterfunc tp_iter; + iternextfunc tp_iternext; + + /* Attribute descriptor and subclassing stuff */ + struct PyMethodDef *tp_methods; + struct PyMemberDef *tp_members; + struct PyGetSetDef *tp_getset; + struct _typeobject *tp_base; + PyObject *tp_dict; + descrgetfunc tp_descr_get; + descrsetfunc tp_descr_set; + long tp_dictoffset; + initproc tp_init; + allocfunc tp_alloc; + newfunc tp_new; + freefunc tp_free; /* Low-level free-memory routine */ + inquiry tp_is_gc; /* For PyObject_IS_GC */ + PyObject *tp_bases; + PyObject *tp_mro; /* method resolution order */ + PyObject *tp_cache; + PyObject *tp_subclasses; + PyObject *tp_weaklist; + +} PyTypeObject; diff --git a/Doc/texinputs/boilerplate.tex b/Doc/texinputs/boilerplate.tex deleted file mode 100644 index 434feaa..0000000 --- a/Doc/texinputs/boilerplate.tex +++ /dev/null @@ -1,11 +0,0 @@ -\author{Guido van Rossum\\ - Fred L. Drake, Jr., editor} -\authoraddress{ - \strong{PythonLabs}\\ - Email: \email{docs@python.org} -} - -\date{\today} % XXX update before final release! -\release{2.4} % software release, not documentation -\setreleaseinfo{a0} % empty for final release -\setshortversion{2.4} % major.minor only for software diff --git a/Doc/texinputs/copyright.tex b/Doc/texinputs/copyright.tex deleted file mode 100644 index e7b8280..0000000 --- a/Doc/texinputs/copyright.tex +++ /dev/null @@ -1,14 +0,0 @@ -Copyright \copyright{} 2001, 2002, 2003 Python Software Foundation. -All rights reserved. - -Copyright \copyright{} 2000 BeOpen.com. -All rights reserved. - -Copyright \copyright{} 1995-2000 Corporation for National Research Initiatives. -All rights reserved. - -Copyright \copyright{} 1991-1995 Stichting Mathematisch Centrum. -All rights reserved. - -See the end of this document for complete license and permissions -information. diff --git a/Doc/texinputs/license.tex b/Doc/texinputs/license.tex deleted file mode 100644 index 5e325a9..0000000 --- a/Doc/texinputs/license.tex +++ /dev/null @@ -1,279 +0,0 @@ -\section{History of the software} - -Python was created in the early 1990s by Guido van Rossum at Stichting -Mathematisch Centrum (CWI, see \url{http://www.cwi.nl/}) in the Netherlands -as a successor of a language called ABC. Guido remains Python's -principal author, although it includes many contributions from others. - -In 1995, Guido continued his work on Python at the Corporation for -National Research Initiatives (CNRI, see \url{http://www.cnri.reston.va.us/}) -in Reston, Virginia where he released several versions of the -software. - -In May 2000, Guido and the Python core development team moved to -BeOpen.com to form the BeOpen PythonLabs team. In October of the same -year, the PythonLabs team moved to Digital Creations (now Zope -Corporation; see \url{http://www.zope.com/}). In 2001, the Python -Software Foundation (PSF, see \url{http://www.python.org/psf/}) was -formed, a non-profit organization created specifically to own -Python-related Intellectual Property. Zope Corporation is a -sponsoring member of the PSF. - -All Python releases are Open Source (see -\url{http://www.opensource.org/} for the Open Source Definition). -Historically, most, but not all, Python releases have also been -GPL-compatible; the table below summarizes the various releases. - -\begin{tablev}{c|c|c|c|c}{textrm}% - {Release}{Derived from}{Year}{Owner}{GPL compatible?} - \linev{0.9.0 thru 1.2}{n/a}{1991-1995}{CWI}{yes} - \linev{1.3 thru 1.5.2}{1.2}{1995-1999}{CNRI}{yes} - \linev{1.6}{1.5.2}{2000}{CNRI}{no} - \linev{2.0}{1.6}{2000}{BeOpen.com}{no} - \linev{1.6.1}{1.6}{2001}{CNRI}{no} - \linev{2.1}{2.0+1.6.1}{2001}{PSF}{no} - \linev{2.0.1}{2.0+1.6.1}{2001}{PSF}{yes} - \linev{2.1.1}{2.1+2.0.1}{2001}{PSF}{yes} - \linev{2.2}{2.1.1}{2001}{PSF}{yes} - \linev{2.1.2}{2.1.1}{2002}{PSF}{yes} - \linev{2.1.3}{2.1.2}{2002}{PSF}{yes} - \linev{2.2.1}{2.2}{2002}{PSF}{yes} - \linev{2.2.2}{2.2.1}{2002}{PSF}{yes} - \linev{2.2.3}{2.2.2}{2002-2003}{PSF}{yes} - \linev{2.3}{2.2.2}{2002-2003}{PSF}{yes} - \linev{2.3.1}{2.3}{2002-2003}{PSF}{yes} -\end{tablev} - -\note{GPL-compatible doesn't mean that we're distributing -Python under the GPL. All Python licenses, unlike the GPL, let you -distribute a modified version without making your changes open source. -The GPL-compatible licenses make it possible to combine Python with -other software that is released under the GPL; the others don't.} - -Thanks to the many outside volunteers who have worked under Guido's -direction to make these releases possible. - - -\section{Terms and conditions for accessing or otherwise using Python} - -\centerline{\strong{PSF LICENSE AGREEMENT FOR PYTHON \version}} - -\begin{enumerate} -\item -This LICENSE AGREEMENT is between the Python Software Foundation -(``PSF''), and the Individual or Organization (``Licensee'') accessing -and otherwise using Python \version{} software in source or binary -form and its associated documentation. - -\item -Subject to the terms and conditions of this License Agreement, PSF -hereby grants Licensee a nonexclusive, royalty-free, world-wide -license to reproduce, analyze, test, perform and/or display publicly, -prepare derivative works, distribute, and otherwise use Python -\version{} alone or in any derivative version, provided, however, that -PSF's License Agreement and PSF's notice of copyright, i.e., -``Copyright \copyright{} 2001-2003 Python Software Foundation; All -Rights Reserved'' are retained in Python \version{} alone or in any -derivative version prepared by Licensee. - -\item -In the event Licensee prepares a derivative work that is based on -or incorporates Python \version{} or any part thereof, and wants to -make the derivative work available to others as provided herein, then -Licensee hereby agrees to include in any such work a brief summary of -the changes made to Python \version. - -\item -PSF is making Python \version{} available to Licensee on an ``AS IS'' -basis. PSF MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR -IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, PSF MAKES NO AND -DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS -FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON \version{} WILL -NOT INFRINGE ANY THIRD PARTY RIGHTS. - -\item -PSF SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON -\version{} FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR -LOSS AS A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON -\version, OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE -POSSIBILITY THEREOF. - -\item -This License Agreement will automatically terminate upon a material -breach of its terms and conditions. - -\item -Nothing in this License Agreement shall be deemed to create any -relationship of agency, partnership, or joint venture between PSF and -Licensee. This License Agreement does not grant permission to use PSF -trademarks or trade name in a trademark sense to endorse or promote -products or services of Licensee, or any third party. - -\item -By copying, installing or otherwise using Python \version, Licensee -agrees to be bound by the terms and conditions of this License -Agreement. -\end{enumerate} - - -\centerline{\strong{BEOPEN.COM LICENSE AGREEMENT FOR PYTHON 2.0}} - -\centerline{\strong{BEOPEN PYTHON OPEN SOURCE LICENSE AGREEMENT VERSION 1}} - -\begin{enumerate} -\item -This LICENSE AGREEMENT is between BeOpen.com (``BeOpen''), having an -office at 160 Saratoga Avenue, Santa Clara, CA 95051, and the -Individual or Organization (``Licensee'') accessing and otherwise -using this software in source or binary form and its associated -documentation (``the Software''). - -\item -Subject to the terms and conditions of this BeOpen Python License -Agreement, BeOpen hereby grants Licensee a non-exclusive, -royalty-free, world-wide license to reproduce, analyze, test, perform -and/or display publicly, prepare derivative works, distribute, and -otherwise use the Software alone or in any derivative version, -provided, however, that the BeOpen Python License is retained in the -Software, alone or in any derivative version prepared by Licensee. - -\item -BeOpen is making the Software available to Licensee on an ``AS IS'' -basis. BEOPEN MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR -IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, BEOPEN MAKES NO AND -DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS -FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE WILL NOT -INFRINGE ANY THIRD PARTY RIGHTS. - -\item -BEOPEN SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF THE -SOFTWARE FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS -AS A RESULT OF USING, MODIFYING OR DISTRIBUTING THE SOFTWARE, OR ANY -DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF. - -\item -This License Agreement will automatically terminate upon a material -breach of its terms and conditions. - -\item -This License Agreement shall be governed by and interpreted in all -respects by the law of the State of California, excluding conflict of -law provisions. Nothing in this License Agreement shall be deemed to -create any relationship of agency, partnership, or joint venture -between BeOpen and Licensee. This License Agreement does not grant -permission to use BeOpen trademarks or trade names in a trademark -sense to endorse or promote products or services of Licensee, or any -third party. As an exception, the ``BeOpen Python'' logos available -at http://www.pythonlabs.com/logos.html may be used according to the -permissions granted on that web page. - -\item -By copying, installing or otherwise using the software, Licensee -agrees to be bound by the terms and conditions of this License -Agreement. -\end{enumerate} - - -\centerline{\strong{CNRI LICENSE AGREEMENT FOR PYTHON 1.6.1}} - -\begin{enumerate} -\item -This LICENSE AGREEMENT is between the Corporation for National -Research Initiatives, having an office at 1895 Preston White Drive, -Reston, VA 20191 (``CNRI''), and the Individual or Organization -(``Licensee'') accessing and otherwise using Python 1.6.1 software in -source or binary form and its associated documentation. - -\item -Subject to the terms and conditions of this License Agreement, CNRI -hereby grants Licensee a nonexclusive, royalty-free, world-wide -license to reproduce, analyze, test, perform and/or display publicly, -prepare derivative works, distribute, and otherwise use Python 1.6.1 -alone or in any derivative version, provided, however, that CNRI's -License Agreement and CNRI's notice of copyright, i.e., ``Copyright -\copyright{} 1995-2001 Corporation for National Research Initiatives; -All Rights Reserved'' are retained in Python 1.6.1 alone or in any -derivative version prepared by Licensee. Alternately, in lieu of -CNRI's License Agreement, Licensee may substitute the following text -(omitting the quotes): ``Python 1.6.1 is made available subject to the -terms and conditions in CNRI's License Agreement. This Agreement -together with Python 1.6.1 may be located on the Internet using the -following unique, persistent identifier (known as a handle): -1895.22/1013. This Agreement may also be obtained from a proxy server -on the Internet using the following URL: -\url{http://hdl.handle.net/1895.22/1013}.'' - -\item -In the event Licensee prepares a derivative work that is based on -or incorporates Python 1.6.1 or any part thereof, and wants to make -the derivative work available to others as provided herein, then -Licensee hereby agrees to include in any such work a brief summary of -the changes made to Python 1.6.1. - -\item -CNRI is making Python 1.6.1 available to Licensee on an ``AS IS'' -basis. CNRI MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR -IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, CNRI MAKES NO AND -DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS -FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON 1.6.1 WILL NOT -INFRINGE ANY THIRD PARTY RIGHTS. - -\item -CNRI SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON -1.6.1 FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS -A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON 1.6.1, -OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF. - -\item -This License Agreement will automatically terminate upon a material -breach of its terms and conditions. - -\item -This License Agreement shall be governed by the federal -intellectual property law of the United States, including without -limitation the federal copyright law, and, to the extent such -U.S. federal law does not apply, by the law of the Commonwealth of -Virginia, excluding Virginia's conflict of law provisions. -Notwithstanding the foregoing, with regard to derivative works based -on Python 1.6.1 that incorporate non-separable material that was -previously distributed under the GNU General Public License (GPL), the -law of the Commonwealth of Virginia shall govern this License -Agreement only as to issues arising under or with respect to -Paragraphs 4, 5, and 7 of this License Agreement. Nothing in this -License Agreement shall be deemed to create any relationship of -agency, partnership, or joint venture between CNRI and Licensee. This -License Agreement does not grant permission to use CNRI trademarks or -trade name in a trademark sense to endorse or promote products or -services of Licensee, or any third party. - -\item -By clicking on the ``ACCEPT'' button where indicated, or by copying, -installing or otherwise using Python 1.6.1, Licensee agrees to be -bound by the terms and conditions of this License Agreement. -\end{enumerate} - -\centerline{ACCEPT} - - - -\centerline{\strong{CWI LICENSE AGREEMENT FOR PYTHON 0.9.0 THROUGH 1.2}} - -Copyright \copyright{} 1991 - 1995, Stichting Mathematisch Centrum -Amsterdam, The Netherlands. All rights reserved. - -Permission to use, copy, modify, and distribute this software and its -documentation for any purpose and without fee is hereby granted, -provided that the above copyright notice appear in all copies and that -both that copyright notice and this permission notice appear in -supporting documentation, and that the name of Stichting Mathematisch -Centrum or CWI not be used in advertising or publicity pertaining to -distribution of the software without specific, written prior -permission. - -STICHTING MATHEMATISCH CENTRUM DISCLAIMS ALL WARRANTIES WITH REGARD TO -THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND -FITNESS, IN NO EVENT SHALL STICHTING MATHEMATISCH CENTRUM BE LIABLE -FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES -WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN -ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT -OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. diff --git a/Doc/texinputs/reportingbugs.tex b/Doc/texinputs/reportingbugs.tex deleted file mode 100644 index 6db43de..0000000 --- a/Doc/texinputs/reportingbugs.tex +++ /dev/null @@ -1,61 +0,0 @@ -\label{reporting-bugs} - -Python is a mature programming language which has established a -reputation for stability. In order to maintain this reputation, the -developers would like to know of any deficiencies you find in Python -or its documentation. - -Before submitting a report, you will be required to log into SourceForge; -this will make it possible for the developers to contact you -for additional information if needed. It is not possible to submit a -bug report anonymously. - -All bug reports should be submitted via the Python Bug Tracker on -SourceForge (\url{http://sourceforge.net/bugs/?group_id=5470}). The -bug tracker offers a Web form which allows pertinent information to be -entered and submitted to the developers. - -The first step in filing a report is to determine whether the problem -has already been reported. The advantage in doing so, aside from -saving the developers time, is that you learn what has been done to -fix it; it may be that the problem has already been fixed for the next -release, or additional information is needed (in which case you are -welcome to provide it if you can!). To do this, search the bug -database using the search box near the bottom of the page. - -If the problem you're reporting is not already in the bug tracker, go -back to the Python Bug Tracker -(\url{http://sourceforge.net/bugs/?group_id=5470}). Select the -``Submit a Bug'' link at the top of the page to open the bug reporting -form. - -The submission form has a number of fields. The only fields that are -required are the ``Summary'' and ``Details'' fields. For the summary, -enter a \emph{very} short description of the problem; less than ten -words is good. In the Details field, describe the problem in detail, -including what you expected to happen and what did happen. Be sure to -include the version of Python you used, whether any extension modules -were involved, and what hardware and software platform you were using -(including version information as appropriate). - -The only other field that you may want to set is the ``Category'' -field, which allows you to place the bug report into a broad category -(such as ``Documentation'' or ``Library''). - -Each bug report will be assigned to a developer who will determine -what needs to be done to correct the problem. You will -receive an update each time action is taken on the bug. - - -\begin{seealso} - \seetitle[http://www-mice.cs.ucl.ac.uk/multimedia/software/documentation/ReportingBugs.html]{How - to Report Bugs Effectively}{Article which goes into some - detail about how to create a useful bug report. This - describes what kind of information is useful and why it is - useful.} - - \seetitle[http://www.mozilla.org/quality/bug-writing-guidelines.html]{Bug - Writing Guidelines}{Information about writing a good bug - report. Some of this is specific to the Mozilla project, but - describes general good practices.} -\end{seealso} diff --git a/Doc/texinputs/typestruct.h b/Doc/texinputs/typestruct.h deleted file mode 100644 index 0afe375..0000000 --- a/Doc/texinputs/typestruct.h +++ /dev/null @@ -1,76 +0,0 @@ -typedef struct _typeobject { - PyObject_VAR_HEAD - char *tp_name; /* For printing, in format "." */ - int tp_basicsize, tp_itemsize; /* For allocation */ - - /* Methods to implement standard operations */ - - destructor tp_dealloc; - printfunc tp_print; - getattrfunc tp_getattr; - setattrfunc tp_setattr; - cmpfunc tp_compare; - reprfunc tp_repr; - - /* Method suites for standard classes */ - - PyNumberMethods *tp_as_number; - PySequenceMethods *tp_as_sequence; - PyMappingMethods *tp_as_mapping; - - /* More standard operations (here for binary compatibility) */ - - hashfunc tp_hash; - ternaryfunc tp_call; - reprfunc tp_str; - getattrofunc tp_getattro; - setattrofunc tp_setattro; - - /* Functions to access object as input/output buffer */ - PyBufferProcs *tp_as_buffer; - - /* Flags to define presence of optional/expanded features */ - long tp_flags; - - char *tp_doc; /* Documentation string */ - - /* Assigned meaning in release 2.0 */ - /* call function for all accessible objects */ - traverseproc tp_traverse; - - /* delete references to contained objects */ - inquiry tp_clear; - - /* Assigned meaning in release 2.1 */ - /* rich comparisons */ - richcmpfunc tp_richcompare; - - /* weak reference enabler */ - long tp_weaklistoffset; - - /* Added in release 2.2 */ - /* Iterators */ - getiterfunc tp_iter; - iternextfunc tp_iternext; - - /* Attribute descriptor and subclassing stuff */ - struct PyMethodDef *tp_methods; - struct PyMemberDef *tp_members; - struct PyGetSetDef *tp_getset; - struct _typeobject *tp_base; - PyObject *tp_dict; - descrgetfunc tp_descr_get; - descrsetfunc tp_descr_set; - long tp_dictoffset; - initproc tp_init; - allocfunc tp_alloc; - newfunc tp_new; - freefunc tp_free; /* Low-level free-memory routine */ - inquiry tp_is_gc; /* For PyObject_IS_GC */ - PyObject *tp_bases; - PyObject *tp_mro; /* method resolution order */ - PyObject *tp_cache; - PyObject *tp_subclasses; - PyObject *tp_weaklist; - -} PyTypeObject; -- cgit v0.12