Python, Plone and Zope

Description

The basics of Python programming, and performing Python interpreter installations.

Introduction

Python is the programming language used by Plone and Zope.

Plone and Zope resources

Plone resources

  • Plone Cheat Sheet. A single list of every technology you need to learn to develop with plone, why you need it and how to learn it. A bit out of date, but a good overview nonetheless.
  • Plone Trac contains bug reports, Plone source code and commits. Useful when you encounter a new exception or you are looking for a reference how to use the API.
  • Plone source code in version control system.

Zope resources

  • Zope 3 API reference. Good source for up-to-date Zope Python API and ZCML references.

  • Zope 2 book. This describes old Zope 2 technologies. The book is mostly good for explaining some old things, but '''do not''' use it as a reference for building new things.

    The chapters on Zope Page Templates however are still the best reference on the topic.

Todo

hyperlink

Installing Python

It is not recommended to use the system-wide Python installation with Plone. There are various reasons for this:

  • Plone may require newer or older package versions, which could conflict with ones installed by your operating system.
  • Installing packages to the system-wide Python installation always requires root privileges, and you could easily hose your box when doing Python development work.
  • You may want to work on different Plone instances, with different versions of Zope and different sets of modules installed.

Plone Unified Installers compile their own, preconfigured, Python interpreter.

If you are a developer, you might wish to use a custom-built Python interpreter, which gives you more control over the configuration.




Edit this document

The source code of this file is hosted on GitHub. Everyone can update and fix errors in this document with few clicks - no downloads needed.

  1. Go to Python, Plone and Zope on GitHub.
  2. Press Fork and edit this file button.
  3. Edit file contents using GitHub's text editor in your web browserm
  4. Fill in the Commit message text box at the end of the page telling why you did the changes. Press Propose file change button next to it when done.
  5. On Send a pull request page you don't need to fill in text anymore. Just press Send pull request button.
  6. Your changes are now queued for review under project's Pull requests tab on Github.

For basic information about updating this manual and Sphinx format please see Writing and updating the manual guide.