Zope 4

Note

New installations should use Zope 5 instead of Zope 4. Users migrating applications from Zope 2 should upgrade to Zope 5 once their application supports Zope 4 on Python 3. The Zope developer community strives to make sure the next upgrade step to Zope 5 is and remains a quick and painless exercise.

• What’s new in Zope 4
  • Restored sane version numbering
  • Extended Python version support
  • WSGI as the new default server type
  • View component Acquisition changes
  • Page Templates now rendered by Chameleon
  • Lower memory consumption at runtime
  • Simplified encoding configuration
  • Restyled Zope Management Interface (ZMI)
• Migrating to Zope 4
  • Zope products that are now distributed separately
    • ZServer
    • Sessioning
    • External Methods
    • Site Error Log
  • Migrating Zope product code
    • Changed import paths
    • implementer versus implements
    • Migrating to the new bootstrap-based ZMI
      • Update existing package code
      • Custom icons and resources
      • Use custom resources via ZMI
      • Update existing Zope 2 ZMI templates
      • More details
  • Migrating content
    • Page Template parsing issues
  • Migrating the ZODB
    • Pre-migration steps on Zope 2
      • Prepare ZODB-based code
      • Delete ZODB objects that no longer exist under Zope 4
    • Migrate to Zope 4 on Python 2
    • Migrate to Zope 4 on Python 3
      • Migration example
        • Going from Zope 2 to Zope 4
        • Going from Python 2 to Python 3
      • Finding broken scripts and templates
      • If you encounter UnicodeDecodeError exceptions
    • Under the hood: Changes in ZODB storage on Python 3
      • The string problem
      • The string solution
      • The code problem
      • The code solution
      • Further reading