Re: [Zope] Improved Zope Org Proposal

2006-06-24 Thread John Schinnerer
Aloha, As an occasional user of the zope.org site I'll present my typical use case, as that's what matters most to me... :-D I go there normally for one of two reasons: 1) to slog through available products to see if I can find something to suit a development need I have 2) to slog

Re: [Zope] Improved Zope Org Proposal

2006-06-24 Thread Lennart Regebro
I would like to take this opprotunity to repeat myself. I know this is boring but I feel it is important. :-) We have already made a new www.zope.org once. That was an ambitious project, which potential did not become fully realized. We need to take with us the experiences of that. And this is

Re: [Zope] Improved Zope Org Proposal

2006-06-24 Thread Jens Vagelpohl
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 24 Jun 2006, at 00:15, Andrew Sawyers wrote: A group of people in the (Plone) community have volunteered their time and resources to put together an improved, **interim** zope.org site. We understand that work is underway on a longer-term

Re: [Zope] Searching for and displaying properties

2006-06-24 Thread Andreas Jung
--On 24. Juni 2006 21:50:15 +0800 Sinang, Danny [EMAIL PROTECTED] wrote: jobs = cat.searchResults({'jobname':'ABC12345'}) for j in jobs: print j.jobname 'jobname' is added as *metadata* to your catalog? -aj -- ZOPYX Ltd. Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany Web:

RE: [Zope] Searching for and displaying properties

2006-06-24 Thread Sinang, Danny
'jobname' is added as *metadata* to your catalog? Not sure if using manage_addProperty () to add jobname is equivalent to adding it as *metadata* . code manage_addProperty('jobname', 'ABC12345', 'string') /code ___ Zope maillist - Zope@zope.org

RE: [Zope] Searching for and displaying properties

2006-06-24 Thread Andreas Jung
--On 24. Juni 2006 22:06:39 +0800 Sinang, Danny [EMAIL PROTECTED] wrote: 'jobname' is added as *metadata* to your catalog? Not sure if using manage_addProperty () to add jobname is equivalent to adding it as *metadata* . code manage_addProperty('jobname', 'ABC12345', 'string') /code

RE: [Zope] Searching for and displaying properties

2006-06-24 Thread Sinang, Danny
This add a property to an object but it has nothing to do with adding *metadata* to a ZCatalog instance. Please read the ZCatalog chapter of the Zope Book 2.7 edition. It carefully explains what *metadata* in the ZCatalog context means. The short version: a Zcatalog search returns *proxy*

RE: [Zope] Searching for and displaying properties

2006-06-24 Thread Andreas Jung
--On 24. Juni 2006 22:36:00 +0800 Sinang, Danny [EMAIL PROTECTED] wrote: So going back to my original question, is there a way for me not to have to mass-refresh my entire catalog just to be able to display my properties ? Click on update catalog in the Advanced tab or use the

RE: [Zope] Searching for and displaying properties

2006-06-24 Thread Sinang, Danny
Click on update catalog in the Advanced tab or use the refreshCatalog() method of the ZCatalog (described in its interfaces.py file). refreshCatalog() is exactly what I was forced to use in the first place. I was wondering if there exists an alternative function / method that won't require

RE: [Zope] Searching for and displaying properties

2006-06-24 Thread Andreas Jung
--On 24. Juni 2006 22:45:10 +0800 Sinang, Danny [EMAIL PROTECTED] wrote: Click on update catalog in the Advanced tab or use the refreshCatalog() method of the ZCatalog (described in its interfaces.py file). refreshCatalog() is exactly what I was forced to use in the first place. I

RE: [Zope] Searching for and displaying properties

2006-06-24 Thread Sinang, Danny
That's the official ZCatalog API. Otherwise find your objects through a catalog search and reindex them individually. I already did the reindexing just before the search and it didn't work. In any case, I may have found a workaround by using getObject(). According to

RE: [Zope] Searching for and displaying properties

2006-06-24 Thread Andreas Jung
--On 24. Juni 2006 23:04:34 +0800 Sinang, Danny [EMAIL PROTECTED] wrote: wf = context.GeneralWorkflow cat = wf.Catalog jobs = cat.searchResults({'jobname':'ABC12345'}) for j in jobs: print j.getObject().jobname return printed /code My only question now is ... How much slower is

[Zope] Re: Searching for and displaying properties

2006-06-24 Thread Michael Haubenwallner
Sinang, Danny wrote: This add a property to an object but it has nothing to do with adding *metadata* to a ZCatalog instance. Please read the ZCatalog chapter of the Zope Book 2.7 edition. It carefully explains what *metadata* in the ZCatalog context means. The short version: a Zcatalog

[Zope] zcatalog strange behavior

2006-06-24 Thread bard stéphane
Hi every one I've used zcatalog 2 years ago. Every thing was perfect My zclass objects where removed from zcatalog when they were delete etc ... Today i try to create another zclass on the same zope server (2.6) zclass with zobject,zcatalogaware inheritance and the zcatalogawareness don't work

