[Zope-Checkins] CVS: Zope/doc - CHANGES.txt:1.625.2.22
TODO.txt:1.18.2.6
Chris McDonough
chrism at zope.com
Tue Aug 26 14:44:44 EDT 2003
Update of /cvs-repository/Zope/doc
In directory cvs.zope.org:/tmp/cvs-serv14046/doc
Modified Files:
Tag: Zope-2_7-branch
CHANGES.txt TODO.txt
Log Message:
Prep for 2.7b2.
=== Zope/doc/CHANGES.txt 1.625.2.21 => 1.625.2.22 ===
--- Zope/doc/CHANGES.txt:1.625.2.21 Wed Aug 20 10:45:58 2003
+++ Zope/doc/CHANGES.txt Tue Aug 26 13:44:13 2003
@@ -4,15 +4,32 @@
Change information for previous versions of Zope can be found in the
file HISTORY.txt.
- Post-2.7.0b1
+ 2.7.0b2
- Bugs fixed
+ Features added
+
+ - New zopectl feature: adduser. Instead of using the inituser
+ mechanism, "zopectl adduser <name> <password>" will add a user
+ with the 'Manager' role to your site. This is useful both
+ interactively and for packagers.
- New top-level package: nt_svcutils. This takes the place of
- the Zope.Startup.nt packagei to allow for reuse outside of Zope.
+ the Zope.Startup.nt package to allow for reuse outside of Zope.
- - Add a check to the configurator to ensure that the Python found
- has the pyexpat module.
+ - Renamed the "service file" for a Zope instance under Windows
+ from ntservice.py to zopeservice.py to allow a ZEO server
+ instance to share the same instance home as a Zope instance
+ (the ZEO service file will be called zeoservice.py).
+
+ - The TemporaryStorage module was moved from
+ Products/TemporaryFolder to a new top-level package named
+ tempstorage.
+
+ - Split functionality of mkzopeinstance into two separate
+ modules: mkzopeinstance.py and copyzopeskel.py.
+ copyzopeskel.py can be used directly by packagers to install
+ custom skeleton directories or mkzopeinstance can use a custom
+ skeleton directory via the '--skelsrc' flag.
- Added 'environment' and 'path' directives to config file directive
list. 'environment' is a section which allows the user to specify
@@ -27,6 +44,21 @@
during startup (the transitive set of all imported modules
within Products.TemporaryStorage).
+ - Add a check to the configurator to ensure that the Python found
+ has an expat parser.
+
+ Bugs fixed
+
+ - The Products directory in an instance home was not
+ automatically added to the Products.__path__ (it needed to be
+ specified manually). It is now automatically added at instance
+ startup.
+
+ - The Windows runzope.bat file generated by mkzopeinstance from
+ the default skeleton directory now uses python.exe instead of
+ pythonw.exe, so you can actually see output from the Zope
+ process when you run it interactively.
+
- backport of TAL fixes from z3
* i18n and metal interactions
@@ -57,6 +89,73 @@
nonexistent Startup.getSchema function.
- VHM: manage_edit has been broken
+
+ - The container-class keyword to database sections
+ didn't work.
+
+ - ZConfig didn't report a line number and munged capitalization
+ of replacement keys when a replacement error was provided.
+
+ - log-to-stderr on startup will now emit messages to the console at
+ the lowest logging level defined by any of the handlers in the
+ eventlog section.
+
+ - entirely removed warning when the starting user's umask is "too
+ permissive". it wasn't clear that it added any value under normal
+ operations.
+
+ - debug-mode config file option did not work.
+
+ - ZClasses that subclassed ObjectManager that were created in
+ earlier versions of Zope would not load under 2.6, due to
+ the new Interfaces package. Added back a simple stub module
+ and changed a constructor to allow these ZClasses to work.
+
+ - Bugfix: if zopectl is run as the root user, the debug, run, and
+ adduser commands will cause the Python process which performs
+ those actions to switch users to the effective user. This
+ prevents ZODB index files, log files, etc. from being written
+ as root, potentially preventing later startup by the effective
+ user.
+
+ - Bugfix: allow the zopectl process to ascertain the program that
+ zdrun should run from the Zope config file. This is necessary
+ if the file is moved out of a "single-directory-as-instance"
+ instance home.
+
+ - Various fixes to content of ZopeTutorial to deal with URLs moving
+ on new.zope.org (thanks to Stefane Fermigier).
+
+ - Added optparse and textwrap modules to docutils package to prevent
+ ReST barfage (AJ).
+
+ - Added a sample zeoclient and tempstorage stanzas to the default
+ config file (zope.conf.in).
+
+ - Various tweaks to the dbtab configuration code (Shane).
+
+ - Various fixes/enhancements to ZODB/ZEO (PythonLabs).
+
+ - Removed 'inst/Zope.spec' Zope RPM spec file in favor of placing
+ it in a separate internal ZC repository. It will be available
+ in the SRPM.
+
+ - Fix for Collector 823 (XML RPC exception values were always
+ converted to strings and thus turned into a Fault object).
+ Thanks to Sandor Palfy for the patch.
+
+ - Remove --zeo/-z flags from mkzopeinstance.py, as custom_zodb.py
+ is no longer the preferred method of configuring custom
+ storages now that we have DBTab in the core, and you should be
+ able to create a custom skeleton dir with the right
+ zope.conf.in that has a zeo client storage set up if you need
+ to.
+
+ - 'make sdist' now creates a file with an extension of '.tgz'
+ rather than .'.tar.gz' (mainly to meet the expectations of
+ Zope.org about file names).
+
+ - moved 'zpasswd.py' into utilities directory in source tree.
2.7.0b1
=== Zope/doc/TODO.txt 1.18.2.5 => 1.18.2.6 ===
--- Zope/doc/TODO.txt:1.18.2.5 Thu Aug 21 15:13:27 2003
+++ Zope/doc/TODO.txt Tue Aug 26 13:44:13 2003
@@ -82,10 +82,9 @@
port cannot be bound, an error is raised. The error currently doesn't
include the port number, and should.
-
I propose that we add two more options to the config file:
-Create import-directory and extensions-directory directives
+ Create import-directory and extensions-directory directives
These would both be multikeys which specify some number of
directories that contained importable zexp files and external
@@ -142,29 +141,6 @@
(to aid GUI builders and to make it possible to have
a meaningful 'zopectl showconfig' or somesuch).
-RPM install should recompile .pycs
-
- The RPM spec file (inst/Zope.spec.in) should delete and recompile
- .pycs/.pyos during an RPM install to make sure tracebacks contain
- real Zope filenames instead of filenames relative to the build
- directory. Alternately the RPM install should not contain .pycs or
- .pyos.
-
- XXX Not clear why this is actually needed; importing a module causes
- the __file__ to be updated with the right filename. A nice touch,
- but not required.
-
- AAA Is this a new Python feature or has it always been this way?
- Tracebacks used to show the location of the .pyc where it had been
- compiled, not where it actually lived.
-
-RPM install versioning scheme needs to be documented
-
- The RPM builder has a versioning scheme via the generated Makefile
- in order to allow for the install of multiple simultaneous versions
- of Zope on a single system. This versioning scheme should be
- documented.
-
----------------------------------
COMMUNITY CONCERNS (uncategorized)
----------------------------------
@@ -215,30 +191,22 @@
lockfile-name /var/lock/$HOSTNAME-lockfile
- Give installaler an option to put libs in a user-specifiable
- directory at software installation time.
+ directory at software home installation time.
- Give installer an option to put docs in a user-specifiable directory
at software home installation time.
- - Give installer an option to put instance skeleton files 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.
- Offer to install software home 'bin' scripts into a directory
separate from the software home 'bin' directory.
- - To help binary distribution creators, mkzopeinstance probably needs
- to make it easier to place instance files in separate directories
- and needs to generate a zope.conf that reflects
- logfile/lockfile/pidfile placement options that can be fed on the
- command line.
-
- - Allow a custom Zope.conf.in to be used by someone invoking
- mkzopeinstance?
-
- Allow for the installation of platform-dependent files (basically
Python extensions) to be installed to a place separate than that of
platform independent files (as requested by Luca DeVitis).
+ - 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
+ so UNIX has a chance to setuid. This is unnecessary for Windows.
More information about the Zope-Checkins
mailing list