In a straight setupttools-based application, adding one or more
console scripts is straightforward: you just declare them in the
setup.py, and set setuptools build them for you. However, when
using zc.buildout for Plone 3.0.x or 3.1.x, you have to arrange to
get the non-eggified Zope2 products on the path, which is not easy.
This recipe works for me.
A brief proposal on how and when one might prefer to use "standard"
setuptools features, rather than relying on zc.buildout.
I have released version 0.2 of a setuptools plugin to the Cheeseshop.
When installed, the plugin extends the .egg-info generation done by many
setup commands to create a new file, test_info.txt, which captures the
data used by the setup.py test command.
Given that the word "Zope" turns out to be a common name in German-speaking countries for a variety of carp (ballerus ballerus) I found the following note [1] strangely appealing, as well as appropriate.
I mused yesterday that I needed to create eggs for the various ZODB-related packages: I was wrong.
Building on Nathan Yergler's work from PyCon, I have just finished a big pile of eggs for both ZopeX3.0.0 and Zope 3.2.0.
Notes and whiteboard from the first sprint day.
Chris has been steadily at work this week on finishing his Basket product, which makes it possible to distribute Zope add-ons using Phillip Eby's "eggs".
This product is a short-term implementation of the egg-related features, which will go away once the feature lands in the Zope core.