Re: [Zope] Searching for and displaying properties

2006-06-24 Thread Tino Wildenhain
Sinang, Danny wrote: Dear All, I managed to add a property to an object by using the manage_addproperty () method. However, if I don't issue a manage.reindexIndex () for the new property, it won't come out in the catalog search results. manage_addProperty does not trigger recataloguing

Re: [Zope] Improved Zope Org Proposal

2006-06-24 Thread Dieter Maurer
Andrew Sawyers wrote at 2006-6-23 18:15 -0400: ... For bug tracking, either links to the existing ZC trackers or a Trac installation. If you move to Trac *PLEASE* migrate the current issues. It is very discouraging to loose all the bug reports and patches (as happened when a former

Re: [Zope] Improved Zope Org Proposal

2006-06-24 Thread Dieter Maurer
Lennart Regebro wrote at 2006-6-24 10:58 +0200: ... 1. We do NOT want a new www.zope.org. We want MANY new something.zope.org. We should have a products.zope.org, and a collector.zope.org, and a faq.zope.org, and a wiki.zope.org, and blablabla. In what way would this differ from

[Zope] Zope 2.9.3/2.9.1 On Suse 10.1 box version

2006-06-24 Thread Ofer Weisglass
Hi I am trying to install Zope 2.9.3 or 2.9.1 on Suse 10.1 and this is what I get: error: must supply either home or prefix/exec-prefix -- not both make: *** [install] Error 1 Any ideas what to do? Thanks linux-6310:/usr/local/src # md5sum Zope-2.9.3.tgz 4e8b4e076cadd6eb62dd4513748cb9f9

Re: [Zope] Improved Zope Org Proposal

2006-06-24 Thread Lennart Regebro
On 6/24/06, Dieter Maurer [EMAIL PROTECTED] wrote: In what way would this differ from zope.org/{collector,faq,wiki,...}? Well, for one, it´s simpler to set up, and does not rely one one single point of failure (and apache that does the rewriting) to each separate server. Secondly, what I'm

Re: [Zope] Improved Zope Org Proposal

2006-06-24 Thread Andrew Sawyers
On Sat, 2006-06-24 at 20:13 +0200, Dieter Maurer wrote: Andrew Sawyers wrote at 2006-6-23 18:15 -0400: ... For bug tracking, either links to the existing ZC trackers or a Trac installation. If you move to Trac *PLEASE* migrate the current issues. It is very discouraging to

Re: [Zope] Improved Zope Org Proposal

2006-06-24 Thread Andrew Sawyers
On Sat, 2006-06-24 at 10:58 +0200, Lennart Regebro wrote: We have already made a new www.zope.org once. That was an ambitious project, which potential did not become fully realized. We need to take with us the experiences of that. Trust me, many of us do. Jens and I spent many many hours on

[Zope-Checkins] SVN: Zope/branches/tseaver-retire_zpkg/doc/CHANGES.txt Don't call retiring zpkg a bugfix.

2006-06-24 Thread Tres Seaver
Log message for revision 68823: Don't call retiring zpkg a bugfix. Changed: U Zope/branches/tseaver-retire_zpkg/doc/CHANGES.txt -=- Modified: Zope/branches/tseaver-retire_zpkg/doc/CHANGES.txt === ---

[Zope-Checkins] SVN: Zope/branches/tseaver-retire_zpkg/inst/Makefile.in Normalize spelling: 'TMPDIR' - 'TMP_DIR'.

2006-06-24 Thread Tres Seaver
Log message for revision 68824: Normalize spelling: 'TMPDIR' - 'TMP_DIR'. Changed: U Zope/branches/tseaver-retire_zpkg/inst/Makefile.in -=- Modified: Zope/branches/tseaver-retire_zpkg/inst/Makefile.in === ---

[Zope-Checkins] SVN: Zope/branches/2.9/lib/python/Signals/SignalHandler.py removed zLOG dependency

2006-06-24 Thread Andreas Jung
Log message for revision 68825: removed zLOG dependency Changed: U Zope/branches/2.9/lib/python/Signals/SignalHandler.py -=- Modified: Zope/branches/2.9/lib/python/Signals/SignalHandler.py === ---

[Zope-Checkins] SVN: Zope/branches/tseaver-retire_zpkg/lib/python/zope/app/ servicenames is required, too.

2006-06-24 Thread Tres Seaver
Log message for revision 68831: servicenames is required, too. Changed: _U Zope/branches/tseaver-retire_zpkg/lib/python/zope/app/ U Zope/branches/tseaver-retire_zpkg/lib/python/zope/app/EXTERNALS.txt -=- Property changes on: Zope/branches/tseaver-retire_zpkg/lib/python/zope/app

[Zope-Checkins] SVN: Zope/branches/2.9/lib/python/ Replace bulk of uses of 'zLOG' with equivalent Python 'logging' module usage.

2006-06-24 Thread Tres Seaver
Log message for revision 68835: Replace bulk of uses of 'zLOG' with equivalent Python 'logging' module usage. Exceptions: - 'ZServer' code which uses the 'register_subsystem' stuff. - Code which imports custom log levels (BLATHER, TRACE), now pulled from

[Zope-dev] Re: SVN: Zope/branches/tseaver-retire_zpkg/ Note dropping of 'zpkg'; use a current version number.

2006-06-24 Thread Philipp von Weitershausen
Tres Seaver wrote: Log message for revision 68810: Note dropping of 'zpkg'; use a current version number. Changed: U Zope/branches/tseaver-retire_zpkg/doc/CHANGES.txt U Zope/branches/tseaver-retire_zpkg/setup.py -=- Modified: Zope/branches/tseaver-retire_zpkg/doc/CHANGES.txt

[Zope-dev] Re: SVN: Zope/branches/tseaver-retire_zpkg/ Note dropping of 'zpkg'; use a current version number.

2006-06-24 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Philipp von Weitershausen wrote: Tres Seaver wrote: Log message for revision 68810: Note dropping of 'zpkg'; use a current version number. Changed: U Zope/branches/tseaver-retire_zpkg/doc/CHANGES.txt U

[Zope-dev] Re: Proposal: Scrap zpkg for Zope2 releases

2006-06-24 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tres Seaver wrote: I worked last night with folks from the Fedora Extras project who were trying to package Zope 2.9.3 for FC5+. Because they were working from the release tarball, generated by 'zpkg', much of my knowledge about how the build

Re: [Zope-dev] Re: Proposal: Scrap zpkg for Zope2 releases

2006-06-24 Thread Andreas Jung
Thanks a lot for your work! --On 24. Juni 2006 09:40:36 -0400 Tres Seaver [EMAIL PROTECTED] wrote: Remaining TODOs: - I would like to have a few more folks try out working with the tarball, which I have uploaded to zope.org:

[Zope-dev] buildbot failure in Zope branches 2.9 2.4 Linux zc-buildbot

2006-06-24 Thread buildbot
The Buildbot has detected a failed build of Zope branches 2.9 2.4 Linux zc-buildbot. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 6317 Blamelist: andreasjung,benji_york,ctheune,dominikhuber,hdima,jens,philikon,tseaver,yuppie BUILD FAILED: failed test

[Zope-dev] Re: Proposal: Scrap zpkg for Zope2 releases

2006-06-24 Thread Philipp von Weitershausen
Tres Seaver wrote: I believe that the extra flexibility which zpkg is intended to provide (dependency-based subset distributions, primarily) would be better served by moving Zope to use eggs, Where are the eggs, btw? I will be ready shortly to merge this branch to the 2.9 branch, the 2.10

[Zope-dev] Re: SVN: Zope/branches/tseaver-retire_zpkg/ Note dropping of 'zpkg'; use a current version number.

2006-06-24 Thread Philipp von Weitershausen
Tres Seaver wrote: Since you're denoting this as a current version number, do I take it that you're planning on changing the way Zope 2.9 and 2.10 releases are created as well? I would consider egg-based deployment a feature; at least it's a big enough change that I'd be worried for it to

Re: [Zope-dev] Database mounting problem in 2.9.3?

2006-06-24 Thread Dieter Maurer
Chris Withers wrote at 2006-6-23 17:12 +0100: Get this error on startup with one project I've just moved to Zope 2.9.3: File /usr/local/zope/2.9.3/lib/python/Zope2/Startup/datatypes.py, line 175, in createDB return ZODBDatabase.open(self, databases) File

[Zope-dev] Re: Proposal: Scrap zpkg for Zope2 releases

2006-06-24 Thread Philipp von Weitershausen
Tres Seaver wrote: The point is that the release tarball should generate the same environment that the developers routinely work in; otherwise, we leave the poor suckers who install from it stuck with whatever bugs are caused by the difference. Ok. I'll note that Python eggs don't fulfill

[Zope-dev] Re: Proposal: Scrap zpkg for Zope2 releases

2006-06-24 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Philipp von Weitershausen wrote: Tres Seaver wrote: The point is that the release tarball should generate the same environment that the developers routinely work in; otherwise, we leave the poor suckers who install from it stuck with whatever

Re: [Zope-dev] Re: Proposal: Scrap zpkg for Zope2 releases

2006-06-24 Thread Sidnei da Silva
On Sat, Jun 24, 2006 at 04:08:23PM +0200, Andreas Jung wrote: | - Make the corresponding changes to the Windows build machinery. | | | Perhaps we should check the Windows build machinery before merging the | branch. | It's easy to mess up the Windows stuff but it's hard to fix it :-) I can

[Zope-dev] Re: Proposal: Scrap zpkg for Zope2 releases

2006-06-24 Thread Philipp von Weitershausen
Tres Seaver wrote: That will be good. Even after eliminating the list you provided (see below), there is still a lot of stuff in zope.app which is irrelevant to Zope2 (I think). Agreed. By the way, I just compated a Zope 2.9.3 install with your tarball. The same comparison should be done