- Zope-Dev - Zope lists

More on the Absent id bug
by Jason Spisak 06 Jan '00

06 Jan '00

More findings on the extra backslash. The url stored in the Catalog when I ask for: <dtml-in "Catalog(id=id)"> <dtml-var url> </dtml-in> is correct. It has no leading slash. However under the 'Cataloged Items' tab as well as when I use getpath() I get a leading slash. This screws up unindex_object because it's looking for an object without the forward slash, and I guess it doesn't see one. Michel, is this fixed in 2.1.2? Is it related to having old Catalaog Aware ZClasses? It's really drving me crazy. An app that was working yeasterday, is pretty useless today. :( All my best, -- Jason Spisak webmaster(a)hiretechs.com

1 0

RE: [Zope-dev] multiple ZODB files?
by Michel Pelletier 06 Jan '00

06 Jan '00

> -----Original Message----- > From: Anthony Baxter [mailto:anthony@interlink.com.au] > Sent: Thursday, January 06, 2000 2:27 AM > To: zope-dev(a)zope.org > Subject: [Zope-dev] multiple ZODB files? > > > Is it possible to set up a site such that as well as the single > Data.fs file, a seperate folder (say, /foo) is loaded from a different > ZODB file? In particular, changes to stuff inside /foo should > be written > to the foo ZODB file. Not yet, we have not fully thought about this problem of multiple databases, but ZODB was architected to be multi-DB aware. -Michel

3 2

RFC: Possible change to PythonMethod restrictions
by Evan Simpson 06 Jan '00

06 Jan '00

I've been thinking about submitting some changes to PythonMethods, but now that they're going to be part of Zope, I thought I should put the idea out for discussion first. A minor annoying side-effect of the safety restrictions on PMs is that you can't manipulate local data structures directly. For example, if you create a dictionary or list to hold some objects, you can't scan through and delete items from it. You have to build a new list or dict instead. I think it should be possible to safely allow some normally illegal operations as long as Zope can verify that you created the target object. When a PythonMethod compiles its code, the following steps would take place: 1. A dict flagging local names as 'safe' or 'unsafe' (0 or 1) is created, defaulting to 'safe' for all. 2. When a local variable is set to a list or dict literal (BUILD_LIST or BUILD_MAP sequence followed by STORE_FAST) the variable name is left alone. 3. When a local variable is set to anything else the name is flagged 'unsafe'. 4. Index and slice assignment and deletion are allowed on a bare name if the name is still flagged 'safe' at the end. This isn't by any means smart enough to allow all 'safe' cases to be allowed, but it will never let you perform an 'unsafe' operation. It provides just enough leeway for you to create local lists and dicts and do whatever you want to them, so long as you keep them in a local variable. The allowed operations in (4) are, more formally, STORE_SUBSCR, DELETE_SUBSCR, STORE_SLICE*, and DELETE_SLICE* where the first operand is the result of a LOAD_FAST of a 'safe' name. Thoughts? Evan @ 4-am

2 1

url is taking on a '/'
by Jason Spisak 06 Jan '00

06 Jan '00

I'm looking deeper into this problem, and the url() method is not getting rid of the last slash after the host. Cataloged objects end up with addresses like '/FolderA/FolderB/myobject' not 'FolderA/FolderB/myobject'. Has anyone else encountered this bug. I'll bet I'm not the only one. Desprately seeking Susan, uh I mean help... -- Jason Spisak webmaster(a)hiretechs.com

1 0

ZCatalog puting in double backslashes
by Jason Spisak 06 Jan '00

06 Jan '00

Help! How do I get the extra forward slash that the find items puts in to go away! Is there a bug fix. I get url's like http://localhost:8080//myobject instead of http://localhost:8080/myobject Help! Jason Spisak webmaster(a)hiretechs.com

1 0

RE: [Zope-dev] Product standardization
by Brian Lloyd 06 Jan '00

06 Jan '00

