Christian Zagrodnick wrote:
now there those wonderful eggs for Zope 3. Apart from the permission
problem we ran into lately there is another one with those eggs:
The dependencies aren't set right.
Apparently nobody every ran the tests of those eggs. This is no wonder.
When developing you
Hey,
Am Donnerstag, den 26.04.2007, 08:14 +0200 schrieb Christian Zagrodnick:
Hi there,
now there those wonderful eggs for Zope 3. Apart from the permission
problem we ran into lately there is another one with those eggs:
The dependencies aren't set right.
Apparently nobody every ran
Previously Christian Theune wrote:
Well. This depends. If you want to enable eggs to work against unstable
releases then you need to do 3.3, because:
3.3 3.4dev 3.4a 3.4(.0)
But =3.4dev should always work, right?
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make
On 26 Apr 2007, at 09:27 , Christian Theune wrote:
Am Donnerstag, den 26.04.2007, 08:40 +0200 schrieb Philipp von
Weitershausen:
Christian Zagrodnick wrote:
now there those wonderful eggs for Zope 3. Apart from the permission
problem we ran into lately there is another one with those eggs:
Hi,
Am Donnerstag, den 26.04.2007, 11:11 +0200 schrieb Philipp von
Weitershausen:
Maybe, but:
3.3 3.3.1 3.4dev etc.
That's right. I missed that one.
:/
--
gocept gmbh co. kg - forsterstraße 29 - 06112 halle/saale - germany
www.gocept.com - [EMAIL PROTECTED] - phone +49 345 122 9889
Hey everybody,
our schedule plans the beta 1 for Zope 3.4 on 3rd of May. That's next
week and it includes a feature freeze for Zope 3.4.
So ladies and gentlemen: get your features wrapped up and merged. :)
Christian
--
gocept gmbh co. kg - forsterstraße 29 - 06112 halle/saale - germany
On Thu, Apr 26, 2007 at 02:53:54PM +0200, Maciej Wisniowski wrote:
Possibly it is enough to change above code to something like:
try:
cursor.execute(query)
except Retry:
raise
except ConflictError:
raise
except Exception, error:
# Just
The giant Zope 3 checkout / shadow project dichotomy is driving me
up the wall. For code that (really) lives in the Zope 3 checkout, it's
difficult to deal with separate releases for the shadow projects since
the version number should really come from the Zope 3 project.
I'm going to move the
The Buildbot has detected a failed build of Zope3 trunk 2.4 Linux zc-buildbot.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 679
Blamelist: fdrake
BUILD FAILED: failed test
sincerely,
-The Buildbot
___
Zope3-dev
Yay!
Is this agreed strategy once on is on the wall?
:)
Christian
Am Donnerstag, den 26.04.2007, 14:00 -0400 schrieb Fred Drake:
The giant Zope 3 checkout / shadow project dichotomy is driving me
up the wall. For code that (really) lives in the Zope 3 checkout, it's
difficult to deal with
On 4/26/07, Fred Drake [EMAIL PROTECTED] wrote:
While I move the code and add externals to the Zope 3 tree, checkouts
will be momentarily broken. I'll send another note when I'm done with
these changes.
Whew! I'm done.
-Fred
--
Fred L. Drake, Jr.fdrake at gmail.com
Chaos is the score
I was reading the discussion on overriding and disabling configurations here
and on grok-dev and I can't help but feel that enabling overrides and trying
to make them smarter or more powerful is the first step in a slippery slope
towards making zcml turing complete.
In grok-dev, Martijn (I
Leonardo Rochael wrote:
If someone else presents me with an alternative zcml configuration for my
package that was useful for their project, I can put this zcml file in my
package for others to include when using it, instead of my default
configuration. If there are parts in common between the
On 4/26/07, Christian Theune [EMAIL PROTECTED] wrote:
Yay!
Is this agreed strategy once on is on the wall?
I'm not sure I understand you question.
I spoke briefly with Jim today about this issue, and he suggests that
for packages that really live within the Zope3 project, they need to
share
14 matches
Mail list logo
