June 2000 - Zope-Dev

Re: [Zope-dev] Logging for ZScheduler?
by Tres Seaver 18 Jun '00

18 Jun '00

"Phillip J. Eby" <pje(a)telecommunity.com> > > At 01:58 PM 6/15/00 +1000, Stuart 'Zen' Bishop wrote: > > > > Its not a problem with ZScheduler, it a problem that no one has > > written a plug-in logging system that is good enough for what > > you are trying to do. The existing zLOG API is fine (well - it > > could be better), but just needs someone to write the relevant > > modules. Hmm... I think I'll > > add a section to the Interfaces Wiki... > > Hm... this could work well with Observer->Observable, too. > Imagine firing ObservableEvents, and subscribing a "Log" object > to them... Ayup, logging is one of the classic instances of that pattern. The problem with using Observer for logging, especially in a fine-grained way, is that the dependency arrows point the "wrong way" -- the logger object needs to register as an Observer of many Subjects, but has no good way to find them all. The typical solution is to add an intermediate observer to all the containers, who watches the add and remove operations, and then either notifies the logger of new subscriptions it should perform, or performs them on behalf of the logger. Tres. -- =========================================================== Tres Seaver tseaver(a)digicool.com Digital Creations "Zope Dealers" http://www.zope.org

1 0

(ZPatterns 0.4.0a1) Getting Customizers to recognize DataSkin descendants descendants
by Itamar Shtull-Trauring 18 Jun '00

18 Jun '00

I want to customize (with a Customizer) a class I made. It inherits from DataSkin. However, it's meta_type doesn't show in the Customizer's manage_typesForm page, so I can't tell the Customizer to use this class unless I call manage_setTypes manually (which works.) So how come my class won't show up - DataSkin and RackMountable both show up, and my Product isn't broken - I can add instances of my DataSkin descendant. -- Itamar S.T. itamar(a)maxnm.com Fingerprint = D365 7BE8 B81E 2B18 6534 025E D0E7 92DB E441 411C

2 1

Changing meta type of a ZClass (bug?)
by Alexander Limi 18 Jun '00

18 Jun '00

Hi, Just a quickie here: I was learning a mate of mine how to use Zope over IRC, and he created a ZClass to try out some stuff. Alas, he forgot to provide a meta type, and the ZClass did not show up in the "Add" list. This reminded me of a long standing "mis-feature" of Zope - changing the name of the metatype of an object does not work the way I expect it to. A real example was when I tried to alter the meta type of a class from "artist" to "Artist" to make it more consistent with the rest of my setup. ZCatalog and the "Add"-dialog still contained the all-lowercase version, with the consequence that I could not index any of the objects in the catalog anymore. So I had to change it back. Shouldn't this be fixed? Or is it like this for a reason? And tell me if this is unnfitting for the dev-list - I thought it more as a development question than a standard "I cannot do this"-question :) -- Alexander Limi alexander(a)limi.net

1 0

User DB, GUF, et al broken under 2.1.7?
by jiva＠devware.com 18 Jun '00

18 Jun '00

Is it just me or are about all the third party ACL folders broken in 2.1.7? I have tired User DB, and GUF and can't seem to get either to work. I was one of the bright fellows who updated to 2.1.7 immediately when it became available from 2.1.4, and now all my user folders are broken and I (like an idiot) did not make a backup before upgrading. (Well I did, but I actually have done some work on the site since then, and it seems the Data.fs is not compatable if I take it from 2.1.7 and try to use it in 2.1.4. ARGH... Help! -- Did I say I was a sardine? Or a bus???

1 0

Re: [Zope-dev] 0.4.0 prerelease snapshot (was zpatterns-0.4 ?)
by Phillip J. Eby 17 Jun '00

17 Jun '00

