Zope 2 2.4.1b1

Milestone information

Project:
Zope 2
Series:
2.4
Version:
2.4.1b1
Released:
 
Registrant:
Sidnei da Silva
Release registered:
Active:
No. Drivers cannot target bugs and blueprints to this milestone.  

Download RDF metadata

Activities

Assigned to you:
No blueprints or bugs assigned to you.
Assignees:
No users assigned to blueprints and bugs.
Blueprints:
No blueprints are targeted to this milestone.
Bugs:
No bugs are targeted to this milestone.

Download files for this release

File Description Downloads

Release notes 

Building and installing Zope from source
----------------------------------------

  This document describes building and installing Zope on Unix.
  We will provide Windows instructions in later releases. We
  will also provide binary releases for some platforms.

Important notes

   ZOPE 2.4 REQUIRES PYTHON 2.1!

   See CHANGES.txt for important notes on Zope 2.4.

Quick Start

  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
    ./start

  The first command builds and adjusts Zope. Take note of the user
  name and password output at the end of this command. You will need
  these to manage Zope.

  If you get errors indicating that addresses are in use, then you
  will have to supply arguments to z2.py to change the ports used for
  HTTP or FTP. The default HTTP and FTP ports used by ZServer are 8080
  and 8021 respectively. (See the help for the z2.py script by running
  z2.py with the -h option for more information on how to specify
  different ports)

  You can then connect to Zope 2 by directing your browser to::

     http://yourhost:8080/manage

  where yourhost is the name or address of the machine running Zope 2.
  If you changed the HTTP port with the -w option to z2.py, then use
  it rather than 8080.

  You will be prompted for a user name and password. Use the user name
  and password output above.

  Now you're off and running! You should be looking at the Zope management
  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.

  If you want to try out Zope in the simplest fashion using ZServer,
  then run the script wo_pcgi::

    python wo_pcgi.py

  If you want to use PCGI and an existing web server run w_pcgi::

    python w_pcgi.py

  Notes

    * You should be using Python 2.1 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.

    * 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.

    * You can use PCGI and an existing web server if you use ZServer.

Starting Zope with an existing web server

  See the WEBSERVERS.txt file for more information about configuring Zope
  with an existing web server.

Running Zope

  There are two ways to run Zope:

  - You can use ZServer, the integration of Zope and Medusa. You must
    use ZServer if you want to use multiple concurrent threads.
    ZServer is a server application that supports multiple protocols:

      o HTTP -- ZServer is a Web server

      o FTP -- ZServer is a file-transfer protocol server. This
        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.

      o monitor -- ZServer has the capability to allow you to access
        the Python interpreter directly over a network channel. If
        you intend to use this, please read the 'DEBUGGING.txt'
        document for more information.

    With ZServer, you must start Zope manually using the z2.py script.
    Typically, the command used to run the z2.py script will be put in
    system startup scripts.

    ZServer is the prefered way to run Zope.

  - If you *only* want to use PCGI and you don't need multi-threaded
    operation, you can have a special program, the pcgi_publisger,
    start Zope for you. See the WEBSERVER.txt file for details on
    using Zope with an existing webserver.

  If you wish to enable Zope logging you must specify options on the
  command line. See LOGGING.txt in the doc directory.

Changelog 

View the full changelog

Zope Changes

  This file contains change information for the current Zope release.
  Change information for previous versions of Zope can be found in the
  file HISTORY.txt.

    Zope 2.4.1 beta 1

      Bugs fixed

        - Collector #2412: a read-only FileStorage has not been closed
          properly.

        - Collector #2438: Using a slice operation like [30:] on a
          ZCatalog search result caused a MemoryError because
          the __getslice__ implementation used range() instead
          of xrange().

        - Collector #2423: Searching a FieldIndexes for documents
          with a blank string has been broken.

        - Collector #2347: there was no interface for incrementally
          refreshing a ZCatalog.

        - Collector #2336: Quoting and globbing in non-trivial queries
          were broken. All tests now pass.

        - Collector #2427, 2429: Tests for keys() was missing.
          Incorporated Chris Withers' fix.

        - WebDAV Lockmanager was not working due to a Python 2.1
          incompatibility.

        - Collector #2482: A COPY operation through WebDAV on a locked
          resource left the destination resource in a locked state
          so any WebDAV client was unable to unlock the destination
          object. Locks are now cleared from the destination object.

        - Collector #2481: adjusted punctuation for link generation
          (not working with ! inside quoted text)

        - Error message AttributeError/_v_blocks when a DTMLfile is
          not present or could not be read replaced by a more
          informative message.

        - Simplified the way product refresh happens. Instead of using
          the reload() function, we just remove the appropriate modules
          from sys.modules. This ensures that modules are loaded in the
          correct order.

        - Fixes to Splitter interfaces to work correctly under MacOSX

        - Collector #2497: SERVER_PROTOCOL variable is now compliant
          with the CGI specification and looks like "HTTP/1.1" instead
          of "1.1"

        - Creation of a TextIndex ignored the vocabulary setting.

        - Fixed broken aquisition of vocabularies from a Catalog
          by a TextIndex.

        - Collector #2504: level parameter has not been passed to HTMLClass
          constructor

        - default for 'orphan' attribute of <dtml-in> is now 0 instead 3.

        - Skip attempting to register APIHelp for files beginning with '_'
          (e.g., '__init__.py'). Allows HelpSys to build help from a
          "real" Python package.

        - Fixed conflict resolution problem in BTrees (BTreeTemplace/
          _p_resolveConflict)

        - Fixed conflict resolution problem in BTrees (BTreeTemplace/
          _p_resolveConflict)

        - Add 'WEBDAV_SOURCE_PORT' marker key to REQUEST.env for requests
          passing through a WebDAV source port (eases detection).

0 blueprints and 0 bugs targeted

There are no feature specifications or bug tasks targeted to this milestone. The project's maintainer, driver, or bug supervisor can target specifications and bug tasks to this milestone to track the things that are expected to be completed for the release.

This milestone contains Public information
Everyone can see this information.