[Paul Winkler]
> I downloaded the "hidden" 2.6.2b6 release (from
> http://zope.org/Products/Zope/2.6.2b6/Zope/view) and had
> a look in lib/python/ZODB/__init__.py, which gives its
> version as ZODB 3.1.2. Is there any reason it's not ZODB 3.1.3?
Because 3.1.3 hasn't yet been tested with that par
On Tue, Aug 26, 2003 at 08:54:08PM -0400, Tim Peters wrote:
> The changes are delicate, ZODB3 3.1.4 is probably coming soon, and all these
> changes need also to be ported to the ZODB3 HEAD, ZODB3-3_2-branch, ZODB4,
> the experimental ZODB3 3.3 branch, and God only knows how many Zope branches
> at
Go to the Find tab in the ZMI, select "All types", containing ""
Error type: TypeError
Error value: expected a character buffer object
Traceback (innermost last):
Module ZPublisher.Publish, line 49, in publish
Module ZPublisher.mapply, line 32, in mapply
Module ZPublisher.Publish, lin
On Wed, Aug 27, 2003 at 02:54:50PM +1000, Anthony Baxter wrote:
>
>
> Go to the Find tab in the ZMI, select "All types", containing ""
>
> Error type: TypeError
> Error value: expected a character buffer object
Interesting... foo is ok, but gives the TypeError.
The minimal reproducing examp
This error is caused by a conversion of "" into a TaintedString
(because of the <..>) notation.
The tainted string is passed to
ob.PrincipiaSearchSource().find(taintedstring). I think the solution is to
pass str(taintedstring) to find() instead of passing the instance itself.
-aj
--On Mittwoch,
--On Dienstag, 26. August 2003 20:02 -0300 Leonardo Rochael Almeida
<[EMAIL PROTECTED]> wrote:
On Tue, 2003-08-26 at 12:05, Stefan H. Holek wrote:
[...]
Did you rebuild the catalog (-indexes) after the upgrade? New Zope
versions usually come with important BTree fixes ;-).
If by rebuilding you
I've got a couple of ZODBs here that's been gradually upgraded over
time from Zope version to Zope version (I think they were initially
started on Zope 1.x!)
I'm sick of the SearchIndex deprecation warnings, so I've gone and
re-created all of the catalog indexes. This fixed it for the indexes,
Hi!
WRT the Zope 2.7 timeline: Couldn't we just get a new beta that includes
the most critical bug fixes very soon? If 2.7 doesn't get deployed on
"almost production" systems there will not be too much further testing I
guess. And currently most non-experts will not even be able to get a
Zope
2.7.0b2 was released yesterday with both of these bugs fixed. Is that
soon enough? ;-)
On Wed, 2003-08-27 at 05:42, Joachim Werner wrote:
> Hi!
>
> WRT the Zope 2.7 timeline: Couldn't we just get a new beta that includes
> the most critical bug fixes very soon? If 2.7 doesn't get deployed on
>
Chris McDonough wrote:
2.7.0b2 was released yesterday with both of these bugs fixed. Is that
soon enough? ;-)
Yes it is ;-)
Sorry, I didn't check before ...
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
**
On Mon, 2003-08-25 at 23:35, Shane Hathaway wrote:
> On 08/25/2003 05:12 PM, Leonardo Rochael Almeida wrote:
>
> > Let me restate something important, because I forget about it myself
> > sometimes when I'm thinking about this problem: *upgrading to 2.6.1 made
> > the situation definetly worse*. T
Dear friends,
just by chance, I got into the position to try out
Zope 2.7.0 beta 1/2, and since it needs Python 2.2.3
at least, and Stackless 3.0 was just ported to that, I tried
to build Zope with Stackless 3.0.
It works very very well! After a few patches to get the includes
right, here the inst
12 matches
Mail list logo
