On 2/18/07, Roger Ineichen <[EMAIL PROTECTED]> wrote:
Since the newest Zope3 trunk checkout,
some tests are not running. This tests are based
on a custom test layer.
Exception raised:
Traceback (most recent call last):
File "D:\trunk\Zope3\src\zope\testing\doctest.py", line 1361, in __
Hi,
How we will be installing Zope 3.4, can I do it like this:
easy_install zope3
If this is the case, the zope3 package will contain few files/packages
which are not separately eggified?
What are the minimum files required in this zope3 package?
I assume some scrips,docs etc. will be there.
I hope others will comment, but I'll make some initial high-level
observations:
- As I've said many times before, Zope 3 is both a library (really a
collection
of libraries) and an application.
- For the purpose of using Zope 3 as a library, there is no need for
a Zope 3 egg.
There is
(Replying to myself!)
Baiju M wrote:
There are few tests which are located outside any particular package.
zope.app.ftests and zope.app.tests
Either we can distribute it with our huge zope.app egg or move it to some
other places. What about moving those tests to zope.app.zcmlfiles ?
When I lo
Baiju M wrote:
(Replying to myself!)
Baiju M wrote:
There are few tests which are located outside any particular package.
zope.app.ftests and zope.app.tests
Either we can distribute it with our huge zope.app egg or move it to
some
other places. What about moving those tests to zope.app.zcml
I'm testing buildout, and one thing I want is to have several cfgs,
one for development, one for staging and one for production. Now,
calling one of the configurations buildout.cfg would make it the
default. That means that if you just run bin/bildout, it will try to
install that configuration. Th
Hi,
we're hiring. Just in case someone isn't reading the German lists or is
interested to work in Germany, gocept is hiring.
The German job description is here:
https://members.zope.de/Members/ctheune/softwareentwickler-m-w/
(Note that the *ideal* candidate speaks German, but we might like you
Hi,
here's the pattern that we use:
- create a directory 'profiles/' in your buildout
- create a file 'profiles/base.cfg' that describes all parts and their
default configurations
- create a file 'profiles/dev.cfg' that has the development variation
and uses '[buildout] extends=base.cfg'
Then we
On 2/19/07, Christian Theune <[EMAIL PROTECTED]> wrote:
Hi,
here's the pattern that we use:
- create a directory 'profiles/' in your buildout
- create a file 'profiles/base.cfg' that describes all parts and their
default configurations
- create a file 'profiles/dev.cfg' that has the development
