Commit 140ff24e authored by Hanno Schlichting's avatar Hanno Schlichting

Updated the what's new document

parent cb9b2eaa
...@@ -16,9 +16,8 @@ Zope 2 has supported and required Python 2.4 since its 2.9 release in summer ...@@ -16,9 +16,8 @@ Zope 2 has supported and required Python 2.4 since its 2.9 release in summer
This version of Zope 2 adds support for both Python 2.5 and 2.6 at the same This version of Zope 2 adds support for both Python 2.5 and 2.6 at the same
time. As Python 2.4 is no longer maintained itself, it is no longer officially time. As Python 2.4 is no longer maintained itself, it is no longer officially
supported by this Zope 2 version. There is however no code in Zope 2 yet which supported by this Zope 2 version. Python 2.4 on 64-bit platforms is known to
requires Python 2.5, so applications built on top of Zope 2 should still be incompatible with Zope 2.12. On 32-bit it could work at your own risk.
continue to run with Python 2.4.
Python 3 is a backwards incompatible release of Python and not supported. At Python 3 is a backwards incompatible release of Python and not supported. At
this point there is no concrete roadmap for adoption of Python 3. It is this point there is no concrete roadmap for adoption of Python 3. It is
...@@ -52,25 +51,29 @@ standard Python mechanisms. To create isolated Python environments both ...@@ -52,25 +51,29 @@ standard Python mechanisms. To create isolated Python environments both
<http://pypi.python.org/pypi/virtualenv>`_ are in wide-spread use. <http://pypi.python.org/pypi/virtualenv>`_ are in wide-spread use.
Zope Toolkit Zope 3
------------ ------
This version of Zope 2 is based on the Zope Toolkit. The Zope Toolkit is an This version of Zope 2 does no longer includes a full version of the Zope 3
extraction of the reusable and wildly used packages of the former Zope 3 application server nor a specific release of it. Instead it includes a minimal
project. The Zope Toolkit is focused on supporting frameworks and applications, set of packages from the former Zope 3 project. Only those packages actually
rather than trying to be one itself. Parts of the Zope Toolkit are used by used by Zope 2 itself are still included. Examples of such packages include
Zope 2, Plone, Grok, Repoze.bfg, and by many other different applications and zope.interface, zope.component, zope.i18n, zope.tal and many more.
frameworks.
A major focus of the Zope Toolkit was to refactor package dependencies to Zope 2.12 marks a transitionary release, where a number of zope.app packages
generate more maintainable and better structured code. Based on this effort are still included. An ongoing effort to refactor those packages into more
the number of packages included by Zope 2 could be dramatically reduced from reusable and minimal packages is going on and will result in no zope.app
about 120 additional packages to just over 60. The total code size of Zope 2 packages being used or shipped with anymore as part of Zope 2. Based on
and its dependencies has decreased by over 200,000 lines of code as a result. current progress Zope 2.13 will no longer ship with any zope.app packages.
You can find more information about the changes in the Zope Toolkit at If you are using zope.app packages inside your own codebase, you should make
http://docs.zope.org/zopetoolkit/. Upgrade information from Zope 3 to the Zope sure to declare these as dependencies of your packages or otherwise follow the
Toolkit can be found at http://docs.zope.org/zopetoolkit/migration/index.html. refactoring effort and remove your dependency on these packages.
As a result of this refocussing on more minimal dependencies, the number of
packages included by Zope 2 could be dramatically reduced from about 120
additional packages to just over 70. The total code size of Zope 2 and its
dependencies has decreased by over 200,000 lines of code as a result.
ZODB 3.9 ZODB 3.9
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment