Martijn Faassen wrote:
Jim Fulton wrote:
Martijn Faassen wrote:
[snip]
* the snapshot is probably aging as bugs get discovered and fixed in
your repository. Could you perhaps update the snapshot?
Sure.
Looking forward to the update, though we haven't found bugs yet in our
experiment
Jim Fulton wrote:
Martijn Faassen wrote:
[snip]
* the snapshot is probably aging as bugs get discovered and fixed in
your repository. Could you perhaps update the snapshot?
Sure.
Looking forward to the update, though we haven't found bugs yet in our
experiments so far.
Initial feedback:
Jim Fulton wrote:
Still, of course, for the bits we open source, I guess we are going to
have
to port back to 2.3.
Martijn Faassen wrote:
Well, there's no need if we just say that this bit requires a Zope 3.1
running Python 2.4; why create extra work for ourselves?
+1
Since 3.1 will run o
Jim Fulton wrote:
Martijn Faassen wrote:
[snip]
We have some concerns though:
* the snapshot is probably aging as bugs get discovered and fixed in
your repository. Could you perhaps update the snapshot?
Sure.
Okay, cool!
* it requires Python 2.4.1. Zope 3.1 to my knowledge is targettin
Martijn Faassen wrote:
Hi there,
Since we keep running into snags and frustrations with the zope.app.form
package, we're checking out zc.page and see whether it could help us
any. We're going to try using it today.
Great!
We have some concerns though:
* the snapshot is probably aging as b
Hi there,
Since we keep running into snags and frustrations with the zope.app.form
package, we're checking out zc.page and see whether it could help us
any. We're going to try using it today.
We have some concerns though:
* the snapshot is probably aging as bugs get discovered and fixed in