[Python-checkins] python/dist/src/Doc/dist dist.tex,1.55,1.56

fdrake@users.sourceforge.net fdrake@users.sourceforge.net
Wed, 02 Jul 2003 05:27:45 -0700


Update of /cvsroot/python/python/dist/src/Doc/dist
In directory sc8-pr-cvs1:/tmp/cvs-serv13911/dist

Modified Files:
	dist.tex 
Log Message:
Fix a variety of small markup nits.

Index: dist.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/dist/dist.tex,v
retrieving revision 1.55
retrieving revision 1.56
diff -C2 -d -r1.55 -r1.56
*** dist.tex	30 Jun 2003 19:33:29 -0000	1.55
--- dist.tex	2 Jul 2003 12:27:43 -0000	1.56
***************
*** 191,200 ****
  
  \item[extension module] a module written in the low-level language of
!   the Python implementation: C/C++ for Python, Java for Jython.
    Typically contained in a single dynamically loadable pre-compiled
    file, e.g. a shared object (\file{.so}) file for Python extensions on
    \UNIX, a DLL (given the \file{.pyd} extension) for Python extensions
    on Windows, or a Java class file for Jython extensions.  (Note that
!   currently, the Distutils only handles C/C++ extensions for Python.)
  
  \item[package] a module that contains other modules; typically contained
--- 191,200 ----
  
  \item[extension module] a module written in the low-level language of
!   the Python implementation: C/\Cpp{} for Python, Java for Jython.
    Typically contained in a single dynamically loadable pre-compiled
    file, e.g. a shared object (\file{.so}) file for Python extensions on
    \UNIX, a DLL (given the \file{.pyd} extension) for Python extensions
    on Windows, or a Java class file for Jython extensions.  (Note that
!   currently, the Distutils only handles C/\Cpp{} extensions for Python.)
  
  \item[package] a module that contains other modules; typically contained
***************
*** 472,479 ****
  list; the \command{build\_ext} command knows how to deal with SWIG
  extensions: it will run SWIG on the interface file and compile the
! resulting C/C++ file into your extension.
  
  \XXX{SWIG support is rough around the edges and largely untested;
!   especially SWIG support of C++ extensions!  Explain in more detail
    here when the interface firms up.}
  
--- 472,479 ----
  list; the \command{build\_ext} command knows how to deal with SWIG
  extensions: it will run SWIG on the interface file and compile the
! resulting C/\Cpp{} file into your extension.
  
  \XXX{SWIG support is rough around the edges and largely untested;
!   especially SWIG support for \Cpp{} extensions!  Explain in more detail
    here when the interface firms up.}
  
***************
*** 481,485 ****
  by the compiler and included in your extension.  Currently, this just
  means Windows message text (\file{.mc}) files and resource definition
! (\file{.rc}) files for Visual C++. These will be compiled to binary resource
  (\file{.res}) files and linked into the executable.
  
--- 481,485 ----
  by the compiler and included in your extension.  Currently, this just
  means Windows message text (\file{.mc}) files and resource definition
! (\file{.rc}) files for Visual \Cpp. These will be compiled to binary resource
  (\file{.res}) files and linked into the executable.