[Zope-Checkins] CVS: Zope/doc - CHANGES.txt:1.528.2.7 INSTALL.txt:1.32.10.3
Chris McDonough
chrism@zope.com
Tue, 8 Oct 2002 17:46:11 -0400
Update of /cvs-repository/Zope/doc
In directory cvs.zope.org:/tmp/cvs-serv17057/doc
Modified Files:
Tag: chrism-install-branch
CHANGES.txt INSTALL.txt
Log Message:
More merges from HEAD.
=== Zope/doc/CHANGES.txt 1.528.2.6 => 1.528.2.7 ===
--- Zope/doc/CHANGES.txt:1.528.2.6 Tue Oct 8 14:41:03 2002
+++ Zope/doc/CHANGES.txt Tue Oct 8 17:45:37 2002
@@ -4,7 +4,78 @@
Change information for previous versions of Zope can be found in the
file HISTORY.txt.
+ Zope 2.7.0 alpha 1
+
+ Features Added
+
+ - ZTUtils.Tree.TreeMaker now has additional methods for setting
+ various flags and attributes that influence how the tree is built,
+ making these aspects accessible to PythonScripts.
+
+ - ZTUtils.Tree.TreeMaker has a new method setStateFunction, which
+ allows you to set a callback function that can influence the state
+ (open, closed, leaf) of each node in the tree.
+
+ - Pidfile handling improved. When Zope is started under
+ zdaemon, it no longer writes its own pidfile. Instead, it
+ passes in the path to Z2.pid to zdaemon as its pidfile name.
+ The 'zProcessManager.pid' file is no longer ever written.
+ This caused a change to the -Z option of z2.py which should be
+ mostly backwards-compatible (unless people were relying on
+ zProcessManager.pid to be written). Now the -Z option is a
+ boolean. -Z1 means use a daemon. -Z0 means dont. The
+ default is -Z1.
+
+ Bugs Fixed
+
+ - Dumb bug in zdaemon fixed in which it would try to kill
+ process numbers 1, 2, 3, 10, 12, and 15 when it caught a
+ signal related to any of these signal numbers. Instead, it
+ actually tries now to kill its child process with the same
+ signal.
+
+ - Write pidfiles out with trailing newlines.
+
+ Zope 2.6.0 beta 1
+
Bugs Fixed
+
+ - Collector #449: PathIndex did not index the last part of path.
+
+ - Collector #539: Fixed rendering of TAL namespace tags with an
+ 'on-error' statement.
+
+ - Collector #586: Generated 'start' scripts had a nonsensical
+ export of an "INST_HOME" environment variable.
+
+ - Collector #538: Hybrid path expressions no longer attempt to call
+ a value returned by the final, non-path alternate.
+
+ - Collector #573: ZTUtils Iterator didn't catch AttributeError.
+
+ - Deprecated hasRole alias in User.py failed to return result.
+
+ - Collector #580: TALES evaluateBoolean() was squishing 'default'.
+
+ - Collector #581: TALES Path traversal should not special-case a blank
+ string in the second element position. It now skips directly
+ to item access when a path element is blank or has a leading '_'.
+
+ - Fixed inconsistent attribute access in TALES Paths.
+
+ - Collector #587: fixed wrong migration to string methods in
+ DTMLMethod.py
+
+ - Collector #583: Searching for '/' with PathIndexes failed.
+
+ - Fixed bug in manage_editProperties which used an incorrect default
+ for several types of property when they were not found in the
+ REQUEST.
+
+ - Collector #574: Fixed write on HEAD requests caused by overzealous
+ ETag support.
+
+ - Fixed broken management form for TopicIndexes.
- Fixed bug in z2.py where it would eat certain socket error exceptions
at startup.
@@ -143,6 +214,9 @@
Features Added
+ - Add optional 'relative' argument to getURL the method in CatalogBrains.
+ This allows it to generate site relative URLs like absolute_url can.
+
- Browser ids can now be encoded in the URL and Zope can be
instructed to automatically include the browser id in its
generated URLs.
@@ -223,7 +297,9 @@
- xmlrpclib has been updated to the Python 2.2 version, which includes
support for the Expat parser for unmarshalling data, which speeds up
things considerably.
-
+
+ - Added i18n support in TAL processing
+
Zope 2.6.0 alpha 1
Features Added
=== Zope/doc/INSTALL.txt 1.32.10.2 => 1.32.10.3 ===
--- Zope/doc/INSTALL.txt:1.32.10.2 Tue Oct 8 14:41:03 2002
+++ Zope/doc/INSTALL.txt Tue Oct 8 17:45:37 2002
@@ -7,11 +7,10 @@
Important notes
- ZOPE 2.5 REQUIRES PYTHON 2.1.X!
+ Starting with Zope 2.7, Zope *REQUIRES* Python 2.2.1 or later.
+ This is done to ease code sharing with Zope 3.
- Note: Using Python 2.2 is not recommended and not supported.
-
- See CHANGES.txt for important notes on Zope 2.5.
+ See CHANGES.txt for important notes on this version of Zope.
Quick Start
@@ -19,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.1
+ python w_pcgi.py # Note, this must be Python 2.2.1 or later
./start
The first command builds and adjusts Zope. Take note of the user
@@ -74,21 +73,22 @@
Notes
- * You should be using Python 2.1 to run the build scripts.
+ * You should be using Python 2.2.1 or later to run the build scripts.
* The python you run Zope with *must* have threads compiled in,
- which is *not* the case for a vanilla build. When you build the
- python you'll use, 'configure --with-threads' does the right thing.
- Warning: Zope will not run with a Python version that uses libpth.
- You *must* use libpthread.
+ which is the case for a vanilla build. Warning: Zope will not
+ run with a Python version that uses libpth. You *must* use
+ libpthread.
* To build python extensions you need to have Python configuration
- information available. If your Python comes from an RPM you may need
- the python-devel package installed too. If you built Python from source
- all the configuration information should already be there.
-
- * If you just want to use Zope components it's not necessary to build Zope
- but it's a good idea since it will compile Python C extensions for you.
+ information available. If your Python comes from an RPM you may
+ need the python-devel package installed too. If you built Python
+ from source all the configuration information should already be
+ there.
+
+ * If you just want to use Zope components it's not necessary to
+ build Zope but it's a good idea since it will compile Python C
+ extensions for you.
* You can use PCGI and an existing web server if you use ZServer.