Mailman 3 September 2003 - Python-checkins

python/dist/src/Doc README,1.51,1.52
by theller＠users.sourceforge.net Sept. 27, 2003

Sept. 27, 2003

Update of /cvsroot/python/python/dist/src/Doc In directory sc8-pr-cvs1:/tmp/cvs-serv5341 Modified Files: README Log Message: Typo: documnetation -> documentation Will backport to 2.3 Index: README =================================================================== RCS file: /cvsroot/python/python/dist/src/Doc/README,v retrieving revision 1.51 retrieving revision 1.52 diff -C2 -d -r1.51 -r1.52 *** README 27 Sep 2003 07:16:32 -0000 1.51 --- README 27 Sep 2003 19:32:04 -0000 1.52 *************** *** 33,37 **** There's a Makefile to call LaTeX and the other utilities in the right order and the right number of times. By default, it will build the ! HTML version of the documnetation, but DVI, PDF, and PostScript can also be made. To view the generated HTML, point your favorite browser at the top-level index (html/index.html) after running "make". --- 33,37 ---- There's a Makefile to call LaTeX and the other utilities in the right order and the right number of times. By default, it will build the ! HTML version of the documentation, but DVI, PDF, and PostScript can also be made. To view the generated HTML, point your favorite browser at the top-level index (html/index.html) after running "make".

1 0

python/dist/src/Doc/tut glossary.tex,1.2,1.3
by fdrake＠users.sourceforge.net Sept. 27, 2003

Sept. 27, 2003

