Hello Michael,
After some simple thinking there are some fears that this wrecks other
basic fields validation.
Something like the field is required, has a default value but is
omitted on input. What will be the result? Accepting the default value
instead of raising an error is definitely a
Hello,
Following just happened. The project has KGS 3.4 versions as a base,
locally I wanted to override lxml to = 2.1.1.
[...snip...]
extends = http://download.zope.org/zope3.4/3.4.0/versions.cfg
versions = versions
[versions]
lxml = 2.1.1
[...snip...]
The bin/buildout -v output was:
Hello Malthe,
Tiny problem is that the doctests seem to have the attributes in
lxml-sane order. That means just by removing lxml output-sanitization
even zpt output does not match the doctest.
Also, lxml is used to do some xpath queries.
Saturday, May 23, 2009, 10:23:16 AM, you wrote:
MB
Adam GROSZER, on 2009-05-24:
Hello,
Following just happened. The project has KGS 3.4 versions as a base,
locally I wanted to override lxml to = 2.1.1.
[...snip...]
extends = http://download.zope.org/zope3.4/3.4.0/versions.cfg
versions = versions
[versions]
lxml = 2.1.1
Only assignment
Summary of messages to the zope-tests list.
Period Sat May 23 12:00:00 2009 UTC to Sun May 24 12:00:00 2009 UTC.
There were 8 messages: 8 from Zope Tests.
Tests passed OK
---
Subject: OK : Zope-2.10 Python-2.4.6 : Linux
From: Zope Tests
Date: Sat May 23 20:47:53 EDT 2009
URL:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
Please exclude the mass-email, most of you will receive this more than
once, we're hoping to catch any current contributor whose email
address on zope.org is not current. Anyone who has svn.zope.org
checkin privileges and has not
Maurits van Rees wrote:
Adam GROSZER, on 2009-05-24:
Hello,
Following just happened. The project has KGS 3.4 versions as a base,
locally I wanted to override lxml to = 2.1.1.
[...snip...]
extends = http://download.zope.org/zope3.4/3.4.0/versions.cfg
versions = versions
[versions]
lxml
Hey,
Shane Hathaway wrote:
Done. I look forward to seeing the changes in the dependency graph.
Great, thanks!
The only cycle left in the zope.app.publisher graph is between
zope.container and zope.filerepresentation.
The graph now contains 42 notes, so we got rid of 3 more dependencies.
Hi there,
Shane Hathaway wrote:
[snip]
Summarizing:
zope.app.publisher - zope.view
zope.app.publication - zope.publicationregistry
zope.app.http - zope.rest
I'm not sure about zope.rest; there's already a z3c.rest which likely
does something quite different, and I think a zope.rest
