Update of /cvsroot/docstring/dps
In directory usw-pr-cvs1:/tmp/cvs-serv14176/dps
Modified Files:
README.txt
Log Message:
brought up to date
Index: README.txt
===================================================================
RCS file: /cvsroot/docstring/dps/README.txt,v
retrieving revision 1.1.1.1
retrieving revision 1.2
diff -C2 -d -r1.1.1.1 -r1.2
*** README.txt 2001/07/22 22:36:35 1.1.1.1
--- README.txt 2001/07/29 15:55:58 1.2
***************
*** 5,9 ****
Author: David Goodger
Contact: dgo...@bi...
- Version: 0.3
Date: $Date$
Web-site: http://docstring.sourceforge.net/
--- 5,8 ----
***************
*** 18,23 ****
! Archive Contents
! ================
* README.txt: You're reading it.
--- 17,22 ----
! Project Files & Directories
! ===========================
* README.txt: You're reading it.
***************
*** 28,41 ****
* setup.py: Installation script. See "Installation" below.
! * spec: The project specification directory. Contains PEPs (Python
! Enhancement Proposals) and XML DTDs (document type definitions)
* dps: The project source directory, installed as a Python package.
Installation
============
! The first step is to expand the dps.0.3.tar.gz archive. It contains a
distutils setup file "setup.py". OS-specific installation instructions
follow.
--- 27,42 ----
* setup.py: Installation script. See "Installation" below.
! * install.py: Quick & dirty installation script.
* dps: The project source directory, installed as a Python package.
+ * spec: The project specification directory. Contains PEPs (Python
+ Enhancement Proposals) and XML DTDs (document type definitions)
+
Installation
============
! The first step is to expand the .tar.gz archive. It contains a
distutils setup file "setup.py". OS-specific installation instructions
follow.
***************
*** 58,61 ****
--- 59,64 ----
permissions to complete this step.
+ You can also just run install.py; it does the same thing.
+
Windows
-------
***************
*** 72,75 ****
--- 75,81 ----
<path_to_python.exe>\python setup.py install
+ If your system is set up to run Python when you double-click on .py
+ files, you can run install.py to do the same as the above.
+
MacOS
-----
***************
*** 83,94 ****
also wrong, and you will need to set up your system to recognize
".py" file extensions as Python files. See
! http://gotools.sf.net/mac/python.html for detailed instructions.
! Once set up, it's easiest to start over by expanding the archive
! again.
3. The distutils options window will appear. From the "Command" popup
list choose "install", click "Add", then click "OK".
Usage
=====
--- 89,104 ----
also wrong, and you will need to set up your system to recognize
".py" file extensions as Python files. See
! http://gotools.sourceforge.net/mac/python.html for detailed
! instructions. Once set up, it's easiest to start over by expanding
! the archive again.
3. The distutils options window will appear. From the "Command" popup
list choose "install", click "Add", then click "OK".
+ If install.py is a "Python module" (see step 2 above if it isn't), you
+ can run it instead of the above. The distutils options windown will
+ not appear.
+
Usage
=====
***************
*** 96,102 ****
The package modules are mostly in their infancy, continually growing
and evolving. The module evolution is being driven by the
! reStructuredText parser project; see http://structuredtext.sf.net. The
! dps.statemachine module is usable independently. It contains extensive
! inline documentation (in reStructuredText format).
The specs, the package structure, and the skeleton modules may also be
--- 106,113 ----
The package modules are mostly in their infancy, continually growing
and evolving. The module evolution is being driven by the
! reStructuredText parser project; see
! http://structuredtext.sourceforge.net. The dps.statemachine module is
! usable independently. It contains extensive inline documentation (in
! reStructuredText format).
The specs, the package structure, and the skeleton modules may also be
|