- Zope-Dev - Zope lists

pythonmethods and namespaces.
by Anthony Baxter 29 Jan '00

29 Jan '00

A note in one of Chris' tutorials reminded me of this... the need to whack a self. on the front of every acquired attribute inside a pythonmethod is slowly driving me insane. from what I can see, the issue is that Python itself won't accept anything but a dictionary for the namespace arguments to exec or eval()... right? This means you can't pass a MultiMapping to it... I'm assuming this is so for performance, or is it just because that's how it's always been? Is this likely to be changed? Can anyone else see a way out of this? I thought about adding something to MultiMappings to allow you to generate a proper dictionary from the MM, but that would bite for performance in a big way... Hm, might try hacking the interpreter's source to switch the test from PyDict_Check to PyMapping_Check, see what happens... Anthony

2 1

Re: [Zope-dev] pythonmethods and namespaces.
by Anthony Baxter 29 Jan '00

29 Jan '00

>>> Anthony Baxter wrote > Hm, might try hacking the interpreter's source to switch the test > from PyDict_Check to PyMapping_Check, see what happens... ooo. badness. obviously it's not just a matter of old stuff that hasn't been updated... damn.

1 0

Local ZClasses (Namespace pollution revisited)
by Lalo Martins 29 Jan '00

29 Jan '00

Is there any good reason why I can't just add a ZClass somewhere outside a Product? All we would need is a ``Local ZClass'' product that is really a wrapped ZClass, and then make ObjectManager check in the acquisition path for ZClasses in addition to the ones in the Control Panel (it already does that if I understand ObjectManager.all_meta_types correctly). I can't think of any security problems offered by this, or any other reasons not too. I may even code it myself, but I'd have to learn the old python-based product API, so I'd be more comfortable if someone more used to it and Zope internals gives this a try. []s, |alo +---- -- I am Lalo of deB-org. You will be freed. Resistance is futile. http://www.webcom.com/lalo mailto:lalo@webcom.com pgp key in the web page Debian GNU/Linux --- http://www.debian.org Brazil of Darkness -- http://zope.gf.com.br/BroDar

1 1

status.py out of sync?
by Robin Becker 29 Jan '00

29 Jan '00

The Zope version at least of status.py seems to be out of sync with the recent changes to asyncore.py eg I think that channel_list_producer should contain something like channel_reprs = map ( lambda x: '<' + repr(x[0]) + ',' + repr(x[1])[1:-1] + '>', asyncore.socket_map.items() ) rather than channel_reprs = map ( lambda x: '<' + repr(x[1])[1:-1] + '>', asyncore.socket_map.keys() ) the same is true wherever we refer to the keys() as these seem to be just integers now rather than objects. -- Robin Becker

2 1

z2.py buglet
by Petru Paler 29 Jan '00

29 Jan '00

Hello, While playing around with FastCGI I found a small bug in the startup script. Patch included. -Petru --- z2.py.orig Sat Jan 29 02:19:37 2000 +++ z2.py Sat Jan 29 02:19:55 2000 @@ -549,7 +549,7 @@ fcgiPort = None fcgiPath = None try: - fcgiPort = string.atoi(FCGI_PORT) + fcgiPort = string.atoi(CGI_PORT) except ValueError: fcgiPath = FCGI_PORT zfcgi = FCGIServer(module=MODULE,

1 0

Re: [Zope-dev] ANN: NotMail v0.2.0 alpha Available
by Anthony Baxter 28 Jan '00

28 Jan '00

also have a look at the recently announced worldpilot. Anthony >>> "Jay, Dylan" wrote > I need an interface to a public folder which is a mailing list archive. > NotMail is almost perfect except for > 1) The ImapAdapater has to be changed so that the mailbox is not based on > the Authenticated_User. > 2) The interface needs a read-only mode so that composing/deleting etc are > not options. > > Has anyone done work on this? > > > -----Original Message----- > > From: Ben Leslie [mailto:benno@sesgroup.net] > > Sent: Monday, November 22, 1999 1:14 AM > > To: zope-dev(a)zope.org > > Cc: benno(a)sesgroup.net > > Subject: [Zope-dev] ANN: NotMail v0.2.0 alpha Available > > > > > > Hi everyone, > > > > After much playing around I finally have a NotMail release. > > This is still > > very much alpha but will give those who are game a chance to > > have a look at > > it, find some bugs, make some patches and give me any further > > suggestions > > for the future of NotMail. > > > > My main concern at the moment is to get this release stable > > and before > > working on extra features so this is where my priority is at > > the moment. > > > > I have tested this on UW Imap and Exchange servers. Please > > read the about > > document for more detailed information. > > > > Breifly features are: > > > > View MIME message > > Send attachments > > Manage messages and folders > > Use a readonly addressbook (readwrite soon) > > > > > > There are still some rough edges which I would have liked to > > clean up before > > releasing but I have exams in the follwoing week so I thought > > getting something > > out would be better than getting nothing out. > > > > > > Please send any bug reports to benno(a)sesgroup.net > > > > Cheers, > > > > Ben Leslie > > > > _______________________________________________ > Zope-Dev maillist - Zope-Dev(a)zope.org > 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 ) -- Anthony Baxter <anthony(a)interlink.com.au> It's never too late to have a happy childhood.

1 0