> Chris McDonough wrote: > > > > Though I can't speak at all for DC regarding this matter (this is > > probably Chris Petrilli's or Brian Lloyd's territory), > > Can you get them to speak up on this issue? :) I'll speak up :^) I agree that there should be more/better documentation on the writing of Zope products - there is some good info out there though: The Boring product: http://www.zope.org/Members/gtk/Boring The (excellent) Product API tutorial: http://www.zope.org/Members/Zen/howto/ProductAPITutorial Of course I will also admit that it's non-obvious how to find these gems and that it would be quite a bit better if there was "offical documentation". The current plan as I understand it is to work on getting an enhanced and updated version of the information in the ProductAPI tutuorial into the Zope Developer's Guide. > > I like the idea > > of having a slightly more formal definition of what > constitutes a "good" > > product, even if that definition only consisted of a couple > of pages of > > "shoulds" and "shouldn't"s. I think that this should be a part of the introductory material for the "how to write a product" documentation... > > I also like the idea of a loose sort of > > peer review (other than someone just downloading the > product, finding > > out it doesn't work, and posting to the mail lists). > > Yes, that's another way to get the ball running quickly. How do we set > this up, > though? Some procedures would be in order. I've whipped up a > suggestion: > > * appoint a number of 'Product reviewers'. Basically the Digital > Creations product gurus should appoint the first product reviewers (at > least 2), which hopefully include themselves. > > * A particular version of a product is considered to be 'Zope > compliant' > if at least 2 product reviewers did a thorough review and approve, and > no product reviewer at all vetos anything. > > * Set up a mailing list, Zope-review, to handle product review > discussions only. The product reviewers are subscribed, along with > product developers who want reviews, and anyone else that's > interested. > The list discussions may by necessity diverge into debates about > standards and guidelines. It may also go into technical discussions on > product development, but ideally the latter discussions > should be moved > to Zope-dev so more people can profit from the information; > development > questions should go to Zope-dev too. > > * If a product developer finishes a product that the current product > reviewers think is good (and substantial enough), such a product > developer can be appointed by them as product reviewer him or herself. > Such a developer should be nominated by a product reviewer, > and no other > product reviewer should veto the appointment. > > * Being a product reviewer is of course voluntary; you don't > have to do > anything or to accept any appointment. The idea is to bring structure > and some dependability to the review process, not to enforce anything. > Nobody _has_ to go through review. And there's of course the > open-source > ego-boost effect of being able to say you're a 'Zope product > reviewer'; > if you are that, you *must* be a Zope guru, eh? :) This status effect > will hopefully help motivate people to participate in the review > process. > > * Participating developers that are not official product reviewers may > of course review each other's code too; this is only good for > everybody > involved. Such informal product reviews will informally count when > official product reviewer status is considered. > > * Care should be taken that all this procedure does not actually slow > down the development process. The entire review process is voluntary; > you may still distribute unreviewed products. The goal of the > process is > to improve the design and code of both Zope and products, and > to get to > an idea of what it means to be 'Zope compliant', not to make > things more > difficult (in fact, this should make everything easier!). I think that peer review is a Good Thing - I share the opinion that it should be strictly voluntary and very light weight (in fact, I think that zope-dev would be a fine place for these types of discussions, rather than a separate list). My only caveat is: it will be much easier to "review" a product once there is an official description of what a good product is - so I would say that the immediate burden is on _us_ to get that out. Can you comment on this Amos? Brian Lloyd brian(a)digicool.com Software Engineer 540.371.6909 Digital Creations http://www.digicool.com

2 1

Can't paste CatalogAware object
by Itamar Shtull-Trauring 06 Jan '00

06 Jan '00

I have a ZClass that inherits (indirectly thorugh a python class) from CatalogAware. I cut an instance, then paste it. I get the following error (2.1.0 and 2.1.1): Error Type: AttributeError Error Value: aq_acquire Traceback (innermost last): ... File /home/zope/lib/python/OFS/CopySupport.py, line 225, in manage_pasteObjects (Object: CatalogAware) File /home/zope/lib/python/OFS/ObjectManager.py, line 267, in _delObject (Object: ElementWithAttributes) File /home/zope/lib/python/Products/ZCatalog/CatalogAwareness.py, line 129, in manage_beforeDelete (Object: CatalogAware) File /home/zope/lib/python/Products/ZCatalog/CatalogAwareness.py, line 186, in unindex_object (Object: CatalogAware) File /home/zope/lib/python/Products/ZCatalog/CatalogAwareness.py, line 156, in url (Object: CatalogAware) File /home/zope/lib/python/OFS/SimpleItem.py, line 315, in absolute_url (Object: CatalogAware) File /home/zope/lib/python/OFS/SimpleItem.py, line 315, in absolute_url (Object: ElementWithAttributes) File /home/zope/lib/python/OFS/Application.py, line 282, in absolute_url (Object: ApplicationDefaultPermissions) AttributeError: (see above) -- Itamar S.T. itamars(a)ibm.net

1 1

RE: [Zope-dev] ODMG compliance?
by Michel Pelletier 06 Jan '00

06 Jan '00

