On Tuesday 27 November 2007, Nathan Yergler wrote:
So unfortunately it's going to require some more work to fix up the
loader; I'll probably create a branch to work on this some...
Great! Let me know if you have questions. I have once updated the XML
definitions and it was not too bad. It's
Philipp von Weitershausen wrote:
btw, I think since we use buildout, it's not possible to
implement mixed Zope3/Five packages bacause setup has to
define the Five packages too. right?
In general, it makes the reuse of a package difficult if it depends on
Zope 2 stuff (incl. Five).
As
Summary of messages to the zope-tests list.
Period Wed Nov 28 13:00:00 2007 UTC to Thu Nov 29 13:00:00 2007 UTC.
There were 5 messages: 5 from Zope Unit Tests.
Tests passed OK
---
Subject: OK : Zope-2.7 Python-2.3.6 : Linux
From: Zope Unit Tests
Date: Wed Nov 28 20:53:07 EST 2007
Sorry, I dont have the summary stuff automated...
Begin forwarded message:
From: [EMAIL PROTECTED] (Cron Daemon)
Date: November 29, 2007 1:02:48 AM EST
To: [EMAIL PROTECTED]
Subject: Cron [EMAIL PROTECTED] $HOME/bin/releasechecker.py
Products.GenericSetup
OK (1 dependencies)
Tres Seaver wrote:
Please separate out the dependency problem from NIH: in this case,
zope.i18n predates the NIH package by *years* (the i18n support was the
topic of the *first* extra-mural Zope3 sprint, in January of 2002).
Actually no, if I understand Philipp's comment correctly, the NIH
