[Zope-Checkins] CVS: Zope/doc - TODO.txt:1.18.2.7
Tres Seaver
tseaver at zope.com
Fri Jul 2 16:13:28 EDT 2004
Update of /cvs-repository/Zope/doc
In directory cvs.zope.org:/tmp/cvs-serv1598/doc
Modified Files:
Tag: Zope-2_7-branch
TODO.txt
Log Message:
- Typos, some added notes.
=== Zope/doc/TODO.txt 1.18.2.6 => 1.18.2.7 ===
--- Zope/doc/TODO.txt:1.18.2.6 Tue Aug 26 13:44:13 2003
+++ Zope/doc/TODO.txt Fri Jul 2 16:13:28 2004
@@ -119,6 +119,9 @@
At least create a HowTo which summarizes the differences between
installing 2.6 and installing 2.7.
+ See the Zope 2.7 version of the book at
+ http://www.plope.com/Books/2_7Edition
+
------------------------------
MAYBE NEVER BUT NICE TO HAVE
------------------------------
@@ -139,7 +142,13 @@
It would be nice if ZConfig kept enough state to be able to
reconstitute the configuration in textual representation
(to aid GUI builders and to make it possible to have
- a meaningful 'zopectl showconfig' or somesuch).
+ a meaningful 'zopectl showconfig' or somesuch).
+
+ XXX Even better, change ZConfig to do two-phase parsing, and rip out
+ *anything* which tries to execute handlers during the first phase.
+ The first phase should *only* create a DOM-ish / AST-like data structure,
+ with pointers to the handlers; the second phase would then walk that
+ structure, executiing handlers.
----------------------------------
COMMUNITY CONCERNS (uncategorized)
@@ -190,14 +199,17 @@
lockfile-name /var/lock/$HOSTNAME-lockfile
- - Give installaler an option to put libs in a user-specifiable
+ - Give installaer an option to put libs in a user-specifiable
directory at software home installation time.
- Give installer an option to put docs in a user-specifiable directory
at software home installation time.
- Make it possible to install Zope-related Python libraries to
- The site-packages of the Python used to invoke setup.py.
+ the site-packages of the Python used to invoke setup.py.
+
+ XXX: I would just leave this as a special case of the item two entries
+ up.
- Offer to install software home 'bin' scripts into a directory
separate from the software home 'bin' directory.
@@ -208,5 +220,5 @@
- Upon failure of Windows service startup, it's possible for the
reason for the failure to not be logged anywhere. This is because
- we carefully wait til late in the startup process to write logfiles
+ we carefully wait until late in the startup process to write logfiles
so UNIX has a chance to setuid. This is unnecessary for Windows.
More information about the Zope-Checkins
mailing list