[EMAIL PROTECTED] wrote:
> Send Zope-Dev maillist submissions to
> [EMAIL PROTECTED]
>
> To subscribe or unsubscribe via the web, visit
> http://lists.zope.org/mailman/listinfo/zope-dev
> or, via email, send a message with subject or body 'help' to
> [EMAIL PROTECTED]
> You can reach the person managing the list at
> [EMAIL PROTECTED]
>
> (When replying, please edit your Subject line so it is more specific than
> "Re: Contents of Zope-Dev digest...")
>
> Today's Topics:
>
> 1. Re: ZDebug questions (Shane Hathaway)
> 2. Re: TCPWatch How-To (Shane Hathaway)
> 3. Re: Python 1.6, "Expected node type 12, got 312" (Toby Dickenson)
> 4. CalendarTag, year mode image (Ibaņez Palomar Juan David)
>
> --__--__--
>
> Message: 1
> Date: Wed, 06 Sep 2000 10:06:54 -0400
> From: Shane Hathaway <[EMAIL PROTECTED]>
> Organization: Digital Creations, Inc.
> To: Chris Withers <[EMAIL PROTECTED]>
> CC: [EMAIL PROTECTED]
> Subject: [Zope-dev] Re: ZDebug questions
>
> Chris Withers wrote:
> > Using your sample 'bad' DTML, I got the same but the 'Contains name?'
> > column didn't show up :-(
> >
> > Any ideas? (yes, I was tracking down a security exception, and that
> > column may have been really useful ;-)
>
> My guess is you're using Zope 2.1.6. ZDebug doesn't have a way to
> figure out what DTML method is being called in Zope 2.1.6. Strange but
> true. So it shows what it can. The 2.2.x security context stack is
> used to figure it out in 2.2.x. (Which is still a hack. :-/ )
>
> > ...speaking of which, this is related to the following PTK Tracker
> > Issue:
> >
> > http://www.zope.org/Products/PTK/Tracker/110
> >
> > while Andy and I were playing with some stuff, we managed to make ZDebug
> > cry by giving the discussion_thread_view DTML method the 'Member' proxy
> > role and then viewing it from a Member's toolbox (what's the new name
> > for that?) on the left:
> >
> > Error Type: TypeError
> > Error Value: not all arguments converted
>
> Oops! Try this patch (I left out a "%s"):
>
> ===================================================================
> RCS file:
> /cvs-repository/Packages/Products/ZDebug/DebugSecurityPolicy.py,v
> retrieving revision 1.2
> diff -u -r1.2 DebugSecurityPolicy.py
> --- DebugSecurityPolicy.py 2000/09/04 19:23:58 1.2
> +++ DebugSecurityPolicy.py 2000/09/06 14:04:32
> @@ -234,8 +234,8 @@
> info = 'The proxy roles set for ' \
> '%s do not allow access to %s, which is
> ' \
> 'contained in %s. The proxy roles would
> ' \
> - 'have to include one of the following
> roles:' \
> - % (
> + 'have to include one of the following '
> \
> + 'roles: %s' % (
> getCleanPath(eo), cleanupName(name,
> value),
> getCleanPath(container, value),
> tuple(roles))
>
> > Well, thanks for the product, it looks like being _extremely_ useful
> > :-))
>
> Thank you. I know when I was new to Zope this would have been
> tremendously useful. Now it's useful because it should help people
> solve problems on their own rather than having to post to the list.
>
> Shane
>
> --__--__--
>
> Message: 2
> Date: Wed, 06 Sep 2000 10:16:39 -0400
> From: Shane Hathaway <[EMAIL PROTECTED]>
> Organization: Digital Creations, Inc.
> To: Chris Withers <[EMAIL PROTECTED]>
> CC: [EMAIL PROTECTED]
> Subject: Re: [Zope-dev] TCPWatch How-To
>
> Chris Withers wrote:
> >
> > Shane Hathaway wrote:
> > > TCPWatch is a simple Python script that lets you monitor a TCP
> > > connection.
> >
> > ...now this really is extremely useful to me, but not for Zope ;-)
> >
> > However, it did take me a while to wrap my head around it. So here's a
> > little How-To/Example (If anyone thinks I should do this as a How-To on
> > Zope.org, just let me know...)
> >
> > 1. Run up Zope on you local machine on port 8080
> > 2. Set the following off in an appropriate shell:
> >
> > python tcpwatch.py 9080 localhost 8080
>
> I thought about writing a server-starter GUI so that command line
> wouldn't even be necessary. But I decided I like TCPWatch how it is
> already. It's simple and to the point.
>
> > 3. Point a browser at localhost:9080
> >
> > Now, the tkinter window that pops up will show you a list of TCP
> > connections that happen and when they started.
> > If you click on them you get shown all the data which was sent to the
> > server (preceded by '==>') and to the client (preceded by '<==') as well
> > as the times the connections opened and closed (could be very useful for
> > spotting connections that Zope, or anything else, leaves open longer
> > than it should)
> >
> > This is a very cool little tool :-)
>
> It should work with most TCP protocols including smtp, imap, pop-3,
> ssh, ZEO, and even that new multi-stream protocol announced recently.
> It might have troubles with ftp, however.
>
> BTW it uses decimal rather than octal to encode control characters,
> which doesn't follow the "standard" but rather my own preference. :-)
> It should probably be a command-line option.
>
> Shane
>
> --__--__--
>
> Message: 3
> From: Toby Dickenson <[EMAIL PROTECTED]>
> To: "John Hayward-Warburton (Programming account)" <[EMAIL PROTECTED]>
> Cc: [EMAIL PROTECTED]
> Subject: Re: [Zope-dev] Python 1.6, "Expected node type 12, got 312"
> Date: Wed, 06 Sep 2000 15:45:49 +0100
> Reply-To: [EMAIL PROTECTED]
>
> On Wed, 06 Sep 2000 13:48:09 +0000, "John Hayward-Warburton
> (Programming account)" <[EMAIL PROTECTED]> wrote:
>
> >Hi,
> >
> >Clean build of Python 1.6 (downloaded immediately following release
> >notification), clean build of Zope-2.2.1-src;
> >
> >Accessing /manage brings an error in gparse.py, line 293 (ast=sequence2ast)
> >, "Expected node type 12, got 312".
> >
> >Anyone else seeing this? Anyone know what it means?
>
> Yes, there was a bug in pythons parser module. If you are deperate to
> use 1.6 then you will need to compile an old copy of parsermodule.c.
>
> However, I recommend using the current CVS of python 2.0. This (and
> other) bugs have been fixed relative to 1.6
>
> Toby Dickenson
> [EMAIL PROTECTED]
>
> --__--__--
>
> Message: 4
> Subject: [Zope-dev] CalendarTag, year mode image
> To: [EMAIL PROTECTED]
> Date: Wed, 6 Sep 2000 20:32:26 +0200 (DFT)
> Reply-To: <[EMAIL PROTECTED]>
> From: [EMAIL PROTECTED] (Ibaņez Palomar Juan David)
>
> Hi all,
>
> I'd like to release the 0.9.21 version of the CalendarTag soon, but
> first I want to change the year mode image, currently it's an "Y" which
> is not very international, I'd like to see a language neutral image.
>
> The interface of the CalendarTag is based in the Palm Pilot, but the
> Palm III I've here lacks the year mode, I think the Palm VII has.
>
> Could somebody send me an international image for the CalendarTag
> year mode?
>
> Thanks in advance,
> david
>
> --__--__--
>
> _______________________________________________
> Zope-Dev maillist - [EMAIL PROTECTED]
> http://lists.zope.org/mailman/listinfo/zope-dev
>
> (To receive general Zope announcements, see:
> http://lists.zope.org/mailman/listinfo/zope-announce
>
> For non-developer, user-level issues,
> [EMAIL PROTECTED], http://lists.zope.org/mailman/listinfo/zope )
>
> --__--__----
>
> End of Zope-Dev Digest
_______________________________________________
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://lists.zope.org/mailman/listinfo/zope-announce
http://lists.zope.org/mailman/listinfo/zope )