RE: [Zope-dev] ANN: NotMail v0.2.0 alpha Available
by Jay, Dylan 28 Jan '00

28 Jan '00

I need an interface to a public folder which is a mailing list archive. NotMail is almost perfect except for 1) The ImapAdapater has to be changed so that the mailbox is not based on the Authenticated_User. 2) The interface needs a read-only mode so that composing/deleting etc are not options. Has anyone done work on this? > -----Original Message----- > From: Ben Leslie [mailto:benno@sesgroup.net] > Sent: Monday, November 22, 1999 1:14 AM > To: zope-dev(a)zope.org > Cc: benno(a)sesgroup.net > Subject: [Zope-dev] ANN: NotMail v0.2.0 alpha Available > > > Hi everyone, > > After much playing around I finally have a NotMail release. > This is still > very much alpha but will give those who are game a chance to > have a look at > it, find some bugs, make some patches and give me any further > suggestions > for the future of NotMail. > > My main concern at the moment is to get this release stable > and before > working on extra features so this is where my priority is at > the moment. > > I have tested this on UW Imap and Exchange servers. Please > read the about > document for more detailed information. > > Breifly features are: > > View MIME message > Send attachments > Manage messages and folders > Use a readonly addressbook (readwrite soon) > > > There are still some rough edges which I would have liked to > clean up before > releasing but I have exams in the follwoing week so I thought > getting something > out would be better than getting nothing out. > > > Please send any bug reports to benno(a)sesgroup.net > > Cheers, > > Ben Leslie >

1 0

Re: [Zope-dev] Problem with ftp to zserver!
by Victor.Zhai＠ogilvy.com 27 Jan '00

27 Jan '00

Dear: Actually , I used Zserver as a Virtual Host. Before I installed SiteAcces and Siterules which including in SiteAccess. Everything is OK! But after I have used my server as a VirtualHost. Then that problem accoured. So I have no method to resolv it. Do you have some other ideas? Thanks a lot! Victor zhai. "WorldSecure Server <ogilvy.com>" made the following annotations on 01/27/00 07:29:36 ------------------------------------------------------------------------------ Privileged/Confidential Information may be contained in this message. If you are not the addressee indicated in this message (or responsible for delivery of the message to such person), you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email. Please advise immediately if you or your employer does not consent to email for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of the Ogilvy Group shall be understood as neither given nor endorsed by it. ==============================================================================

1 0

XMLDocument, a bug with the fix
by al028823＠alumail.uji.es 27 Jan '00

27 Jan '00

Hi, (first, excuse my english, please) I downloaded from http://www.zope.org/Products/XMLDocument the latest two releases and found one differnet bug in each of them. * 1.0a3 - the test code, entry = self.getOwnerDocument().createElement('entry') return entry.getParentNode() - the problem, getParentNode should return None but it doesn't (it returns self or something else, I don't remember) * 1.0a4 - the test code, entry = self.getOwnerDocument().createElement('entry') return entry.getOwnerDocument() == self.getOwnerDocument() - the problem, self.getOwnerDocument() and entry.getOwnerDocument() are different, they should be the same object. Both errors make other methods to fail, such as appendChild. I've wrote about the two releases because I'm not sure whether the 1.0a4 really is the 1.0a4 or not (1.0a3 is 1.0a4 and vice versa?). The CHANGES.txt file in the Zope site makes me to think the last. Anyway, I've solved the problem (I think), the diff with the 1.0a4 release is: 290c290,293 < return self.ownerDocument --- > try: > return self.ownerDocument.aq_self > except AttributeError: > return None I'm not sure if this is the right solution but I think it's a good one. Hope to be helpful, David PS: the Howto "http://www.zope.org/Members/htrd/howto/aq_order" helped me to diagnose the problem, thanks to Toby Dickenson.

1 0

Re: [Zope-dev] Authentication Patch
by Anthony Baxter 27 Jan '00

27 Jan '00

>>> Evan Simpson wrote > I got tired of dealing with the weird mechanics cookie-based logins have > to deal with, where standard_html_error and tracebacks intrude on login > intercepts. I came up with the following minor change, which works > great for me, and might make GenericUserFolder's job easier, too. > In ZPublisher/HTTPRequest.py (or SiteAccess/ChangeBehaviors.py, if you minor glitchlet: it's in BaseRequest.py. > use SiteAccess), change the lines: > > if user is None and roles != UNSPECIFIED_ROLES: > response.unauthorized() > to: > if user is None and roles != UNSPECIFIED_ROLES: > object = response.unauthorized > Under normal circumstances, this has no effect, since > 'response.unauthorized' will be called as soon as it is returned and > will raise its exception as usual. Now however, we add a twist; When > the cookie-based authenticator fails, it replaces > 'response.unauthorized' with its 'login' document. If no higher-level > authentication succeeds, the 'login' document is rendered normally. > Since 'response' is re-created with each request, this modification has > no effect beyond the current request. I'm trying to puzzle through the access control code - right now, if a login validate method fails, they typically do something like raise 'LoginRequired', self.docLogin(self, request) should they just, in this case, return back None, and let the machinery deal with it? Hm, in that case, wouldn't that then just recurse back through the parent folders looking for additional access controls? So if you had /a/acl_users and /a/b/acl_users, and both used something like the above, a request to /a/b/foo would get the /a/acl_users' docLogin page... ? Anthony

3 2