Update of /cvsroot/python/python/dist/src/Doc/tut In directory sc8-pr-cvs1:/tmp/cvs-serv31014 Modified Files: glossary.tex Log Message: Lots of markup corrections. Some are minor, but others are not: the contents of an \item should not be enclosed in a group! Index: glossary.tex =================================================================== RCS file: /cvsroot/python/python/dist/src/Doc/tut/glossary.tex,v retrieving revision 1.2 retrieving revision 1.3 diff -C2 -d -r1.2 -r1.3 *** glossary.tex 27 Sep 2003 05:42:14 -0000 1.2 --- glossary.tex 27 Sep 2003 18:59:43 -0000 1.3 *************** *** 7,79 **** \index{...} ! \item[...]{The typical Python prompt of the interactive shell when entering ! code for an indented code block.} \index{>>>} ! \item[>>>]{The typical Python prompt of the interactive shell. Often seen ! for code examples that can be tried right away in the interpreter.} \index{__slots__} ! \item[__slots__]{A declaration inside a \emph{new-style class} that saves ! memory by pre-declaring space for instance attributes and eliminating ! instance dictionaries. Though popular, the technique is somewhat tricky to ! get right and is best reserved for rare cases where there are large numbers ! of instances in a memory critical application.} \index{BDFL} ! \item[BDFL]{Benevolent Dictator For Life, a.k.a. \ulink{Guido van ! Rossum}{http://www.python.org/~guido/}, Python's creator.} \index{byte code} ! \item[byte code]{The internal representation of a Python program in the ! interpreter. The byte code is also cached in the \code{.pyc} and ! {}\code{.pyo} files so that executing the same file is faster the second ! time (compilation from source to byte code can be saved). This ! "intermediate language" is said to run on a "virtual machine" that calls the ! subroutines corresponding to each bytecode.} \index{classic class} ! \item[classic class]{Any class which does not inherit from \class{object}. ! See new-style class.} \index{coercion} ! \item[coercion]{Converting data from one type to another. For example, ! {}\code{int(3.15)} coerces the floating point number to the integer, \code{3}. ! Most mathematical operations have rules for coercing their arguments to a common ! type. For instance, adding \code{3 + 4.5}, causes the integer \code{3} to be ! coerced to be a float \code{3.0} before adding to \code{4.5} resulting in the ! float \code{7.5}.} \index{descriptor} ! \item[descriptor]{Any object that defines the methods \method{__get__()}, ! \method{__set__()}, or \method{__delete__()}. When a class attribute is a ! descriptor, its special binding behavior is triggered upon attribute lookup. ! Normally, writing {}\var{a.b} looks up the object \var{b} in the class ! dictionary for \var{a}, but if \var{b} is a descriptor, the defined method ! gets called. Understanding descriptors is a key to a deep understanding of ! Python because they are the basis for many features including functions, ! methods, properties, class methods, static methods, and reference to super ! classes.} \index{dictionary} ! \item[dictionary]{An associative array, where arbitrary keys are mapped to ! values. The use of \class{dict} much resembles that for \class{list}, but ! the keys can be any object with a \function{__hash__} function, not just ! integers starting from zero. Called a hash in Perl.} \index{EAFP} ! \item[EAFP]{Easier to ask for forgiveness than permission. This common ! Python coding style assumes the existence of valid keys or attributes and ! catches exceptions if the assumption proves false. This clean and fast ! style is characterized by the presence of many \keyword{try} and ! {}\keyword{except} statements. The technique contrasts with the \emph{LBYL} ! style that is common in many other languages such as C.} \index{__future__} ! \item[__future__]{A pseudo module which programmers can use to enable ! new language features which are not compatible with the current interpreter. ! For example, the expression \code{11 / 4} currently evaluates to \code{2}. ! If the module in which it is executed had enabled emph{true division} by ! executing:} \begin{verbatim} --- 7,92 ---- \index{...} ! \item[\code{.\code{.}.}] ! The typical Python prompt of the interactive shell when entering code ! for an indented code block. \index{>>>} ! \item[\code{>\code{>}>}] ! The typical Python prompt of the interactive shell. Often seen for ! code examples that can be tried right away in the interpreter. \index{__slots__} ! \item[__slots__] ! A declaration inside a \emph{new-style class} that saves memory by ! pre-declaring space for instance attributes and eliminating instance ! dictionaries. Though popular, the technique is somewhat tricky to get ! right and is best reserved for rare cases where there are large ! numbers of instances in a memory critical application. \index{BDFL} ! \item[BDFL] ! Benevolent Dictator For Life, a.k.a. \ulink{Guido van ! Rossum}{http://www.python.org/~guido/}, Python's creator. \index{byte code} ! \item[byte code] ! The internal representation of a Python program in the interpreter. ! The byte code is also cached in the \code{.pyc} and \code{.pyo} ! files so that executing the same file is faster the second time ! (compilation from source to byte code can be saved). This ! \emph{intermediate language} is said to run on a \emph{virtual ! machine} that calls the subroutines corresponding to each bytecode. \index{classic class} ! \item[classic class] ! Any class which does not inherit from \class{object}. See ! \emph{new-style class}. \index{coercion} ! \item[coercion] ! Converting data from one type to another. For example, ! {}\code{int(3.15)} coerces the floating point number to the integer, ! {}\code{3}. Most mathematical operations have rules for coercing ! their arguments to a common type. For instance, adding \code{3 + ! 4.5}, causes the integer \code{3} to be coerced to be a float ! {}\code{3.0} before adding to \code{4.5} resulting in the float ! {}\code{7.5}. \index{descriptor} ! \item[descriptor] ! Any \emph{new-style} object that defines the methods ! {}\method{__get__()}, \method{__set__()}, or \method{__delete__()}. ! When a class attribute is a descriptor, its special binding behavior ! is triggered upon attribute lookup. Normally, writing \var{a.b} looks ! up the object \var{b} in the class dictionary for \var{a}, but if ! {}\var{b} is a descriptor, the defined method gets called. ! Understanding descriptors is a key to a deep understanding of Python ! because they are the basis for many features including functions, ! methods, properties, class methods, static methods, and reference to ! super classes. \index{dictionary} ! \item[dictionary] ! An associative array, where arbitrary keys are mapped to values. The ! use of \class{dict} much resembles that for \class{list}, but the keys ! can be any object with a \method{__hash__()} function, not just ! integers starting from zero. Called a hash in Perl. \index{EAFP} ! \item[EAFP] ! Easier to ask for forgiveness than permission. This common Python ! coding style assumes the existence of valid keys or attributes and ! catches exceptions if the assumption proves false. This clean and ! fast style is characterized by the presence of many \keyword{try} and ! {}\keyword{except} statements. The technique contrasts with the ! {}\emph{LBYL} style that is common in many other languages such as C. \index{__future__} ! \item[__future__] ! A pseudo module which programmers can use to enable new language ! features which are not compatible with the current interpreter. For ! example, the expression \code{11 / 4} currently evaluates to \code{2}. ! If the module in which it is executed had enabled emph{true division} ! by executing: \begin{verbatim} *************** *** 81,88 **** \end{verbatim} ! the expression \code{11 / 4} would evaluate to \code{2.75}. By actually ! importing the \module{__future__} module and evaluating its variables, you ! can see when a new feature was first added to the language and when it will ! become the default: \begin{verbatim} --- 94,101 ---- \end{verbatim} ! the expression \code{11 / 4} would evaluate to \code{2.75}. By ! actually importing the \refmodule[future]{__future__} module and ! evaluating its variables, you can see when a new feature was first ! added to the language and when it will become the default: \begin{verbatim} *************** *** 93,268 **** \index{generator} ! \item[generator]{A function that returns an iterator. It looks like a ! normal function except that the \keyword{yield} keyword is used instead of {}\keyword{return}. Generator functions often contain one or more ! {}\keyword{for} or \keyword{while} loops that \keyword{yield} elements back to ! the caller. The function execution is stopped at the \keyword{yield} keyword ! (returning the result) and is resumed there when the next element is ! requested by calling the \function{next()} method of the returned iterator.} \index{GIL} ! \item[GIL]{See \emph{global interpreter lock}.} \index{global interpreter lock} ! \item[global interpreter lock]{the lock used by Python threads to assure ! that only one thread can be run at a time. This simplifies Python by ! assuring that no two processes can access the same memory at the same time. ! Locking the entire interpreter makes it easier for the interpreter to be multi-threaded, at the expense of some parallelism on multi-processor ! machines. Efforts have been made in the past to create a "free-threaded" ! interpreter (one which locks shared data at a much finer granularity), but ! performance suffered in the common single-processor case.} \index{IDLE} ! \item[IDLE]{an Integrated Development Environment for Python. IDLE is a basic editor and interpreter environment that ships with the standard distribution of Python. Good for beginners, it also serves as clear example code for those wanting to implement a moderately ! sophisticated, multi-platform GUI application.} \index{immutable} ! \item[immutable]{A object with fixed value. Immutable objects are numbers, ! strings or tuples (and more). Such an object cannot be altered. A new object has to be created if a different value has to be stored. They play an ! important role in places where a constant hash value is needed. For example ! as a key in a dictionary.} \index{integer division} ! \item[integer division]{Mathematical division discarding any remainder. For ! example, the expression \code{11 / 4} currently evaluates to \code{2} in ! contrast to the \code{2.75} returned by float division. Also called ! \emph{floor division}. When dividing two integers the outcome will always be ! another integer (having the floor function applied to it). However, if one ! of the operands is another numeric type (such as a \class{float}), the result ! will be coerced (see \emph{coercion}) to a common type. For example, a integer ! divided by a float will result in a float value, possibly with a decimal ! fraction. Integer division can be forced by using the \code{//} operator ! instead of the \code{/} operator. ! See also, \emph{__future__}.} \index{interactive} ! \item[interactive]{Python has an interactive interpreter which means that ! you can try out things and directly see its result. Just launch ! {}\code{python} with no arguments (possibly by selecting it from your ! computer's main menu). It is a very powerful way to test out new ideas or ! inspect modules and packages (remember \code{help(x)}).} \index{interpreted} ! \item[interpreted]{Python is an interpreted language, opposed to a compiled ! one. This means that the source files can be run right away without first ! making an executable which is then run. Interpreted languages typically have a shorter development/debug cycle than compiled ones. See also ! {}\emph{interactive}.} \index{iterable} ! \item[iterable]{A container object capable of returning its members one at a ! time. Examples of iterables include all sequence types (such as\class{list}, {}\class{str}, and \class{tuple}) and some non-sequence types like ! {}\class{dict} and \class{file} and objects of any classes you define with ! an \method{__iter__} or \function{__getitem__} method. Iterables can be ! used in a \keyword{for} loop and in many other places where a sequence is ! needed (\function{zip}, \function{map}, ...). When an iterable object is ! passed as an argument to the builtin function \function{iter()}, it returns ! an iterator for the object. This iterator is good for one pass over the set ! of values. When using iterables, it is usually not necessary to call ! {}\function{iter()} or deal with iterator objects yourself - the \code{for} ! statement does that automatically for you, creating a temporary unnamed ! variable to hold the iterator for the duration of the loop. See also ! \emph{iterator}, \emph{sequence} and \emph{generator}.} \index{iterator} ! \item[iterator]{An object representing a stream of data. Repeated calls to ! the iterator's \function{next()} method return successive items in the stream. When no more data is available a \exception{StopIteration} ! exception is raised instead. At this point, the iterator object is exhausted ! and any further calls to its \function{next()} method just raise ! {}\exception{StopIteration} again. Iterators are required to have an ! {}\function{__iter__()} method that returns the iterator object itself so ! every iterator is also iterable and may be used in most places where other ! iterables are accepted. One notable exception is code that attempts ! multiple iteration passes. A container object (such as a \class{list}) ! produces a fresh new iterator each time you pass it to the \function{iter()} ! function or use it in a \function{for} loop. Attempting this with an iterator ! will just return the same exhausted iterator object from the second iteration ! pass, making it appear like an empty container.} \index{list comprehension} ! \item[list comprehension]{A compact way to process all or a subset of elements ! in a sequence and return a list with the results. \code{result = ["0x\%02x" \% x for x in range(256) if x \% 2 == 0]} generates a list of strings containing hex numbers (0x..) that are even and in the range from 0 to 255. The \keyword{if} clause is optional. If omitted, all elements in ! {}\code{range(256)} are processed in that case.} \index{mapping} ! \item[mapping]{A container object (such as \class{dict}) that supports ! arbitrary key lookups using the special method \function{__getitem__()}.} \index{metaclass} ! \item[metaclass]{The class of a class. Class definitions create a class ! name, a class dictionary, and a list of base classes. The metaclass is ! responsible for taking those three arguments and creating the class. Most ! object oriented programming languages provide a default implementation. ! What makes Python special is that it is possible to create custom ! metaclasses. Most users never need this tool, but when the need arises, ! metaclasses can provide powerful, elegant solutions. They have been used ! for logging attribute access, adding thread-safety, tracking object ! creation, implementing singletons, and many other tasks.} \index{LBYL} ! \item[LBYL]{Look before you leap. This coding style explicitly tests for ! pre-conditions before making calls or lookups. This style contrasts with ! the \emph{EAFP} approach and is characterized the presence of many ! {}\keyword{if} statements.} \index{mutable} ! \item[mutable]{Mutable objects can change their value but keep their ! \function{id()}. See also immutable.} \index{namespace} ! \item[namespace]{The place where a variable is stored. Namespaces are ! implemented as dictionary. There is the local, global and builtins ! namespace and the nested namespaces in objects (in methods). Namespaces ! support modularity by preventing naming conflicts. For instance, the ! functions \function{__builtins__.open()} and \function{os.open()} are ! distinguished by their namespaces. Namespaces also aid readability and ! maintainability by making it clear which modules implement a function. For ! instance, writing \function{random.seed()} or \function{itertools.izip()} ! makes it clear that those functions are implemented by the \module{random} ! and \module{itertools} modules respectively.} \index{nested scope} ! \item[nested scope]{The ability to refer to a variable in an enclosing ! definition. For instance, a function defined inside another function can ! refer to variables in the outer function. Note that nested scopes work only for reference and not for assignment which will always write to the ! innermost scope. In contrast, local variables both read and write in the ! innermost scope. Likewise, global variables read and write to the global ! namespace.} \index{new-style class} ! \item[new-style class]{Any class that inherits from \class{object}. This ! includes all built-in types like \class{list} and \class{dict}. Only ! new-style classes can use Python's newer, versatile features like ! {}\var{__slots__}, descriptors, properties, \var{__getattribute__}, class ! methods, and static methods.} \index{Python3000} ! \item[Python3000]{A mythical python release, allowed not to be backward ! compatible, with telepathic interface.} \index{sequence} ! \item[sequence]{An \emph{iterable} which supports efficient element access using ! integer indices via the \function{__getitem__} and \function{__len()__} ! special methods. Some builtin sequence types are \class{list}, \class{str}, ! {}\class{tuple}, and \class{unicode}. Note that \class{dict} also supports ! {}\function{__getitem__} and \function{__len__}, but is considered a mapping ! rather than a sequence because the lookups use arbitrary \emph{immutable} keys ! rather than integers.} \index{Zen of Python} ! \item[Zen of Python]{listing of Python design principles and philosophies ! that are helpful in understanding and using the language. The listing can ! be found by typing \code{import this} at the interactive prompt.} \end{description} --- 106,309 ---- \index{generator} ! \item[generator] ! A function that returns an iterator. It looks like a normal function ! except that the \keyword{yield} keyword is used instead of {}\keyword{return}. Generator functions often contain one or more ! {}\keyword{for} or \keyword{while} loops that \keyword{yield} elements ! back to the caller. The function execution is stopped at the ! {}\keyword{yield} keyword (returning the result) and is resumed there ! when the next element is requested by calling the \method{next()} ! method of the returned iterator. \index{GIL} ! \item[GIL] ! See \emph{global interpreter lock}. \index{global interpreter lock} ! \item[global interpreter lock] ! The lock used by Python threads to assure that only one thread can be ! run at a time. This simplifies Python by assuring that no two ! processes can access the same memory at the same time. Locking the ! entire interpreter makes it easier for the interpreter to be multi-threaded, at the expense of some parallelism on multi-processor ! machines. Efforts have been made in the past to create a ! "free-threaded" interpreter (one which locks shared data at a much ! finer granularity), but performance suffered in the common ! single-processor case. \index{IDLE} ! \item[IDLE] ! An Integrated Development Environment for Python. IDLE is a basic editor and interpreter environment that ships with the standard distribution of Python. Good for beginners, it also serves as clear example code for those wanting to implement a moderately ! sophisticated, multi-platform GUI application. \index{immutable} ! \item[immutable] ! A object with fixed value. Immutable objects are numbers, strings or ! tuples (and more). Such an object cannot be altered. A new object has to be created if a different value has to be stored. They play an ! important role in places where a constant hash value is needed. For ! example as a key in a dictionary. \index{integer division} ! \item[integer division] ! Mathematical division discarding any remainder. For example, the ! expression \code{11 / 4} currently evaluates to \code{2} in contrast ! to the \code{2.75} returned by float division. Also called ! {}\emph{floor division}. When dividing two integers the outcome will ! always be another integer (having the floor function applied to it). ! However, if one of the operands is another numeric type (such as a ! {}\class{float}), the result will be coerced (see \emph{coercion}) to ! a common type. For example, a integer divided by a float will result ! in a float value, possibly with a decimal fraction. Integer division ! can be forced by using the \code{//} operator instead of the \code{/} ! operator. See also \emph{__future__}. \index{interactive} ! \item[interactive] ! Python has an interactive interpreter which means that you can try out ! things and directly see its result. Just launch \code{python} with no ! arguments (possibly by selecting it from your computer's main menu). ! It is a very powerful way to test out new ideas or inspect modules and ! packages (remember \code{help(x)}). \index{interpreted} ! \item[interpreted] ! Python is an interpreted language, opposed to a compiled one. This ! means that the source files can be run right away without first making ! an executable which is then run. Interpreted languages typically have a shorter development/debug cycle than compiled ones. See also ! {}\emph{interactive}. \index{iterable} ! \item[iterable] ! A container object capable of returning its members one at a time. ! Examples of iterables include all sequence types (such as\class{list}, {}\class{str}, and \class{tuple}) and some non-sequence types like ! {}\class{dict} and \class{file} and objects of any classes you define ! with an \method{__iter__()} or \method{__getitem__()} method. Iterables ! can be used in a \keyword{for} loop and in many other places where a ! sequence is needed (\function{zip()}, \function{map()}, ...). When an ! iterable object is passed as an argument to the builtin function ! {}\function{iter()}, it returns an iterator for the object. This ! iterator is good for one pass over the set of values. When using ! iterables, it is usually not necessary to call \function{iter()} or ! deal with iterator objects yourself---the \code{for} statement does ! that automatically for you, creating a temporary unnamed variable to ! hold the iterator for the duration of the loop. See also ! {}\emph{iterator}, \emph{sequence}, and \emph{generator}. \index{iterator} ! \item[iterator] ! An object representing a stream of data. Repeated calls to the ! iterator's \method{next()} method return successive items in the stream. When no more data is available a \exception{StopIteration} ! exception is raised instead. At this point, the iterator object is ! exhausted and any further calls to its \method{next()} method just ! raise \exception{StopIteration} again. Iterators are required to have ! an \method{__iter__()} method that returns the iterator object ! itself so every iterator is also iterable and may be used in most ! places where other iterables are accepted. One notable exception is ! code that attempts multiple iteration passes. A container object ! (such as a \class{list}) produces a fresh new iterator each time you ! pass it to the \function{iter()} function or use it in a ! {}\keyword{for} loop. Attempting this with an iterator will just ! return the same exhausted iterator object from the second iteration ! pass, making it appear like an empty container. \index{list comprehension} ! \item[list comprehension] ! A compact way to process all or a subset of elements in a sequence and ! return a list with the results. \code{result = ["0x\%02x" \% x for x in range(256) if x \% 2 == 0]} generates a list of strings containing hex numbers (0x..) that are even and in the range from 0 to 255. The \keyword{if} clause is optional. If omitted, all elements in ! {}\code{range(256)} are processed in that case. \index{mapping} ! \item[mapping] ! A container object (such as \class{dict}) that supports arbitrary key ! lookups using the special method \method{__getitem__()}. \index{metaclass} ! \item[metaclass] ! The class of a class. Class definitions create a class name, a class ! dictionary, and a list of base classes. The metaclass is responsible ! for taking those three arguments and creating the class. Most object ! oriented programming languages provide a default implementation. What ! makes Python special is that it is possible to create custom ! metaclasses. Most users never need this tool, but when the need ! arises, metaclasses can provide powerful, elegant solutions. They ! have been used for logging attribute access, adding thread-safety, ! tracking object creation, implementing singletons, and many other ! tasks. \index{LBYL} ! \item[LBYL] ! Look before you leap. This coding style explicitly tests for ! pre-conditions before making calls or lookups. This style contrasts ! with the \emph{EAFP} approach and is characterized the presence of ! many \keyword{if} statements. \index{mutable} ! \item[mutable] ! Mutable objects can change their value but keep their \function{id()}. ! See also \emph{immutable}. \index{namespace} ! \item[namespace] ! The place where a variable is stored. Namespaces are implemented as ! dictionary. There is the local, global and builtins namespace and the ! nested namespaces in objects (in methods). Namespaces support ! modularity by preventing naming conflicts. For instance, the ! functions \function{__builtin__.open()} and \function{os.open()} are ! distinguished by their namespaces. Namespaces also aid readability ! and maintainability by making it clear which modules implement a ! function. For instance, writing \function{random.seed()} or ! {}\function{itertools.izip()} makes it clear that those functions are ! implemented by the \refmodule{random} and \refmodule{itertools} ! modules respectively. \index{nested scope} ! \item[nested scope] ! The ability to refer to a variable in an enclosing definition. For ! instance, a function defined inside another function can refer to ! variables in the outer function. Note that nested scopes work only for reference and not for assignment which will always write to the ! innermost scope. In contrast, local variables both read and write in ! the innermost scope. Likewise, global variables read and write to the ! global namespace. \index{new-style class} ! \item[new-style class] ! Any class that inherits from \class{object}. This includes all ! built-in types like \class{list} and \class{dict}. Only new-style ! classes can use Python's newer, versatile features like ! {}\var{__slots__}, descriptors, properties, ! \method{__getattribute__()}, class methods, and static methods. \index{Python3000} ! \item[Python3000] ! A mythical python release, allowed not to be backward compatible, with ! telepathic interface. \index{sequence} ! \item[sequence] ! An \emph{iterable} which supports efficient element access using ! integer indices via the \method{__getitem__()} and ! {}\method{__len__()} special methods. Some built-in sequence types ! are \class{list}, \class{str}, \class{tuple}, and \class{unicode}. ! Note that \class{dict} also supports \method{__getitem__()} and ! {}\method{__len__()}, but is considered a mapping rather than a ! sequence because the lookups use arbitrary \emph{immutable} keys ! rather than integers. \index{Zen of Python} ! \item[Zen of Python] ! Listing of Python design principles and philosophies that are helpful ! in understanding and using the language. The listing can be found by ! typing \code{import this} at the interactive prompt. \end{description}

1 0

python/dist/src/Include patchlevel.h, 2.74.4.2, 2.74.4.3
by fdrake＠users.sourceforge.net Sept. 27, 2003

Sept. 27, 2003

Update of /cvsroot/python/python/dist/src/Include In directory sc8-pr-cvs1:/tmp/cvs-serv23037 Modified Files: Tag: release23-maint patchlevel.h Log Message: bump the release info Index: patchlevel.h =================================================================== RCS file: /cvsroot/python/python/dist/src/Include/patchlevel.h,v retrieving revision 2.74.4.2 retrieving revision 2.74.4.3 diff -C2 -d -r2.74.4.2 -r2.74.4.3 *** patchlevel.h 23 Sep 2003 02:36:16 -0000 2.74.4.2 --- patchlevel.h 27 Sep 2003 18:10:41 -0000 2.74.4.3 *************** *** 22,31 **** #define PY_MAJOR_VERSION 2 #define PY_MINOR_VERSION 3 ! #define PY_MICRO_VERSION 1 ! #define PY_RELEASE_LEVEL PY_RELEASE_LEVEL_FINAL ! #define PY_RELEASE_SERIAL 0 /* Version as a string */ ! #define PY_VERSION "2.3.1" /* Version as a single 4-byte hex number, e.g. 0x010502B2 == 1.5.2b2. --- 22,31 ---- #define PY_MAJOR_VERSION 2 #define PY_MINOR_VERSION 3 ! #define PY_MICRO_VERSION 2 ! #define PY_RELEASE_LEVEL PY_RELEASE_LEVEL_GAMMA ! #define PY_RELEASE_SERIAL 1 /* Version as a string */ ! #define PY_VERSION "2.3.2c1" /* Version as a single 4-byte hex number, e.g. 0x010502B2 == 1.5.2b2.

1 0

python/dist/src/Doc/perl l2hinit.perl,1.79,1.80
by fdrake＠users.sourceforge.net Sept. 27, 2003

Sept. 27, 2003

Update of /cvsroot/python/python/dist/src/Doc/perl In directory sc8-pr-cvs1:/tmp/cvs-serv1526 Modified Files: l2hinit.perl Log Message: Make sure LaTeX2HTML's $TEXINPUTS variable is initialized to include directories identified in the TEXINPUTS environment variable. I think this is the last part of the fix for the version number problems seen in the documentation for the 2.3.1 release. Index: l2hinit.perl =================================================================== RCS file: /cvsroot/python/python/dist/src/Doc/perl/l2hinit.perl,v retrieving revision 1.79 retrieving revision 1.80 diff -C2 -d -r1.79 -r1.80 *** l2hinit.perl 11 Sep 2003 04:14:20 -0000 1.79 --- l2hinit.perl 27 Sep 2003 16:04:23 -0000 1.80 *************** *** 89,92 **** --- 89,96 ---- # processing. # + # XXX This still isn't quite right; we should actually be inserting + # $mytexinputs just before any empty entry in TEXINPUTS is one + # exists instead of just concatenating the pieces like we do here. + # my $file = $_[0]; my($jobname, $dir, $ext) = fileparse($file, '\..*'); *************** *** 94,98 **** $dir =~ s/$dd$//; $TEXINPUTS = "$dir$envkey$mytexinputs"; ! print "\nAdding $dir to \$TEXINPUTS\n"; } --- 98,110 ---- $dir =~ s/$dd$//; $TEXINPUTS = "$dir$envkey$mytexinputs"; ! # Push everything into $TEXINPUTS since LaTeX2HTML doesn't pick ! # this up on it's own; we clear $ENV{'TEXINPUTS'} so the value set ! # for this by the main LaTeX2HTML script doesn't contain duplicate ! # directories. ! if ($ENV{'TEXINPUTS'}) { ! $TEXINPUTS .= "$envkey$ENV{'TEXINPUTS'}"; ! $ENV{'TEXINPUTS'} = undef; ! } ! print "\nSetting \$TEXINPUTS to $TEXINPUTS\n"; }

1 0

python/dist/src/Doc/perl l2hinit.perl, 1.74, 1.74.10.1
by fdrake＠users.sourceforge.net Sept. 27, 2003

Sept. 27, 2003

Update of /cvsroot/python/python/dist/src/Doc/perl In directory sc8-pr-cvs1:/tmp/cvs-serv1340 Modified Files: Tag: release23-maint l2hinit.perl Log Message: Make sure LaTeX2HTML's $TEXINPUTS variable is initialized to include directories identified in the TEXINPUTS environment variable. I think this is the last part of the fix for the version number problems seen in the documentation for the 2.3.1 release. Index: l2hinit.perl =================================================================== RCS file: /cvsroot/python/python/dist/src/Doc/perl/l2hinit.perl,v retrieving revision 1.74 retrieving revision 1.74.10.1 diff -C2 -d -r1.74 -r1.74.10.1 *** l2hinit.perl 27 Jun 2003 18:26:01 -0000 1.74 --- l2hinit.perl 27 Sep 2003 16:03:27 -0000 1.74.10.1 *************** *** 89,92 **** --- 89,96 ---- # processing. # + # XXX This still isn't quite right; we should actually be inserting + # $mytexinputs just before any empty entry in TEXINPUTS is one + # exists instead of just concatenating the pieces like we do here. + # my $file = $_[0]; my($jobname, $dir, $ext) = fileparse($file, '\..*'); *************** *** 94,98 **** $dir =~ s/$dd$//; $TEXINPUTS = "$dir$envkey$mytexinputs"; ! print "\nAdding $dir to \$TEXINPUTS\n"; } --- 98,110 ---- $dir =~ s/$dd$//; $TEXINPUTS = "$dir$envkey$mytexinputs"; ! # Push everything into $TEXINPUTS since LaTeX2HTML doesn't pick ! # this up on it's own; we clear $ENV{'TEXINPUTS'} so the value set ! # for this by the main LaTeX2HTML script doesn't contain duplicate ! # directories. ! if ($ENV{'TEXINPUTS'}) { ! $TEXINPUTS .= "$envkey$ENV{'TEXINPUTS'}"; ! $ENV{'TEXINPUTS'} = undef; ! } ! print "\nSetting \$TEXINPUTS to $TEXINPUTS\n"; }

1 0

python/dist/src aclocal.m4, 1.1, 1.2 configure, 1.425, 1.426
by anthonybaxter＠users.sourceforge.net Sept. 27, 2003

Sept. 27, 2003

Update of /cvsroot/python/python/dist/src In directory sc8-pr-cvs1:/tmp/cvs-serv25123 Modified Files: configure Added Files: aclocal.m4 Log Message: fix for bug #811160 - autoconf vs. hp/ux system header files. also applied to release23-maint. Note that aclocal.m4 can go away when autoconf 2.58 is out. Index: configure =================================================================== RCS file: /cvsroot/python/python/dist/src/configure,v retrieving revision 1.425 retrieving revision 1.426 diff -C2 -d -r1.425 -r1.426 *** configure 25 Sep 2003 14:50:04 -0000 1.425 --- configure 27 Sep 2003 09:12:27 -0000 1.426 *************** *** 1,4 **** #! /bin/sh ! # From configure.in Revision: 1.435 . # Guess values for system-dependent variables and create Makefiles. # Generated by GNU Autoconf 2.57 for python 2.4. --- 1,4 ---- #! /bin/sh ! # From configure.in Revision: 1.436 . # Guess values for system-dependent variables and create Makefiles. # Generated by GNU Autoconf 2.57 for python 2.4. *************** *** 11362,11367 **** which can conflict with char pthread_detach (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. */ ! #ifdef __STDC__ # include <limits.h> #else --- 11362,11369 ---- which can conflict with char pthread_detach (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. Under hpux, ! including <limits.h> includes <sys/time.h> and causes problems ! checking for functions defined therein. */ ! #if defined (__STDC__) && !defined (_HPUX_SOURCE) # include <limits.h> #else *************** *** 12313,12318 **** which can conflict with char $ac_func (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. */ ! #ifdef __STDC__ # include <limits.h> #else --- 12315,12322 ---- which can conflict with char $ac_func (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. Under hpux, ! including <limits.h> includes <sys/time.h> and causes problems ! checking for functions defined therein. */ ! #if defined (__STDC__) && !defined (_HPUX_SOURCE) # include <limits.h> #else *************** *** 12898,12903 **** which can conflict with char $ac_func (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. */ ! #ifdef __STDC__ # include <limits.h> #else --- 12902,12909 ---- which can conflict with char $ac_func (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. Under hpux, ! including <limits.h> includes <sys/time.h> and causes problems ! checking for functions defined therein. */ ! #if defined (__STDC__) && !defined (_HPUX_SOURCE) # include <limits.h> #else *************** *** 13113,13118 **** which can conflict with char $ac_func (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. */ ! #ifdef __STDC__ # include <limits.h> #else --- 13119,13126 ---- which can conflict with char $ac_func (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. Under hpux, ! including <limits.h> includes <sys/time.h> and causes problems ! checking for functions defined therein. */ ! #if defined (__STDC__) && !defined (_HPUX_SOURCE) # include <limits.h> #else *************** *** 14011,14016 **** which can conflict with char $ac_func (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. */ ! #ifdef __STDC__ # include <limits.h> #else --- 14019,14026 ---- which can conflict with char $ac_func (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. Under hpux, ! including <limits.h> includes <sys/time.h> and causes problems ! checking for functions defined therein. */ ! #if defined (__STDC__) && !defined (_HPUX_SOURCE) # include <limits.h> #else *************** *** 14157,14162 **** which can conflict with char $ac_func (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. */ ! #ifdef __STDC__ # include <limits.h> #else --- 14167,14174 ---- which can conflict with char $ac_func (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. Under hpux, ! including <limits.h> includes <sys/time.h> and causes problems ! checking for functions defined therein. */ ! #if defined (__STDC__) && !defined (_HPUX_SOURCE) # include <limits.h> #else *************** *** 14310,14315 **** which can conflict with char $ac_func (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. */ ! #ifdef __STDC__ # include <limits.h> #else --- 14322,14329 ---- which can conflict with char $ac_func (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. Under hpux, ! including <limits.h> includes <sys/time.h> and causes problems ! checking for functions defined therein. */ ! #if defined (__STDC__) && !defined (_HPUX_SOURCE) # include <limits.h> #else *************** *** 14399,14404 **** which can conflict with char $ac_func (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. */ ! #ifdef __STDC__ # include <limits.h> #else --- 14413,14420 ---- which can conflict with char $ac_func (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. Under hpux, ! including <limits.h> includes <sys/time.h> and causes problems ! checking for functions defined therein. */ ! #if defined (__STDC__) && !defined (_HPUX_SOURCE) # include <limits.h> #else *************** *** 14486,14491 **** which can conflict with char $ac_func (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. */ ! #ifdef __STDC__ # include <limits.h> #else --- 14502,14509 ---- which can conflict with char $ac_func (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. Under hpux, ! including <limits.h> includes <sys/time.h> and causes problems ! checking for functions defined therein. */ ! #if defined (__STDC__) && !defined (_HPUX_SOURCE) # include <limits.h> #else *************** *** 14610,14615 **** which can conflict with char $ac_func (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. */ ! #ifdef __STDC__ # include <limits.h> #else --- 14628,14635 ---- which can conflict with char $ac_func (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. Under hpux, ! including <limits.h> includes <sys/time.h> and causes problems ! checking for functions defined therein. */ ! #if defined (__STDC__) && !defined (_HPUX_SOURCE) # include <limits.h> #else *************** *** 14734,14739 **** which can conflict with char $ac_func (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. */ ! #ifdef __STDC__ # include <limits.h> #else --- 14754,14761 ---- which can conflict with char $ac_func (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. Under hpux, ! including <limits.h> includes <sys/time.h> and causes problems ! checking for functions defined therein. */ ! #if defined (__STDC__) && !defined (_HPUX_SOURCE) # include <limits.h> #else *************** *** 15114,15119 **** which can conflict with char $ac_func (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. */ ! #ifdef __STDC__ # include <limits.h> #else --- 15136,15143 ---- which can conflict with char $ac_func (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. Under hpux, ! including <limits.h> includes <sys/time.h> and causes problems ! checking for functions defined therein. */ ! #if defined (__STDC__) && !defined (_HPUX_SOURCE) # include <limits.h> #else *************** *** 16479,16484 **** which can conflict with char gethostbyname_r (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. */ ! #ifdef __STDC__ # include <limits.h> #else --- 16503,16510 ---- which can conflict with char gethostbyname_r (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. Under hpux, ! including <limits.h> includes <sys/time.h> and causes problems ! checking for functions defined therein. */ ! #if defined (__STDC__) && !defined (_HPUX_SOURCE) # include <limits.h> #else *************** *** 16754,16759 **** which can conflict with char $ac_func (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. */ ! #ifdef __STDC__ # include <limits.h> #else --- 16780,16787 ---- which can conflict with char $ac_func (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. Under hpux, ! including <limits.h> includes <sys/time.h> and causes problems ! checking for functions defined therein. */ ! #if defined (__STDC__) && !defined (_HPUX_SOURCE) # include <limits.h> #else *************** *** 16847,16852 **** which can conflict with char __fpu_control (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. */ ! #ifdef __STDC__ # include <limits.h> #else --- 16875,16882 ---- which can conflict with char __fpu_control (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. Under hpux, ! including <limits.h> includes <sys/time.h> and causes problems ! checking for functions defined therein. */ ! #if defined (__STDC__) && !defined (_HPUX_SOURCE) # include <limits.h> #else *************** *** 17079,17084 **** which can conflict with char $ac_func (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. */ ! #ifdef __STDC__ # include <limits.h> #else --- 17109,17116 ---- which can conflict with char $ac_func (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. Under hpux, ! including <limits.h> includes <sys/time.h> and causes problems ! checking for functions defined therein. */ ! #if defined (__STDC__) && !defined (_HPUX_SOURCE) # include <limits.h> #else

1 0

python/dist/src aclocal.m4, NONE, 1.1.2.1 configure, 1.416.4.6, 1.416.4.7
by anthonybaxter＠users.sourceforge.net Sept. 27, 2003

Sept. 27, 2003

Update of /cvsroot/python/python/dist/src In directory sc8-pr-cvs1:/tmp/cvs-serv23108 Modified Files: Tag: release23-maint configure Added Files: Tag: release23-maint aclocal.m4 Log Message: fix for bug #811160 - autoconf vs. hp/ux system header files. --- NEW FILE: aclocal.m4 --- # Code swiped wholesale from the GCC project, see # http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12100 # This file can go away once autoconf 2.58 is out and being used - # it's reported that this is fixed in the autoconf cvs already. # AC_LANG_FUNC_LINK_TRY(C)(FUNCTION) # ---------------------------------- # Don't include <ctype.h> because on OSF/1 3.0 it includes # <sys/types.h> which includes <sys/select.h> which contains a # prototype for select. Similarly for bzero. # # A similar problem afflicts HP/UX, but it also hits <sys/time.h> # # This test used to merely assign f=$1 in main(), but that was # optimized away by HP unbundled cc A.05.36 for ia64 under +O3, # presumably on the basis that there's no need to do that store if the # program is about to exit. Conversely, the AIX linker optimizes an # unused external declaration that initializes f=$1. So this test # program has both an external initialization of f, and a use of f in # main that affects the exit status. # m4_define([AC_LANG_FUNC_LINK_TRY(C)], [AC_LANG_PROGRAM( [/* System header to define __stub macros and hopefully few prototypes, which can conflict with char $1 (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since <limits.h> exists even on freestanding compilers. Under hpux, including <limits.h> includes <sys/time.h> and causes problems checking for functions defined therein. */ #if defined (__STDC__) && !defined (_HPUX_SOURCE) # include <limits.h> #else # include <assert.h> #endif /* Override any gcc2 internal prototype to avoid an error. */ #ifdef __cplusplus extern "C" { #endif /* We use char because int might match the return type of a gcc2 builtin and then its argument prototype would still apply. */ char $1 (); /* The GNU C library defines this for functions which it implements to always fail with ENOSYS. Some functions are actually named something starting with __ and the normal name is an alias. */ #if defined (__stub_$1) || defined (__stub___$1) choke me #else char (*f) () = $1; #endif #ifdef __cplusplus } #endif ], [return f != $1;])]) Index: configure =================================================================== RCS file: /cvsroot/python/python/dist/src/configure,v retrieving revision 1.416.4.6 retrieving revision 1.416.4.7 diff -C2 -d -r1.416.4.6 -r1.416.4.7 *** configure 25 Sep 2003 15:20:55 -0000 1.416.4.6 --- configure 27 Sep 2003 08:58:55 -0000 1.416.4.7 *************** *** 1,4 **** #! /bin/sh ! # From configure.in Revision: 1.427.4.5 . # Guess values for system-dependent variables and create Makefiles. # Generated by GNU Autoconf 2.57 for python 2.3. --- 1,4 ---- #! /bin/sh ! # From configure.in Revision: 1.427.4.6 . # Guess values for system-dependent variables and create Makefiles. # Generated by GNU Autoconf 2.57 for python 2.3. *************** *** 11350,11355 **** which can conflict with char pthread_detach (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. */ ! #ifdef __STDC__ # include <limits.h> #else --- 11350,11357 ---- which can conflict with char pthread_detach (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. Under hpux, ! including <limits.h> includes <sys/time.h> and causes problems ! checking for functions defined therein. */ ! #if defined (__STDC__) && !defined (_HPUX_SOURCE) # include <limits.h> #else *************** *** 12301,12306 **** which can conflict with char $ac_func (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. */ ! #ifdef __STDC__ # include <limits.h> #else --- 12303,12310 ---- which can conflict with char $ac_func (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. Under hpux, ! including <limits.h> includes <sys/time.h> and causes problems ! checking for functions defined therein. */ ! #if defined (__STDC__) && !defined (_HPUX_SOURCE) # include <limits.h> #else *************** *** 12886,12891 **** which can conflict with char $ac_func (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. */ ! #ifdef __STDC__ # include <limits.h> #else --- 12890,12897 ---- which can conflict with char $ac_func (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. Under hpux, ! including <limits.h> includes <sys/time.h> and causes problems ! checking for functions defined therein. */ ! #if defined (__STDC__) && !defined (_HPUX_SOURCE) # include <limits.h> #else *************** *** 13101,13106 **** which can conflict with char $ac_func (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. */ ! #ifdef __STDC__ # include <limits.h> #else --- 13107,13114 ---- which can conflict with char $ac_func (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. Under hpux, ! including <limits.h> includes <sys/time.h> and causes problems ! checking for functions defined therein. */ ! #if defined (__STDC__) && !defined (_HPUX_SOURCE) # include <limits.h> #else *************** *** 13999,14004 **** which can conflict with char $ac_func (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. */ ! #ifdef __STDC__ # include <limits.h> #else --- 14007,14014 ---- which can conflict with char $ac_func (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. Under hpux, ! including <limits.h> includes <sys/time.h> and causes problems ! checking for functions defined therein. */ ! #if defined (__STDC__) && !defined (_HPUX_SOURCE) # include <limits.h> #else *************** *** 14145,14150 **** which can conflict with char $ac_func (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. */ ! #ifdef __STDC__ # include <limits.h> #else --- 14155,14162 ---- which can conflict with char $ac_func (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. Under hpux, ! including <limits.h> includes <sys/time.h> and causes problems ! checking for functions defined therein. */ ! #if defined (__STDC__) && !defined (_HPUX_SOURCE) # include <limits.h> #else *************** *** 14298,14303 **** which can conflict with char $ac_func (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. */ ! #ifdef __STDC__ # include <limits.h> #else --- 14310,14317 ---- which can conflict with char $ac_func (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. Under hpux, ! including <limits.h> includes <sys/time.h> and causes problems ! checking for functions defined therein. */ ! #if defined (__STDC__) && !defined (_HPUX_SOURCE) # include <limits.h> #else *************** *** 14387,14392 **** which can conflict with char $ac_func (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. */ ! #ifdef __STDC__ # include <limits.h> #else --- 14401,14408 ---- which can conflict with char $ac_func (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. Under hpux, ! including <limits.h> includes <sys/time.h> and causes problems ! checking for functions defined therein. */ ! #if defined (__STDC__) && !defined (_HPUX_SOURCE) # include <limits.h> #else *************** *** 14474,14479 **** which can conflict with char $ac_func (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. */ ! #ifdef __STDC__ # include <limits.h> #else --- 14490,14497 ---- which can conflict with char $ac_func (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. Under hpux, ! including <limits.h> includes <sys/time.h> and causes problems ! checking for functions defined therein. */ ! #if defined (__STDC__) && !defined (_HPUX_SOURCE) # include <limits.h> #else *************** *** 14598,14603 **** which can conflict with char $ac_func (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. */ ! #ifdef __STDC__ # include <limits.h> #else --- 14616,14623 ---- which can conflict with char $ac_func (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. Under hpux, ! including <limits.h> includes <sys/time.h> and causes problems ! checking for functions defined therein. */ ! #if defined (__STDC__) && !defined (_HPUX_SOURCE) # include <limits.h> #else *************** *** 14722,14727 **** which can conflict with char $ac_func (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. */ ! #ifdef __STDC__ # include <limits.h> #else --- 14742,14749 ---- which can conflict with char $ac_func (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. Under hpux, ! including <limits.h> includes <sys/time.h> and causes problems ! checking for functions defined therein. */ ! #if defined (__STDC__) && !defined (_HPUX_SOURCE) # include <limits.h> #else *************** *** 15102,15107 **** which can conflict with char $ac_func (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. */ ! #ifdef __STDC__ # include <limits.h> #else --- 15124,15131 ---- which can conflict with char $ac_func (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. Under hpux, ! including <limits.h> includes <sys/time.h> and causes problems ! checking for functions defined therein. */ ! #if defined (__STDC__) && !defined (_HPUX_SOURCE) # include <limits.h> #else *************** *** 16467,16472 **** which can conflict with char gethostbyname_r (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. */ ! #ifdef __STDC__ # include <limits.h> #else --- 16491,16498 ---- which can conflict with char gethostbyname_r (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. Under hpux, ! including <limits.h> includes <sys/time.h> and causes problems ! checking for functions defined therein. */ ! #if defined (__STDC__) && !defined (_HPUX_SOURCE) # include <limits.h> #else *************** *** 16742,16747 **** which can conflict with char $ac_func (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. */ ! #ifdef __STDC__ # include <limits.h> #else --- 16768,16775 ---- which can conflict with char $ac_func (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. Under hpux, ! including <limits.h> includes <sys/time.h> and causes problems ! checking for functions defined therein. */ ! #if defined (__STDC__) && !defined (_HPUX_SOURCE) # include <limits.h> #else *************** *** 16835,16840 **** which can conflict with char __fpu_control (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. */ ! #ifdef __STDC__ # include <limits.h> #else --- 16863,16870 ---- which can conflict with char __fpu_control (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. Under hpux, ! including <limits.h> includes <sys/time.h> and causes problems ! checking for functions defined therein. */ ! #if defined (__STDC__) && !defined (_HPUX_SOURCE) # include <limits.h> #else *************** *** 17067,17072 **** which can conflict with char $ac_func (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. */ ! #ifdef __STDC__ # include <limits.h> #else --- 17097,17104 ---- which can conflict with char $ac_func (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since ! <limits.h> exists even on freestanding compilers. Under hpux, ! including <limits.h> includes <sys/time.h> and causes problems ! checking for functions defined therein. */ ! #if defined (__STDC__) && !defined (_HPUX_SOURCE) # include <limits.h> #else

1 0

python/dist/src/Doc Makefile,1.268,1.269
by fdrake＠users.sourceforge.net Sept. 27, 2003

Sept. 27, 2003

Update of /cvsroot/python/python/dist/src/Doc In directory sc8-pr-cvs1:/tmp/cvs-serv14021 Modified Files: Makefile Log Message: update one more reference to a file that moved from texinputs/ to commontex/ Index: Makefile =================================================================== RCS file: /cvsroot/python/python/dist/src/Doc/Makefile,v retrieving revision 1.268 retrieving revision 1.269 diff -C2 -d -r1.268 -r1.269 *** Makefile 27 Sep 2003 07:37:09 -0000 1.268 --- Makefile 27 Sep 2003 07:48:25 -0000 1.269 *************** *** 349,353 **** # files are not used to actually generate content. ! BOILERPLATE=texinputs/boilerplate.tex html/index.html: $(INDEXFILES) html/index.html: html/index.html.in $(BOILERPLATE) tools/rewrite.py --- 349,353 ---- # files are not used to actually generate content. ! BOILERPLATE=commontex/boilerplate.tex html/index.html: $(INDEXFILES) html/index.html: html/index.html.in $(BOILERPLATE) tools/rewrite.py

1 0

python/dist/src/Doc Makefile,1.261.4.6,1.261.4.7
by fdrake＠users.sourceforge.net Sept. 27, 2003

Sept. 27, 2003

Update of /cvsroot/python/python/dist/src/Doc In directory sc8-pr-cvs1:/tmp/cvs-serv13980 Modified Files: Tag: release23-maint Makefile Log Message: update one more reference to a file that moved from texinputs/ to commontex/ Index: Makefile =================================================================== RCS file: /cvsroot/python/python/dist/src/Doc/Makefile,v retrieving revision 1.261.4.6 retrieving revision 1.261.4.7 diff -C2 -d -r1.261.4.6 -r1.261.4.7 *** Makefile 27 Sep 2003 07:36:18 -0000 1.261.4.6 --- Makefile 27 Sep 2003 07:48:04 -0000 1.261.4.7 *************** *** 349,353 **** # files are not used to actually generate content. ! BOILERPLATE=texinputs/boilerplate.tex html/index.html: $(INDEXFILES) html/index.html: html/index.html.in $(BOILERPLATE) tools/rewrite.py --- 349,353 ---- # files are not used to actually generate content. ! BOILERPLATE=commontex/boilerplate.tex html/index.html: $(INDEXFILES) html/index.html: html/index.html.in $(BOILERPLATE) tools/rewrite.py

1 0

python/dist/src/Doc Makefile,1.267,1.268
by fdrake＠users.sourceforge.net Sept. 27, 2003

Sept. 27, 2003

Update of /cvsroot/python/python/dist/src/Doc In directory sc8-pr-cvs1:/tmp/cvs-serv12412 Modified Files: Makefile Log Message: Adjust the organization a bit and update some of the comments to better explain what's happening. Index: Makefile =================================================================== RCS file: /cvsroot/python/python/dist/src/Doc/Makefile,v retrieving revision 1.267 retrieving revision 1.268 diff -C2 -d -r1.267 -r1.268 *** Makefile 27 Sep 2003 07:11:15 -0000 1.267 --- Makefile 27 Sep 2003 07:37:09 -0000 1.268 *************** *** 72,82 **** 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 --- 72,75 ---- *************** *** 84,90 **** # current implementation and Makefile structure). We use the GNUish # $(shell) function here to work around that restriction by ! # identifying mkhowto using an absolute path. # ! MKHOWTO= TEXINPUTS=$(TEXINPUTS) $(PYTHON) $(PWD)/tools/mkhowto MKDVI= $(MKHOWTO) --paper=$(PAPER) --dvi --- 77,95 ---- # current implementation and Makefile structure). We use the GNUish # $(shell) function here to work around that restriction by ! # identifying mkhowto and the commontex/ directory using absolute paths. # ! 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: ! ! # The mkhowto script can be run from the checkout using the first ! # version of this variable definition, or from a preferred version ! # using the second version. The standard documentation is typically ! # built using the second flavor, where the preferred version is from ! # the Python CVS trunk. ! #MKHOWTO= TEXINPUTS=$(TEXINPUTS) $(PYTHON) $(PWD)/tools/mkhowto ! MKHOWTO= TEXINPUTS=$(TEXINPUTS) mkhowto MKDVI= $(MKHOWTO) --paper=$(PAPER) --dvi

1 0