By popular demand, I am releasing a development snapshot of version 0.4.0. Please see the main ZPatterns download page. This is EXTREMELY ALPHA and includes a fair amount of code that just got written or debugged today. Actually, most of the stuff I wrote today got exercised pretty well. I'm more concerned about whether I broke anything that worked before in the process, as I haven't come up a way to regression test this thing except manually. :( Anyway... there are quite a few undone bits as yet, but the main things are there. DataSkins, and Folders w/Customizer support, for example. Ty's ExprGetter AttributeProvider, which is pretty cool, and my updates to it to make it even cooler. :) Some things that may not work right... DataSkins need to have their _objectAdding()/_objectDeleting() methods called from manage_afterAdd/manage_beforeDelete, and if you subclass ObjectManager or CatalogAware or anything else with custom hooks for these methods, you may break add/delete events, which are required for some things to work. This might not affect you in the prerelease, because not much is wired to the events yet. But they may break in the final release. In general, you should assume that this release is dangerous. On various occasions today, it has caused Zope to dump core. In each case, I found and fixed the problems, which had to do with the new deep acquisitional/transactional/computedattribute magic for DataSkins. There is no guarantee, however, that I have fixed all such bugs. I reserve the right to make incompatible changes between this release and the final 0.4.0, that would require you to delete all prerelease-based objects and start over. (I am doing my best to maintain transparent upgradability from 0.3.0, however. But I won't be putting in data upgrade code for interim releases.) Last, but not least, the docs are even worse than usual for my releases, and some of the newer objects have ugly, missing, or confusing interim icons. So all in all, use at your own risk. At 04:06 PM 6/7/00 +0300, Itamar Shtull-Trauring wrote: >"Phillip J. Eby" wrote: > >> I'm shooting for release by the end of next week. Search plugins have not >> been finished yet, but in any case they will NOT work with prior versions; >> there is no place to plug them in, nor will any of the old code call them. :) > >Could you maybe release a preliminary version in the beginnng of the week, >even if it's not finished? I'd like to start designing a Product using the >events-sending interfaces, and it'd be a real help if I could know even >approximately what the interfaces looked like. Not that I'm rushing you or >anything :) Have a look at Agents.py in the new release. To have an object that receives events, subclass the Agent class, and override: def _getMementoFor(self,client): def _objectChanged(self,client,memento): def _objectDeleted(self,client,memento): def _objectAdded(self,client): as appropriate. getMemento should return a snapshot of any data you want passed into the methods that take a "memento" parameter. Make sure your memento contains only "immutables all the way down", since the object you're watching ("client")might change anything that's mutable. By the way, the final release of 0.4.0 should (time permitting) include an "ExprNotifier" which can automatically translate the above events into calls to arbitrary DTML expressions, including handling memento generation for you by saving specified expressions executed against the object before it changes.

3 4

2.2 or Membership Component alpha problem, and suggestions for the latter latter
by Bill Anderson 17 Jun '00

17 Jun '00

(sorry if this is a duplicate, it didn't seem to go the first time...) OK, first, a tip I learned earlier today (and couldn't find the answer for): Problem: If you try to add a membership system to your root folder, and it has an acl_users folder, you will not succeed in adding it, ecause it will complain about mismatched passwords (or at least it did for me). Solution: Delete the acl_users fodler first. Now, onto the current issue. I have some DTML that adds ZClass instances. The Member user has the appropriate roles, yet is refused. The forbidden page tells me I need Manager role. Now, why is this? In particular, I am using the MeetingManagement product. It works fine in 2.1.6. I think it is related to the security changes in 2.2. Problem is, even adding proxy roles for the methods in the chain changes nothing. Here is the big kicker. If I sign up as an anonymous(!) user, it works as it is supposed to. It only barfs when I am logged in as a 'Member'...Help? Now, a suggestion for Kevin: It would be nice if there was user management for the Membership component's default setup. I am sure you're thinking about it, but thought I'd let you know it is needed :) Specifically, there should be some way that the site manager can modify theroles of the users, reset passwords, and DELETE them as needed. Any ideas/work being done for this? Otherwise, the MembershipZ component is working flawlessly!

1 0

2.2 beta and borked ZopeTime
by Bill Anderson 16 Jun '00

16 Jun '00

Found a bug in the ne ZopeTime: <dtml-var ZopeTime> Returns the correct info. However: <p> Today is <dtml-var ZopeTime fmt="%A %d/%m/%Y - %H:%M"> tells me everything correct, only it thinks it is Monday, when today is actually Friday. -- Bill Anderson Linux/Unix Administrator, Security Analyst ESBU (ARC) bill_anderson(a)boi.hp.com My opinions are just that; _my_ opinions.

1 0

Distutils scripts for ZODB
by A.M. Kuchling 16 Jun '00

16 Jun '00

