Hello Malthe,
The problem that I see here with lxml is that it is used for output
checking. Even worse z3c.form requires at least 2.1.1 of lxml, where KGS
3.4 has lxml nailed at 1.3.6.
This burpes already on buildout.
Now even if I would ignore this requirement for testing, (and testing)
how
Martijn Faassen wrote:
So, the only dependency cycles left in zope.app.publisher are these:
zope.app.publisher -- zope.app.publication -- zope.app.http
I fixed those tonight. On the trunk, there are no longer any
dependencies between zope.app.publisher, zope.app.publication, and
Shane Hathaway wrote:
Martijn Faassen wrote:
So, the only dependency cycles left in zope.app.publisher are these:
zope.app.publisher -- zope.app.publication -- zope.app.http
I fixed those tonight. On the trunk, there are no longer any
dependencies between zope.app.publisher,
2009/5/23 Adam GROSZER agros...@gmail.com:
The problem that I see here with lxml is that it is used for output
checking. Even worse z3c.form requires at least 2.1.1 of lxml, where KGS
3.4 has lxml nailed at 1.3.6.
It might be possible to shed this testing dependency; ``lxml`` is used
because
Summary of messages to the zope-tests list.
Period Fri May 22 12:00:00 2009 UTC to Sat May 23 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: Fri May 22 20:53:08 EDT 2009
URL:
Shane Hathaway wrote:
Martijn Faassen wrote:
So, the only dependency cycles left in zope.app.publisher are these:
zope.app.publisher -- zope.app.publication -- zope.app.http
I fixed those tonight. On the trunk, there are no longer any
dependencies between zope.app.publisher,
Hey Shane,
Shane Hathaway wrote:
Shane Hathaway wrote:
Martijn Faassen wrote:
So, the only dependency cycles left in zope.app.publisher are these:
zope.app.publisher -- zope.app.publication -- zope.app.http
I fixed those tonight. On the trunk, there are no longer any
dependencies between
Martijn Faassen wrote:
Shane Hathaway wrote:
- I used zope.deferred to deprecate things I moved from
zope.app.publication, zope.app.publisher, and zope.app.http. Are there
any objections to using zope.deferred in those packages?
No objection, but what's the reason to use zope.deferred
On Sat, May 23, 2009 at 08:59:34PM +0200, Martijn Faassen wrote:
What about simply calling it zope.view? (I don't like the plural in
package names either generally)
FWIW at some point I decided that singular is appropriate when a package
defines a concept, and plural is appropriate when a
Shane Hathaway wrote:
Martijn Faassen wrote:
Shane Hathaway wrote:
In all, I changed 6 packages. Should I release them now, or should I
look for other dependencies we might clean up at the same time?
I'm +1 on releasing now. (and thanks for making them feature releases)
Getting these
Martijn Faassen wrote:
Shane Hathaway wrote:
- zope.app.publisher: A library of ZCML directives for configuring
views. Also provides generic view classes. A better name for this
package might be zope.basicviews. A lot of packages depend on this.
I'm not sure 'basic' needs to be in
Marius Gedminas wrote:
On Sat, May 23, 2009 at 08:59:34PM +0200, Martijn Faassen wrote:
What about simply calling it zope.view? (I don't like the plural in
package names either generally)
FWIW at some point I decided that singular is appropriate when a package
defines a concept, and plural
12 matches
Mail list logo
