On Thu, 24 May 2001, Michel Pelletier wrote:
I don't think you are using a globbing vocabulary.
I think I am:
print_info(applic.Catalog(word='scripto*'))
unsplitted ['scripto*']
unl: ['scripto*']
unq: [104623, 'or', 112198, 'or', 151568]
Length: 6
Content: [mybrains instance at 1226d358,
On Mon, May 28, 2001 at 09:37:21AM +0100, Chris Withers wrote:
Well, a nicer interface for changing them is about all I think they
need.
And sort the marshalling stuff out. It would be nice to actually store
blank
dates and numbers (None should be a valid value for both of them ;-)
On Tue, 29 May 2001, Chris Withers wrote:
As for nicer interface... I guess you' ll have to elaborate a
bit ;-)
Well, I think it's manage_changeProperties (nasty name for starters) that
deletes any property you don't include in its arguments, see the interfaces
wiki for details.
Nope,
On Tue, 29 May 2001, Erik Enge wrote:
On Thu, 24 May 2001, Michel Pelletier wrote:
the unsplitted, unl and unq are my debug flags, but you can see what
happens: without parens the '*' has it's desired effect, with, it doesn't.
Got a clue? Is this my bug, or ZCatalog's?
Must be
Hi all,
When using batching in dtml-in, why is 'previous-sequence' only defined at
the first iteration of the current batch? And why is 'next-sequence' only
defined at the last iteration of the current batch?
This behaviour makes it difficult to display a batch like this:
-- begin sample --
If the ZEO server goes down, the the client no longer tries to keep
reconnecting.
This appears to be something to do with the __closed attribute in
zrpc.py.
Is there a page to check the status of bugs in ZEO?
When is the next version due out? and will it be a final 1.0 version?
thanks
-d
On Tue, 29 May 2001, Dyon Balding wrote:
If the ZEO server goes down, the the client no longer tries to keep
reconnecting.
This appears to be something to do with the __closed attribute in
zrpc.py.
Is there a page to check the status of bugs in ZEO?
When is the next version due out?