Here are 3 short setup.py scripts for various bits of Zope. Two of them don't fully work yet due to bugs in the current CVS of distutils; the problems have been reported and should be fixed in a day or two. 'XXX' marks fields that I didn't fill in. First, lib/python/setup.py; currently this just installs zLOG.py: # Setup file for zLOG from distutils.core import setup setup(name = "zLOG", version = "XXX", description = "XXX", author = "Jim Fulton", author_email = "XXX", url = "XXX", py_modules = ['zLOG'] ) Second, lib/Components/ExtensionClass. I'm not sure which of the modules actually need to be installed. ExtensionClass.h gets installed in the wrong place (/usr/include/python/1.6 instead of .../python1.6); this is one of the reported bugs. # Setup file for ExtensionClass from distutils.core import setup from distutils.extension import Extension # XXX which of these should really be installed? ExtensionClass = Extension(name = 'ExtensionClass', sources= ['ExtensionClass.c'] ) Acquisition = Extension(name = 'Acquisition', sources = ['Acquisition.c']) MethodObject = Extension(name = 'MethodObject', sources = ['MethodObject.c']) Missing = Extension(name = 'Missing', sources=['Missing.c'] ) MultiMapping = Extension(name = 'MultiMapping', sources=['MultiMapping.c'] ) ThreadLock = Extension(name = 'ThreadLock', sources=['ThreadLock.c'] ) setup(name = "ExtensionClass", version = "XXX", description = "XXX", author = "Jim Fulton", author_email = "XXX", url = "XXX", ext_modules = [ExtensionClass, Acquisition, MethodObject, Missing, MultiMapping, ThreadLock], headers = ["ExtensionClass.h"] ) Finally, lib/python/ZODB/setup.py. The define_macros setting doesn't work either, the second bug. # Setup file for ZODB package from distutils.core import setup from distutils.extension import Extension # XXX which of these should really be installed? cPersistence = Extension(name = 'ZODB.cPersistence', include_dirs=['../ExtensionClass/'], sources= ['cPersistence.c'] ) cPickleCache = Extension(name = 'ZODB.cPickleCache', include_dirs=['../ExtensionClass/'], sources= ['cPickleCache.c'] ) TimeStamp = Extension(name = 'ZODB.TimeStamp', # XXX define_macros doesn't currently work define_macros = ['USE_EXTENSION_CLASS'], include_dirs=['../ExtensionClass/'], sources= ['TimeStamp.c'] ) coptimizations = Extension(name = 'ZODB.coptimizations', include_dirs=['../ExtensionClass/'], sources= ['coptimizations.c'] ) winlock = Extension(name = 'ZODB.winlock', sources = ['winlock.c']) setup(name = "ZODB", version = "XXX", description = "XXX", author = "Jim Fulton", author_email = "XXX", url = "XXX", packages=['ZODB'], package_dir = {'ZODB':'.'}, ext_modules = [cPersistence, cPickleCache, TimeStamp, coptimizations, winlock] ) --amk

3 2

Re: [Zope-dev] Zope ...2.1.7 update - patch for EMarket 0.1.03
by Adam Karpierz 16 Jun '00

16 Jun '00

Patch for EMarket v.0.1.3 product for Zope 2.1.7 begin 666 EMarket.py.patch M*BHJ($5-87)K970N<'DN;W)I9PE4:'4@2G5N(# Q(# P.C V.C Q(#(P,# * M+2TM($5-87)K970N<'D)1G)I($IU;B Q-B P,CHU-CHS-2 R,# P"BHJ*BHJ M*BHJ*BHJ*BHJ*@HJ*BH@,C4X+#(V-2 J*BHJ"B @(" @(&YE=TUA:6Y&+G1R M86YS86-T:6]N1F]L9&5R(#T@;F5W5')A;G-&"B @(" @( H@(" @("!0<F]D M=6-T<RY-86EL2&]S="Y-86EL2&]S="YA9&0H;F5W36%I;D8L("=E36%R:V5T M36%I;&AO<W0G+ HA(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @ M(" @<VUT<%]H;W-T(#T@<VUT<%]H;W-T+ HA(" @(" @(" @(" @(" @(" @ M(" @(" @(" @(" @(" @(" @;&]C86QH;W-T(#T@;&]C86QH;W-T*0H@( H@ M(" @("!T:&5-86EL2&]S=" ](&=E=&%T='(H;F5W36%I;D8L)V5-87)K971- M86EL:&]S="<I(" C(R,@5$]$3RXN+B!C:&%N9V4@9&]C=6UE;G1S('1H870@ M<V5N9"!M86EL('1O(&)E('!R;WAI97,@9F]R($UA;F%G97(*(" *+2TM(#(U M."PR-C0@+2TM+0H@(" @("!N97=-86EN1BYT<F%N<V%C=&EO;D9O;&1E<B ] M(&YE=U1R86YS1@H@(" @(" *(" @(" @4')O9'5C=',N36%I;$AO<W0N36%I M;$AO<W0N861D*&YE=TUA:6Y&+" G94UA<FME=$UA:6QH;W-T)RP*(2 @(" @ M(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @('-M='!?:&]S=" ]('-M M='!?:&]S="D*(" *(" @(" @=&AE36%I;$AO<W0@/2!G971A='1R*&YE=TUA M:6Y&+"=E36%R:V5T36%I;&AO<W0G*2 @(R,C(%1/1$\N+BX@8VAA;F=E(&1O M8W5M96YT<R!T:&%T('-E;F0@;6%I;"!T;R!B92!P<F]X:65S(&9O<B!-86YA '9V5R"B @"@`` ` end

2 1

Unpickleable Error
by Nick Garcia 16 Jun '00

16 Jun '00

So, I'm getting this error when trying to use one of my Products under Zope 2.2b1: Error Type: UnpickleableError Error Value: Cannot pickle <type 'StringO'> objects What exactly is a StringO object, and why can't it be pickled/unpickled? It worked fine under 2.1, so I'm assuming there have been changes to the pickling routines that haven't been completely cleaned up yet? -- Nick Garcia | ngarcia(a)codeit.com CodeIt Computing | http://codeit.com

1 0