Re: [Zope-dev] compilezpy (compileall)
On Wednesday 21 November 2001 18:41, Richard Jones wrote: On Wednesday 21 November 2001 16:34, Danny William Adair wrote: As from what I know (leaving aside for a moment that I basically know nothing), Zope should be _started_ as root, but then be _running_ as nobody. This does make sense to me, in a couple of ways. :-) Do you know when or where this switch to nobody is performed? in z2[s].py (lines 831 onwards in z2s.py) Cool! This sounds like a really cool answer - just the kind I love - but... I have never seen a z2s.py, and z2.py has less than 800 lines. Please tell me where I'm being thick here... thx, Danny ___ 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 )
Re: [Zope-dev] SearchIndex deprecation warning
Danny William Adair wrote: Apparently one or more of my installed (third-party) products is causing this. I don't think so. Try this: delete all filesystem products from the Zope control panel, and restart Zope. I think you'll find that the products will return, and you won't get these messages at startup. You're getting these errors because of persistent Catalog objects stored by the Zope help system, which were created before Zope 2.4. -- Steve Alexander Software Engineer Cat-Box limited ___ 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 )
Re: [Zope-dev] SearchIndex deprecation warning
Steve, you are right. I have only thought of a fresh 2.4 installation without using a pre-2.4 Data.fs. Andreas - Original Message - From: Steve Alexander [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: Andreas Jung [EMAIL PROTECTED]; zope-dev @ zope.org [EMAIL PROTECTED] Sent: Wednesday, November 21, 2001 04:48 Subject: Re: [Zope-dev] SearchIndex deprecation warning Danny William Adair wrote: Apparently one or more of my installed (third-party) products is causing this. I don't think so. Try this: delete all filesystem products from the Zope control panel, and restart Zope. I think you'll find that the products will return, and you won't get these messages at startup. You're getting these errors because of persistent Catalog objects stored by the Zope help system, which were created before Zope 2.4. -- Steve Alexander Software Engineer Cat-Box limited ___ 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 )
Re: [Zope-dev] bug reporting idea
Your points are valid, but I think I maybe didn't explain myself well enough. I was just thinking of it happening in debug mode, not on a live server. So many people may find bugs but don't know about the collector. Even just a link to the collector would encourage more people to report bugs. There would be a greater volume of false positives, but this is a bug management issue, not a reason to discourage bug reports. IMO we should be aiming at a very stable, bug free system, and for that we need lots of eyeballs. All this thinking just came from the observation that real bugs often don't get reported because someone doesn't know about the collector, or even how to report bugs well. seb - Original Message - From: Chris Withers [EMAIL PROTECTED] To: seb bacon [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Sunday, November 11, 2001 11:14 AM Subject: Re: [Zope-dev] bug reporting idea seb bacon wrote: What do people think about a semi-automatic bug reporting system, like the gnome bug buddy? Gotta be a big -1 from me I'm afraid. There's a few issues: - huge ammounts of false reports. Imagine someone who sticks up their first Zope site has a slight bug. Everyone who visits it sees the warning and 'does their duty' by reporting the bug. - irritation factor for site users - I go to special efforts to kill off Netscape's thing when I'm using Mozilla 'cos it just adds more time to recovering from a Mozilla crash/hang/etc. With a website, people might well walk away :-( however, this last one is the killer for me: - security. As someone who runs Zope servers, I don't want _anything_ automatically dumping potentially senesitive information out of my server. And yes, I am one of those people who sometimes 'cleans' tracebacks before posting them here or in the collecto ;-) cheers, Chris ___ 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 )
Re: [Zope-dev] Catalog improvements
On Tuesday, November 20, 2001, at 03:35 PM, Wolfram Kerber wrote: Hi, i'm currently working on a product that allows to attach relational information to zope-objects. It works quite well so far, but to further enhance it i need to make some changes to the Catalog. I could perhaps implement it as a separate product, but i strongly feel that those changes are best applied to the Catalog itself, as they are of general use (i think) and involve a lot of changes to the inner workings of the Catalog. In particular i need the following: - named/stored queries these are precompiled queries, so they can be executed without parsing and are easily cacheable i.e. similar to what is implemented in CMFTopic, but stored in the Catalog and a bit smarter There used to be something like this in ZTables/Tabula (a Zope 1.x product that was sort of the genesis of the Catalog, for better or worse) called 'Hierarchies'. Hierarchies were actually indexes (I think the current Keyword index is descended from the Keyword Hierarchy). I don't know what happened to that code. If it's not available, you could probably achieve the effect that you're looking for here with PluginIndexes, which wouldn't require changing the Catalog at all. Just write a Query Index that indexes objects that match its pre-cooked Query. This would speed up searching tremendously, but you could take a big hit at indexing time if you have many of them. Jeffrey P Shell, [EMAIL PROTECTED] ___ 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 )
Re: [Zope-dev] SearchIndex deprecation warning
On Wednesday 21 November 2001 22:48, Steve Alexander wrote: Danny William Adair wrote: Apparently one or more of my installed (third-party) products is causing this. I don't think so. Try this: delete all filesystem products from the Zope control panel, and restart Zope. I think you'll find that the products will return, and you won't get these messages at startup. You're getting these errors because of persistent Catalog objects stored by the Zope help system, which were created before Zope 2.4. That did the trick. Thank you very much! Andreas, sorry that I didn't mention the upgrade. Thanks you two, Danny ___ 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 )
[Zope-dev] PathIndex
The search method of PathIndex class returns varying types depending on the success of the search. If the search fails a list object is returned, if the search succeeds an object of type BTrees.IIBTree.IISet is returned. This causes a problem in _apply_index in PathIndex when PathIndex tries to do either a union or intersection. I am doing a search of a catalog like this: catalog.searchResults(path=['/folder1','/folder2']) This should return all objects in the catalog that are inside of folder1 or folder2 and works perfectly as long as objects from both folder1 and folder2 exist in the catalog. However if say folder2 does not exist then _apply_index tries to do a union between a list and an IISet object. This raises an invalid argument exception. I'm not 100% sure where this problem should be addressed, but a quick fix I saw was to change part of _apply_index in PathIndex from: if operator==or: set_func = union else: set_func = intersection res = None for k in record.keys: rows = self.search(k,level) res = set_func(res, rows) To something like this: if operator==or: set_func = union else: set_runc = intersection res = None for k in record.keys: rows = self.search(k,level) if rows == []: rows = None res = set_func(res,rows) This works since union and intersection will take None as an argument but not an empty list. I would suggest PathIndex.search be changed to return an empty IISet if it fails just to have consistancy. Let me know what you think --Brian Brinegar ECN Web Technician MSEE 104 A 494-3106 http://www.geeksoft.net/ ___ 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 )
Re: [Zope-dev] compilezpy (compileall)
On Wednesday 21 November 2001 19:49, Danny William Adair wrote: On Wednesday 21 November 2001 18:41, Richard Jones wrote: On Wednesday 21 November 2001 16:34, Danny William Adair wrote: As from what I know (leaving aside for a moment that I basically know nothing), Zope should be _started_ as root, but then be _running_ as nobody. This does make sense to me, in a couple of ways. :-) Do you know when or where this switch to nobody is performed? in z2[s].py (lines 831 onwards in z2s.py) Cool! This sounds like a really cool answer - just the kind I love - but... I have never seen a z2s.py, and z2.py has less than 800 lines. Please tell me where I'm being thick here... You're not - z2s is from M2Crypto and is a modified z2.py that's used to control the SSL-enabled Zope. Richard ___ 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 )
Re: [Zope-dev] Catalog improvements
- Original Message - From: Jeffrey P Shell [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, November 21, 2001 7:38 PM Subject: Re: [Zope-dev] Catalog improvements On Tuesday, November 20, 2001, at 03:35 PM, Wolfram Kerber wrote: Hi, i'm currently working on a product that allows to attach relational information to zope-objects. It works quite well so far, but to further enhance it i need to make some changes to the Catalog. I could perhaps implement it as a separate product, but i strongly feel that those changes are best applied to the Catalog itself, as they are of general use (i think) and involve a lot of changes to the inner workings of the Catalog. In particular i need the following: - named/stored queries these are precompiled queries, so they can be executed without parsing and are easily cacheable i.e. similar to what is implemented in CMFTopic, but stored in the Catalog and a bit smarter There used to be something like this in ZTables/Tabula (a Zope 1.x product that was sort of the genesis of the Catalog, for better or worse) called 'Hierarchies'. Hierarchies were actually indexes (I think the current Keyword index is descended from the Keyword Hierarchy). I don't know what happened to that code. If it's not available, you could probably achieve the effect that you're looking for here with PluginIndexes I think your right. Indexes also have a management interface that could be used to define the query. It could result in a nesting problem however, if 'QueryIndexes' rely on each others results (that they should be able to). I would possibly need a management view that shows the hirarchical structure of the Indexes, but it can be merely that, a view. I'll try this out... , which wouldn't require changing the Catalog at all. I'd say, if i would _not_ store the result of the query and just delegate to other indexes this would be true, otherwise i would need some notify mechanism to tell if my result is affected by an indexing call, and/or at least be notified when the call is over so i can update the result by issuing a query, but the latter would mean to 'take the big hit' as you mentioned, wich i think isn't acceptable. Just write a Query Index that indexes objects that match its pre-cooked Query. This would speed up searching tremendously, but you could take a big hit at indexing time if you have many of them. Jeffrey P Shell, [EMAIL PROTECTED] thanks, Wolfram ___ 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 )
Re: [Zope-dev] PathIndex
Let me know what you think You should submit this to the Collector: http://collector.zope.org I have already had a good experience with it ;-) ___ 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 )
