[Zope-dev] Re: TALES idea: tuple unpacking

2003-07-31 Thread Chris Withers
Evan Simpson wrote: OK, I've checked in a sample implementation on evan-pathprefix-branch. It allows for registering prefixes with: from Products.PageTemplates.PathPrefixes import registerSubPathPrefix registerSubPathPrefix('call', call_compiler, call_handler) How would this interact with the

Re: [Zope-dev] Re: TALES idea: tuple unpacking

2003-07-31 Thread Chris Withers
Shane Hathaway wrote: Guys, that line of thinking is a distraction. ZPT authors ought to learn Python. I dunno about that, I would really like to see simple ZPT require no understanding of python... language again. If DTML used TALES expressions, it would be just as clean as ZPT. I actually

Re: [Zope-dev] Re: TALES idea: tuple unpacking

2003-07-31 Thread Chris Withers
Jim Penny wrote: Ahh, OK. The damned here/context semantic trap again. It is too late to revisit, it is a done deed, it was a really good idea to call the concept context, self, and here, depending on what kind of object you are using, etc. But here suggests container more strongly to my mind

Re: [Zope-dev] more Zope2.6 fun: ZEO client death.

2003-07-31 Thread Andrew Sydelko
On Thu, 31 Jul 2003 12:57am, Anthony Baxter wrote: Anthony Baxter wrote Updating it by hand to ZEO2 hasn't made all good and happy, though - the ZEO/start.py includes import ThreadedAsync.LoopCallback at the top of the file, but the sys.path magic that makes this available is inside the

Re: [Zope-dev] more Zope2.6 fun: ZEO client death.

2003-07-31 Thread Shane Hathaway
Andrew Sydelko wrote: I've seen no problems with imports. And if anything, the cache implementation in the ZODB3.1.2 version of ZEO made a remarkable performance difference. ... as compared with earlier versions or later versions? I hope it's getting faster, not slower. :-) Shane

Re: [Zope-dev] more Zope2.6 fun: ZEO client death.

2003-07-31 Thread Andrew Sydelko
On Thu, 31 Jul 2003 8:49am, Shane Hathaway wrote: Andrew Sydelko wrote: I've seen no problems with imports. And if anything, the cache implementation in the ZODB3.1.2 version of ZEO made a remarkable performance difference. ... as compared with earlier versions or later versions? I hope it's

Re: [Zope-dev] more Zope2.6 fun: ZEO client death.

2003-07-31 Thread Shane Hathaway
Andrew Sydelko wrote: It's faster especially compared to ZEO 1.x, but also compared to earlier versions of ZEO 2.x/ZEO from ZODB3.1.x. At one point, changes were made to the initial cache invalidation check that caused ZEO startup time to become significantly faster. Before this change the ZEO

[Zope-dev] NOTICE: Final content migration and transition to new zope.org begins today!

2003-07-31 Thread Brian Lloyd
Hi all - sorry for the wide cross-posting, but I want to be sure that the word gets out. Starting today, we will be starting the transition of zope.org to a new look and a new platform. We plan to do the final content migration later today, so if you are a frequent content contributor to

ZEO caching, was Re: [Zope-dev] more Zope2.6 fun: ZEO client death.

2003-07-31 Thread Paul Winkler
On Thu, Jul 31, 2003 at 10:06:08AM -0400, Shane Hathaway wrote: Jim and PythonLabs put a bunch of work into optimizing ZEO cache validation earlier this year, and now it's quite speedy. Which reminds me... Is it expected that ZEO can take quite a while to show a new object on all clients?

Re: ZEO caching, was Re: [Zope-dev] more Zope2.6 fun: ZEO clientdeath.

2003-07-31 Thread Shane Hathaway
Paul Winkler wrote: Which reminds me... Is it expected that ZEO can take quite a while to show a new object on all clients? With zope 2.6.2b3, ZEO 2.0.2, I can reliably get this behavior: 1) browser 1 looking at foofolder on client 1 adds a new object /foofolder/bar. 2) browser 2 on client 2

[Zope-dev] A First Look at Zope3

2003-07-31 Thread Chris Gray
I checked out Zope3 from CVS yesterday and had a go at it for the first time. Granted that it is a work in progress, I did have a few comments from a user's (rather than a developer's) perspective. The API exposed to DTML and ZPT seems very sparse (compared to Zope2) at this stage. Is this the

Re: ZEO caching, was Re: [Zope-dev] more Zope2.6 fun: ZEO client death.

2003-07-31 Thread Paul Winkler
On Thu, Jul 31, 2003 at 12:13:40PM -0400, Shane Hathaway wrote: This is clearly problematic. At what point is client 2 supposed to see the new object?? Immediately. You are experiencing a bug. ;-) OK... is this a known bug? Is it a bug in ZEO or Zope or what? -- Paul Winkler

Re: [Zope-dev] A First Look at Zope3

2003-07-31 Thread Fred L. Drake, Jr.
Chris Gray writes: I checked out Zope3 from CVS yesterday and had a go at it for the first time. Granted that it is a work in progress, I did have a few comments from a user's (rather than a developer's) perspective. Thanks for taking the time to look at Zope 3! We definately appreciate

Re: ZEO caching, was Re: [Zope-dev] more Zope2.6 fun: ZEO clientdeath.

2003-07-31 Thread Shane Hathaway
Paul Winkler wrote: On Thu, Jul 31, 2003 at 12:13:40PM -0400, Shane Hathaway wrote: This is clearly problematic. At what point is client 2 supposed to see the new object?? Immediately. You are experiencing a bug. ;-) OK... is this a known bug? Is it a bug in ZEO or Zope or what? I've seen

[Zope-dev] Re: TALES idea: tuple unpacking

2003-07-31 Thread Evan Simpson
Chris Withers wrote: How would this interact with the Adapters stuff implements in Zope 3's TALES? It wouldn't -- this is a Zope 2 implementation. OK, I know what you mean, but I don't know enough about the Zope 3 implementation to make an informed response. Wouldn't Zope 2's lack of the

Re: [Zope-dev] A First Look at Zope3

2003-07-31 Thread Chris Gray
On Thu, 31 Jul 2003, Fred L. Drake, Jr. wrote: Chris Gray writes: but I see one problems. The text input appears at the top of the list and the button to commit the change is at the bottom of the list. This will become more inconvenient as a