[Python-checkins] python/dist/src/Doc ACKS, 1.39, 1.39.8.1 Makefile, 1.261, 1.261.4.1 README, 1.49, 1.49.8.1 python-docs.txt, 1.1, 1.1.18.1

bwarsaw at users.sourceforge.net bwarsaw at users.sourceforge.net
Mon Aug 4 16:50:14 EDT 2003


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

Modified Files:
      Tag: release23-maint
	ACKS Makefile README python-docs.txt 
Log Message:
Merging release23-branch into the long-term Python 2.3 maintenance branch


Index: ACKS
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/ACKS,v
retrieving revision 1.39
retrieving revision 1.39.8.1
diff -C2 -d -r1.39 -r1.39.8.1
*** ACKS	30 Jun 2003 12:18:52 -0000	1.39
--- ACKS	4 Aug 2003 22:49:41 -0000	1.39.8.1
***************
*** 5,9 ****
  documentation.  It is probably not complete -- if you feel that you or
  anyone else should be on this list, please let us know (send email to
! python-docs at python.org), and we'll be glad to correct the problem.
  
  It is only with the input and contributions of the Python community
--- 5,9 ----
  documentation.  It is probably not complete -- if you feel that you or
  anyone else should be on this list, please let us know (send email to
! docs at python.org), and we'll be glad to correct the problem.
  
  It is only with the input and contributions of the Python community

Index: Makefile
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/Makefile,v
retrieving revision 1.261
retrieving revision 1.261.4.1
diff -C2 -d -r1.261 -r1.261.4.1
*** Makefile	29 Jul 2003 03:11:34 -0000	1.261
--- Makefile	4 Aug 2003 22:49:41 -0000	1.261.4.1
***************
*** 50,54 ****
  # PostScript, look in the paper-$(PAPER)/ directory.  For HTML, look in
  # the html/ directory.  If you want to fix the GNU info process, look
! # in the info/ directory; please send patches to python-docs at python.org.
  
  # This Makefile only includes information on how to perform builds; for
--- 50,54 ----
  # PostScript, look in the paper-$(PAPER)/ directory.  For HTML, look in
  # the html/ directory.  If you want to fix the GNU info process, look
! # in the info/ directory; please send patches to docs at python.org.
  
  # This Makefile only includes information on how to perform builds; for
***************
*** 67,71 ****
  # This is the *documentation* release, and is used to construct the file
  # names of the downloadable tarballs.
! RELEASE=2.3
  
  PYTHON=	   python
--- 67,71 ----
  # This is the *documentation* release, and is used to construct the file
  # names of the downloadable tarballs.
! RELEASE=2.3+
  
  PYTHON=	   python

Index: README
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/README,v
retrieving revision 1.49
retrieving revision 1.49.8.1
diff -C2 -d -r1.49 -r1.49.8.1
*** README	8 Jul 2003 18:05:26 -0000	1.49
--- README	4 Aug 2003 22:49:41 -0000	1.49.8.1
***************
*** 67,82 ****
  Documentation Team:
  
! 	python-docs at python.org
  
  Thanks!
- 
- 
- What happened to the Macintosh chapter of the Python Library Reference?
- -----------------------------------------------------------------------
- 
- The directory mac/ contains the LaTeX sources for the "Macintosh
- Library Modules" manual; this is built using the standard build
- targets, so check the proper output directory for your chosen format
- and paper size.
  
  
--- 67,73 ----
  Documentation Team:
  
! 	docs at python.org
  
  Thanks!
  
  

Index: python-docs.txt
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/python-docs.txt,v
retrieving revision 1.1
retrieving revision 1.1.18.1
diff -C2 -d -r1.1 -r1.1.18.1
*** python-docs.txt	12 Aug 2002 22:01:42 -0000	1.1
--- python-docs.txt	4 Aug 2003 22:49:41 -0000	1.1.18.1
***************
*** 1,4 ****
  This message is being sent in response to your message to the Python
! documentation maintainers (python-docs at python.org).  Your message will
  be handled by a human, but this message serves to answer the most
  common questions sent to this address.
--- 1,4 ----
  This message is being sent in response to your message to the Python
! documentation maintainers (docs at python.org).  Your message will
  be handled by a human, but this message serves to answer the most
  common questions sent to this address.
***************
*** 97,101 ****
        Start by reading the documentation for XXX.  If the
        documentation doesn't make sense or seems incomplete, please
!       file a specific bug report to python-docs at python.org (the
        address you sent your question to).  Otherwise, you probably
        sent your question to the wrong place (which does not preclude
--- 97,101 ----
        Start by reading the documentation for XXX.  If the
        documentation doesn't make sense or seems incomplete, please
!       file a specific bug report to docs at python.org (the
        address you sent your question to).  Otherwise, you probably
        sent your question to the wrong place (which does not preclude
***************
*** 125,129 ****
  
        Chances are very good that the person who answers questions
!       posted to python-docs at python.org doesn't use Jython very often, 
        and won't be able to give you a meaningful answer beyond "Look
        at the Jython website."  Sorry, I don't have *all* the answers!
--- 125,129 ----
  
        Chances are very good that the person who answers questions
!       posted to docs at python.org doesn't use Jython very often, 
        and won't be able to give you a meaningful answer beyond "Look
        at the Jython website."  Sorry, I don't have *all* the answers!
***************
*** 132,136 ****
  
        If you're reading this, you've found the right address!  Send
!       all documentation bug reports to python-docs at python.org.  If
        you prefer to use a Web-based reporting mechanism, you can use
        the bug database at http://www.python.org/python-bugs/.
--- 132,136 ----
  
        If you're reading this, you've found the right address!  Send
!       all documentation bug reports to docs at python.org.  If
        you prefer to use a Web-based reporting mechanism, you can use
        the bug database at http://www.python.org/python-bugs/.





More information about the Python-checkins mailing list