> -----Original Message----- > From: Kenneth Y.K. YOUNG [mailto:kyoung@kyoung.net] > Sent: Wednesday, January 05, 2000 9:12 PM > To: Zope-Dev Mailing List > Cc: Hannu Krosing; Anthony Baxter > Subject: RE: [Zope-dev] ODMG compliance? > > > > My understanding of ODMG standard is superficial, but the > motivation of > examining Zope's standard compliance are as follows: (pls > correct me if I'm > wrong) > > (1) how well it integrates with Corba - i.e. can I access > Zope functions > from programs written in perl/C/smalltalk/Java via corba, and > have zope > reuse Corba components written in these languages. Corba integration does not exist, but it would not be dificult to do. As a corba client, you could take some third party python corba package and integrate it into a Zope product to create "CORBA Methods" that would word presumably like External Methods. As a CORBA server you could create a new ZServer module. Remember, ZPublisher, the 'heart' of Zope, is an Object Request Broker (ORB) that maps quite cleanly onto CORBA. In the past when ZPublisher was Bobo, I beleive there was even some work done to make Bobo corba aware, I'm not certain. In any case there has been no demand on us for it for a while now, corba is not a very active standard. XML-RPC seems to fill it's shoes quite well. > (2) how well it complies with the OQL standard - i.e. is it > query-lanugage > compatiable with e.g. CA's Jasmine ii It is not OQL compliant at all, however I see no reason why it would not be easy to make it so. > (3) Zope's architecture is so user-friendly and extensible > that i am very > pleased with it on small projects, and would be very eager to > use it for a > large scale implementation if I can find out how it stands re (1)/(2). It is suitable for large scale implimentations regardless of 1 or 2, it just doesn't support 1 or 2. > From the replies received, I gather Zope is not very advanced in these > directions, psychologically if not actually. I beg any core > developer might > explain that it will take 3 months'/years' work to make these > happen, for > example? I couldn't tell you, but you could take a hack at it. I belive there are a couple Python corba packages. -Michel

1 0

debugging zope in IDLE
by Wei Tao 06 Jan '00

06 Jan '00

After changing some codes in z2.py around line 381: - __builtins__.__debug__=DEBUG + os.environ['Z_DEBUG_MODE']='1' + DEBUG=1 +# __builtins__.__debug__=DEBUG I have successfully run Zope from the IDLE in debug mode, and i can use those "go, step, over, out and quit". There is no anything wrong till now. But, I can't set breakpoint in IDLE ( the current windoze version downloaded from www.python.org ). Sorry for windoze, these days I stay home preparing for exams and have only windoze :< When I right click in the source window and click "set breakpoint here", IDLE just responds with a "click" and does nothing AT ALL. en, my question is whether IDLE does NOT support breakpoint yet ? or just IDLE for windoze doesn't ? regards, lenx

1 1

RE: [Zope-dev] Product standardization
by Chris McDonough 06 Jan '00

06 Jan '00

Though I can't speak at all for DC regarding this matter (this is probably Chris Petrilli's or Brian Lloyd's territory), I like the idea of having a slightly more formal definition of what constitutes a "good" product, even if that definition only consisted of a couple of pages of "shoulds" and "shouldn't"s. I also like the idea of a loose sort of peer review (other than someone just downloading the product, finding out it doesn't work, and posting to the mail lists). I would be willing to work on both. Chris McDonough mailto:chrism@digicool.com Digital Creations http://www.digicool.com Publishers of Zope http://www.zope.org > -----Original Message----- > From: Martijn Faassen [mailto:m.faassen@vet.uu.nl] > Sent: Wednesday, January 05, 2000 9:38 AM > To: zope-dev(a)zope.org > Subject: [Zope-dev] Product standardization > > > Hi there, > > Many of us are developing products for Zope; either in pure > python, pure > ZClasses, or a combination. I'd like to make the products I'm > making as > 'Zope compliant' as possible; that is, they should use: > > * the standard Zope web interface > * they should follow the standard Zope security conventions > * when possible, they should implement a number other standard Zope > interfaces, such as the properties interface and the object manager > interface. > > The problem is that there is, as far as I know, no: > > * standard Zope web interface definition > * standard Zope security conventions description > * description of other standard Zope interfaces > > This is in part a documentation problem, but in part it's simply that > the standards are probably undefined. The classes to inherit from are > there in many cases, but I personally am in the dark concerning many > issues. I just practice 'voodoo programming' where I just do stuff > because I know I have to, but haven't a clue why. This is bad. > > So, could we start somekind of process in order to define > what it means > to be 'Zope compliant'. I have in mind: > > * standards documents > > * guidelines documents > > * motivations and explanations of the standards and guidelines. > > * tutorials and examples, such as products like the 'Boring' product > that give working and compliant examples. > > * a peer review process; developers review each other's > product code for > standard compliance. Product users can do part of the > reviewing as well. > > * Perhaps somekind of 'official approval stamp', that at least gives a > clue that the product you're using is mature and complaint. Though we > should watch out that this process wouldn't slow down development. > > Doing this could help us in many ways; we learn more about > how to write > a product, we learn more about how to write a *good* (secure, usable) > product, and finally the development of Zope itself is helped by > pointing out what people use/should use, and suggestions for future > directions. > > Any comments, ideas? > > Regards, > > Martijn > > _______________________________________________ > 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 ) >

3 2