[Zope-Checkins] CVS: Zope/doc - CHANGES.txt:1.528.2.9 ENVIRONMENT.txt:1.17.2.1 INSTALL.txt:1.32.10.4
Chris McDonough
chrism@zope.com
Sun, 24 Nov 2002 19:13:41 -0500
Update of /cvs-repository/Zope/doc
In directory cvs.zope.org:/tmp/cvs-serv19523
Modified Files:
Tag: chrism-install-branch
CHANGES.txt ENVIRONMENT.txt INSTALL.txt
Log Message:
Merge with HEAD.
=== Zope/doc/CHANGES.txt 1.528.2.8 => 1.528.2.9 ===
--- Zope/doc/CHANGES.txt:1.528.2.8 Sat Oct 26 15:51:35 2002
+++ Zope/doc/CHANGES.txt Sun Nov 24 19:13:39 2002
@@ -8,6 +8,16 @@
Features Added
+ - The zLOG package is now backed by Vinay Sajip's "PEP 282" logger
+ which has been included in lib/python/logging. As a result,
+ the ZLogger package was removed (as its only real duty was to
+ handle syslog-based logging).
+
+ - Zope's shutdown process is now more careful and clean. It
+ avoids sending half-complete responses to clients, particularly
+ when running in a cluster using ICP.
+ http://dev.zope.org/Wikis/DevSite/Proposals/CleanShutdown
+
- ZTUtils.Iterator now handles any object that has a Python
iterator, resolving Collector #385 and #577. The
implementation is somwhat simpler, as well.
@@ -30,7 +40,14 @@
boolean. -Z1 means use a daemon. -Z0 means dont. The
default is -Z1.
+ - Collector #670: applied patch from Dieter Maurer to enhance
+ the Zope profiling support
+
Bugs Fixed
+
+ - Collector #651: WebDAV Lock Manager was broken.
+
+ - Collector #646: metal:slot was lost during the I18n merge.
- Removed the signal handler hung off USR1 for packing the database.
This feature proved dangerous as the pack operation would happen in
=== Zope/doc/ENVIRONMENT.txt 1.17 => 1.17.2.1 ===
--- Zope/doc/ENVIRONMENT.txt:1.17 Tue Aug 20 15:37:51 2002
+++ Zope/doc/ENVIRONMENT.txt Sun Nov 24 19:13:39 2002
@@ -41,12 +41,24 @@
This environment variable can be used to force or suppress
Zope's normal automatic (implicit) product installation. If
- this variable is set, then products are implicitly installed
- is and only if the environment variable has a non-empty value.
+ this variable is set, then persistent objects representing Zope
+ products are implicitly installed if and only if the environment
+ variable has a non-empty value.
If this environment variable is not set, then products are
implicitly installed unless the ZEO_CLIENT environment
variable is set to a non-empty value.
+
+ Here's a table explaining how FORCE_PRODUCT_LOAD and ZEO_CLIENT
+ will effect the behavior of product loading:
+
+ FORCE_PRODUCT_LOAD ZEO_CLIENT RESULT
+ unset unset Products are loaded
+ empty string unset Products are not loaded
+ nonempty string unset Products are loaded
+ unset set Products are not loaded
+ nonempty string set Products are loaded
+ empty string set Products are not loaded
Profiling
=== Zope/doc/INSTALL.txt 1.32.10.3 => 1.32.10.4 ===
--- Zope/doc/INSTALL.txt:1.32.10.3 Tue Oct 8 17:45:37 2002
+++ Zope/doc/INSTALL.txt Sun Nov 24 19:13:39 2002
@@ -7,7 +7,7 @@
Important notes
- Starting with Zope 2.7, Zope *REQUIRES* Python 2.2.1 or later.
+ Starting with Zope 2.7, Zope *REQUIRES* Python 2.2.2 or later.
This is done to ease code sharing with Zope 3.
See CHANGES.txt for important notes on this version of Zope.
@@ -18,7 +18,7 @@
If you are impatient, the following commands should get you up and
running with Zope 2 using ZServer and ZODB 3 on Unix::
- python w_pcgi.py # Note, this must be Python 2.2.1 or later
+ python w_pcgi.py # Note, this must be Python 2.2.2 or later
./start
The first command builds and adjusts Zope. Take note of the user
@@ -47,17 +47,17 @@
screen which is divided into two frames. On the left you can navigate
between Zope object and on the right you can edit them by selecting
different management functions with the tabs at the top of the frame.
-
+
If you haven't used Zope before, you should head to the Zope web site
and read some documentation. The Zope Manager's Guide is a good place
to start. You can access the Zope site at:
-
+
'http://www.zope.org/'
-
+
Have fun!
Building Zope
-
+
There are some python scripts in the top-level directory that should
help you get started. You must run these scripts from the top-level
directory.
@@ -72,8 +72,8 @@
python w_pcgi.py
Notes
-
- * You should be using Python 2.2.1 or later to run the build scripts.
+
+ * You should be using Python 2.2.2 or later to run the build scripts.
* The python you run Zope with *must* have threads compiled in,
which is the case for a vanilla build. Warning: Zope will not
@@ -112,9 +112,9 @@
allows you to use FTP-enabled publishing systems with Zope.
o PCGI -- PCGI is a lightweight protocol for forwarding
- requests from other web servers, like Apache or Netscape, to
- Zope. This makes it possible to use web server features like
- connection encryption or logging with Zope.
+ requests from other web servers, like Apache or Netscape, to
+ Zope. This makes it possible to use web server features like
+ connection encryption or logging with Zope.
o monitor -- ZServer has the capability to allow you to access
the Python interpreter directly over a network channel. If
@@ -134,5 +134,3 @@
If you wish to enable Zope logging you must specify options on the
command line. See LOGGING.txt in the doc directory.
-
-