[Zope-Checkins] SVN: Zope/trunk/lib/python/zope/ Use a newer version of zope.interface and zope.component
Log message for revision 81360: Use a newer version of zope.interface and zope.component Changed: _U Zope/trunk/lib/python/zope/ -=- Property changes on: Zope/trunk/lib/python/zope ___ Name: svn:externals - annotation -r 77445 svn://svn.zope.org/repos/main/zope.annotation/trunk/src/zope/annotation cachedescriptors-r 77445 svn://svn.zope.org/repos/main/zope.cachedescriptors/trunk/src/zope/cachedescriptors component -r 77445 svn://svn.zope.org/repos/main/zope.component/trunk/src/zope/component configuration -r 77445 svn://svn.zope.org/repos/main/zope.configuration/trunk/src/zope/configuration contentprovider -r 77445 svn://svn.zope.org/repos/main/zope.contentprovider/trunk/src/zope/contentprovider contenttype -r 77445 svn://svn.zope.org/repos/main/zope.contenttype/trunk/src/zope/contenttype copypastemove -r 77445 svn://svn.zope.org/repos/main/zope.copypastemove/trunk/src/zope/copypastemove datetime-r 77445 svn://svn.zope.org/repos/main/zope.datetime/trunk/src/zope/datetime decorator -r 77445 svn://svn.zope.org/repos/main/zope.decorator/trunk/src/zope/decorator deferredimport -r 77445 svn://svn.zope.org/repos/main/zope.deferredimport/trunk/src/zope/deferredimport deprecation -r 77445 svn://svn.zope.org/repos/main/zope.deprecation/trunk/src/zope/deprecation documenttemplate-r 77445 svn://svn.zope.org/repos/main/zope.documenttemplate/trunk/src/zope/documenttemplate dottedname -r 77445 svn://svn.zope.org/repos/main/zope.dottedname/trunk/src/zope/dottedname dublincore -r 77445 svn://svn.zope.org/repos/main/zope.dublincore/trunk/src/zope/dublincore event -r 77445 svn://svn.zope.org/repos/main/zope.event/trunk/src/zope/event exceptions -r 77445 svn://svn.zope.org/repos/main/zope.exceptions/trunk/src/zope/exceptions filerepresentation -r 77445 svn://svn.zope.org/repos/main/zope.filerepresentation/trunk/src/zope/filerepresentation formlib -r 77445 svn://svn.zope.org/repos/main/zope.formlib/trunk/src/zope/formlib hookable-r 77445 svn://svn.zope.org/repos/main/zope.hookable/trunk/src/zope/hookable i18nmessageid -r 77445 svn://svn.zope.org/repos/main/zope.i18nmessageid/trunk/src/zope/i18nmessageid i18n-r 77445 svn://svn.zope.org/repos/main/zope.i18n/trunk/src/zope/i18n index -r 77445 svn://svn.zope.org/repos/main/zope.index/trunk/src/zope/index interface -r 77445 svn://svn.zope.org/repos/main/zope.interface/trunk/src/zope/interface lifecycleevent -r 77445 svn://svn.zope.org/repos/main/zope.lifecycleevent/trunk/src/zope/lifecycleevent location-r 77445 svn://svn.zope.org/repos/main/zope.location/trunk/src/zope/location modulealias -r 77445 svn://svn.zope.org/repos/main/zope.modulealias/trunk/src/zope/modulealias pagetemplate-r 77445 svn://svn.zope.org/repos/main/zope.pagetemplate/trunk/src/zope/pagetemplate proxy -r 77445 svn://svn.zope.org/repos/main/zope.proxy/trunk/src/zope/proxy publisher -r 77445 svn://svn.zope.org/repos/main/zope.publisher/trunk/src/zope/publisher rdb -r 77445 svn://svn.zope.org/repos/main/zope.rdb/trunk/src/zope/rdb schema -r 77445 svn://svn.zope.org/repos/main/zope.schema/trunk/src/zope/schema security-r 77445 svn://svn.zope.org/repos/main/zope.security/trunk/src/zope/security sequencesort-r 77445 svn://svn.zope.org/repos/main/zope.sequencesort/trunk/src/zope/sequencesort sendmail-r 77445 svn://svn.zope.org/repos/main/zope.sendmail/trunk/src/zope/sendmail server -r 77445 svn://svn.zope.org/repos/main/zope.server/trunk/src/zope/server size-r 77445 svn://svn.zope.org/repos/main/zope.size/trunk/src/zope/size structuredtext -r 77445 svn://svn.zope.org/repos/main/zope.structuredtext/trunk/src/zope/structuredtext tales -r 77445 svn://svn.zope.org/repos/main/zope.tales/trunk/src/zope/tales tal -r 77445 svn://svn.zope.org/repos/main/zope.tal/trunk/src/zope/tal testbrowser -r 77445 svn://svn.zope.org/repos/main/zope.testbrowser/trunk/src/zope/testbrowser testing -r 77445 svn://svn.zope.org/repos/main/zope.testing/trunk/src/zope/testing thread -r 77445 svn://svn.zope.org/repos/main/zope.thread/trunk/src/zope/thread traversing -r 77445 svn://svn.zope.org/repos/main/zope.traversing/trunk/src/zope/traversing viewlet -r 77445 svn://svn.zope.org/repos/main/zope.viewlet/trunk/src/zope/viewlet wfmc-r 77445 svn://svn.zope.org/repos/main/zope.wfmc/trunk/src/zope/wfmc + annotation -r 77445 svn://svn.zope.org/repos/main/zope.annotation/trunk/src/zope/annotation cachedescriptors-r 77445
[Zope-Checkins] SVN: Zope/trunk/lib/python/zope/ Use an even newer zope.interface
Log message for revision 81364: Use an even newer zope.interface Changed: _U Zope/trunk/lib/python/zope/ -=- Property changes on: Zope/trunk/lib/python/zope ___ Name: svn:externals - annotation -r 77445 svn://svn.zope.org/repos/main/zope.annotation/trunk/src/zope/annotation cachedescriptors-r 77445 svn://svn.zope.org/repos/main/zope.cachedescriptors/trunk/src/zope/cachedescriptors component -r 81359 svn://svn.zope.org/repos/main/zope.component/trunk/src/zope/component configuration -r 77445 svn://svn.zope.org/repos/main/zope.configuration/trunk/src/zope/configuration contentprovider -r 77445 svn://svn.zope.org/repos/main/zope.contentprovider/trunk/src/zope/contentprovider contenttype -r 77445 svn://svn.zope.org/repos/main/zope.contenttype/trunk/src/zope/contenttype copypastemove -r 77445 svn://svn.zope.org/repos/main/zope.copypastemove/trunk/src/zope/copypastemove datetime-r 77445 svn://svn.zope.org/repos/main/zope.datetime/trunk/src/zope/datetime decorator -r 77445 svn://svn.zope.org/repos/main/zope.decorator/trunk/src/zope/decorator deferredimport -r 77445 svn://svn.zope.org/repos/main/zope.deferredimport/trunk/src/zope/deferredimport deprecation -r 77445 svn://svn.zope.org/repos/main/zope.deprecation/trunk/src/zope/deprecation documenttemplate-r 77445 svn://svn.zope.org/repos/main/zope.documenttemplate/trunk/src/zope/documenttemplate dottedname -r 77445 svn://svn.zope.org/repos/main/zope.dottedname/trunk/src/zope/dottedname dublincore -r 77445 svn://svn.zope.org/repos/main/zope.dublincore/trunk/src/zope/dublincore event -r 77445 svn://svn.zope.org/repos/main/zope.event/trunk/src/zope/event exceptions -r 77445 svn://svn.zope.org/repos/main/zope.exceptions/trunk/src/zope/exceptions filerepresentation -r 77445 svn://svn.zope.org/repos/main/zope.filerepresentation/trunk/src/zope/filerepresentation formlib -r 77445 svn://svn.zope.org/repos/main/zope.formlib/trunk/src/zope/formlib hookable-r 77445 svn://svn.zope.org/repos/main/zope.hookable/trunk/src/zope/hookable i18nmessageid -r 77445 svn://svn.zope.org/repos/main/zope.i18nmessageid/trunk/src/zope/i18nmessageid i18n-r 77445 svn://svn.zope.org/repos/main/zope.i18n/trunk/src/zope/i18n index -r 77445 svn://svn.zope.org/repos/main/zope.index/trunk/src/zope/index interface -r 81359 svn://svn.zope.org/repos/main/zope.interface/trunk/src/zope/interface lifecycleevent -r 77445 svn://svn.zope.org/repos/main/zope.lifecycleevent/trunk/src/zope/lifecycleevent location-r 77445 svn://svn.zope.org/repos/main/zope.location/trunk/src/zope/location modulealias -r 77445 svn://svn.zope.org/repos/main/zope.modulealias/trunk/src/zope/modulealias pagetemplate-r 77445 svn://svn.zope.org/repos/main/zope.pagetemplate/trunk/src/zope/pagetemplate proxy -r 77445 svn://svn.zope.org/repos/main/zope.proxy/trunk/src/zope/proxy publisher -r 77445 svn://svn.zope.org/repos/main/zope.publisher/trunk/src/zope/publisher rdb -r 77445 svn://svn.zope.org/repos/main/zope.rdb/trunk/src/zope/rdb schema -r 77445 svn://svn.zope.org/repos/main/zope.schema/trunk/src/zope/schema security-r 77445 svn://svn.zope.org/repos/main/zope.security/trunk/src/zope/security sequencesort-r 77445 svn://svn.zope.org/repos/main/zope.sequencesort/trunk/src/zope/sequencesort sendmail-r 77445 svn://svn.zope.org/repos/main/zope.sendmail/trunk/src/zope/sendmail server -r 77445 svn://svn.zope.org/repos/main/zope.server/trunk/src/zope/server size-r 77445 svn://svn.zope.org/repos/main/zope.size/trunk/src/zope/size structuredtext -r 77445 svn://svn.zope.org/repos/main/zope.structuredtext/trunk/src/zope/structuredtext tales -r 77445 svn://svn.zope.org/repos/main/zope.tales/trunk/src/zope/tales tal -r 77445 svn://svn.zope.org/repos/main/zope.tal/trunk/src/zope/tal testbrowser -r 77445 svn://svn.zope.org/repos/main/zope.testbrowser/trunk/src/zope/testbrowser testing -r 77445 svn://svn.zope.org/repos/main/zope.testing/trunk/src/zope/testing thread -r 77445 svn://svn.zope.org/repos/main/zope.thread/trunk/src/zope/thread traversing -r 77445 svn://svn.zope.org/repos/main/zope.traversing/trunk/src/zope/traversing viewlet -r 77445 svn://svn.zope.org/repos/main/zope.viewlet/trunk/src/zope/viewlet wfmc-r 77445 svn://svn.zope.org/repos/main/zope.wfmc/trunk/src/zope/wfmc + annotation -r 77445 svn://svn.zope.org/repos/main/zope.annotation/trunk/src/zope/annotation cachedescriptors-r 77445
[Zope-dev] Re: Zope on Python 2.5?
Alexander Limi wrote: On Wed, 31 Oct 2007 21:29:36 -0700, Andreas Jung [EMAIL PROTECTED] wrote: The recommendation is still System python is evil, evil, evil (quoting Jim). Sure, but if you ever want to be able to tell users to do: easy_install plone to get their Plone site, it's a necessary evil evil evil. ;) I don't think the System Python argument is the most important here. It's more important that Python 2.4 will start looking unsupported and third party libraries will start depending on Python 2.5 before long, if not already. Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Zope on Python 2.5?
Baiju M wrote: Hi Limi, Alexander Limi wrote: Sorry if this has been asked hundreds of times before — I couldn't find any info on this apart from the Summer of Code project related to Zope 3. Now only the packages under `zope` `zope.app` packages works using Python 2.5 . I don't know the status of packages in `zc`, `z3c` and other namespaces. I also heard Grok is working fine with Python 2.5, but not yet officially blessed/supported. Indeed. The biggest problem that's preventing us from officially blessing Python 2.5 as *a* supported platform is a MemoryError on 64 bit Linux systems. Possibly https://bugs.edge.launchpad.net/zodb/+bug/153316 is related to this as well (another issue that's only a problem on 64 bit). Will Zope 2 ever run on Python 2.5, or is that postponed indefinitely? We see an increasing amount of users trying to use Zope 2 with their systems that have Python 2.5 as default. Nikhil, who worked on Python 2.5 porting of Zope 3, told me that he will be working Zope 2 porting after his exams. That's great news. -- http://worldcookery.com -- Professional Zope documentation and training ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Zope on Python 2.5?
Alexander Limi wrote: Will Zope 2 ever run on Python 2.5, or is that postponed indefinitely? It will run on Python 2.5 when somebody makes it run. We see an increasing amount of users trying to use Zope 2 with their systems that have Python 2.5 as default. Then I suggest you do something about it. Making it a sprint topic on one of the numerous Plone sprints would help, for instance. As far as I can remember, Nikhil (our GSoC student) looked at making RestrictedPython work on Python 2.5. Somebody should review this. Moreover, there are lots C extension that -- last time I checked -- just failed to compile on Python 2.5. Though I'm sure most of these problems could be fixed by applying suggested replacements in the Python 2.5 release notes. -- http://worldcookery.com -- Professional Zope documentation and training ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: Zope on Python 2.5?
On Thursday 01 November 2007 06:18:18 Andreas Jung wrote: --On 31. Oktober 2007 22:00:46 -0700 Alexander Limi [EMAIL PROTECTED] wrote: On Wed, 31 Oct 2007 21:29:36 -0700, Andreas Jung [EMAIL PROTECTED] wrote: The recommendation is still System python is evil, evil, evil (quoting Jim). Sure, but if you ever want to be able to tell users to do: easy_install plone Would be fine but as long as several distros contain brain-dead or castrated Python installations there is little we can do - even if we would support Python 2.5. I always wondered -- I never had any trouble with the system Pythons, or at least not a problem that I could attribute to a system Python (Debian Stable and Ubuntu LTS) Its just so damn convenient if you have to maintain a few dozen VServers to manage the Pythons including add-on libraries exclusively via apt-get Which system Pythons do you think are brain dead, and why? Thanks, peter. to get their Plone site, it's a necessary evil evil evil. ;) We generally encourage not to use the system Python in everything we ship (Windows, Mac and Unified installers all ship their own Python) — but I really hope we won't be stuck with Python 2.4 after the world has moved on to Python 2.5 and 2.6. Bring the word to the Python packagers. I agree that for proper deployments, you shouldn't use the system Python, but there's the case of letting people get started with Plone easily from their Ubuntu or Mac OS X (Leopard ships with Python 2.5 and easy_install by default) — we should be able to let them do that too. See above. Stepping forward with Python 2.5/2.6 support would be fine but it basically does not solve the problem that system python installation are often broken. Installation a Python from the sources is usually much more faster than trying to figure out why a system python is broken once more. ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] z3c.rml svn checkout
Hello I am trying to checkout latest version of z3c.rml and i get the following error: svn co http://svn.zope.org/z3c.rml/ z3c.rml svn: PROPFIND request failed on '/z3c.rml' svn: PROPFIND of '/z3c.rml': 301 Moved (http://svn.zope.org) Thanks, -- Catalin Constantin ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Zope Tests: 5 OK
Summary of messages to the zope-tests list. Period Wed Oct 31 13:00:00 2007 UTC to Thu Nov 1 13:00:00 2007 UTC. There were 5 messages: 5 from Zope Unit Tests. Tests passed OK --- Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Wed Oct 31 21:46:50 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-October/008576.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Wed Oct 31 21:48:20 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-October/008577.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Wed Oct 31 21:49:50 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-October/008578.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Wed Oct 31 21:51:20 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-October/008579.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Wed Oct 31 21:52:51 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-October/008580.html ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope on Python 2.5?
On Nov 1, 2007, at 12:29 AM, Andreas Jung wrote: We see an increasing amount of users trying to use Zope 2 with their systems that have Python 2.5 as default. The recommendation is still System python is evil, evil, evil (quoting Jim). N, that's evil evil evil evil. Geez. ;) Or maybe it should be stupid stupid . Jim -- Jim Fulton Zope Corporation ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: Zope on Python 2.5?
On Nov 1, 2007, at 1:00 AM, Alexander Limi wrote: On Wed, 31 Oct 2007 21:29:36 -0700, Andreas Jung [EMAIL PROTECTED] wrote: The recommendation is still System python is evil, evil, evil (quoting Jim). Sure, but if you ever want to be able to tell users to do: easy_install plone to get their Plone site, it's a necessary evil evil evil. ;) So don't do that. Plone is an application (afaik) not a library. I thought Plone had an installer that installed a local Python. We generally encourage not to use the system Python in everything we ship (Windows, Mac and Unified installers all ship their own Python) Cool. Note that I think this problem will get worse as system packages include more and more of the packages we use. I read yesterday that the Python in Mac OS X Leopard includes zope.interface. — but I really hope we won't be stuck with Python 2.4 after the world has moved on to Python 2.5 and 2.6. This is really a separate issue. I hope we won't either. Unfortunately, supporting them is non-trivial, I think we've made a lot of progress. I agree that for proper deployments, you shouldn't use the system Python, but there's the case of letting people get started with Plone easily from their Ubuntu or Mac OS X (Leopard ships with Python 2.5 and easy_install by default) — we should be able to let them do that too. I don't agree. easy_install is really not well suited to installing applications IMO. I think an installer is a better idea for installing applications, for lots of reasons. Jim -- Jim Fulton Zope Corporation ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: SVN: zope.component/trunk/ Optimized un/registerUtility via storing an optimized data structure for
Hanno Schlichting wrote: Log message for revision 81348: Optimized un/registerUtility via storing an optimized data structure for efficient retrieval of already registered utilities. This avoids looping over all utilities when registering a new one. You are changing what looks like persistent datastructures. Are you sure this doesn't introduce backwards compatibility issues? I also question naming the next release 3.4.1. This is not a bugfix. I think it should come in as 3.5. Regards, Martijn ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Zope on Python 2.5?
Alexander Limi wrote: On Wed, 31 Oct 2007 21:29:36 -0700, Andreas Jung [EMAIL PROTECTED] wrote: The recommendation is still System python is evil, evil, evil (quoting Jim). Sure, but if you ever want to be able to tell users to do: easy_install plone to get their Plone site, it's a necessary evil evil evil. ;) We generally encourage not to use the system Python in everything we ship (Windows, Mac and Unified installers all ship their own Python) — but I really hope we won't be stuck with Python 2.4 after the world has moved on to Python 2.5 and 2.6. Agreed. Of course we'll still be stuck on Python 2.x for what amounts to indefinitely when Python 3.x comes out, but that is another problem for the future. I agree that something like this is a necessary evil. I don't think easy_install plone should ever be the way to install it, unless this installs a 'ploneproject' that creates buildouts for you and then installs everything non-globally. Nonetheless, this should be possible with the system Python, just so people can try things out easily. Anyway, perhaps some of the Plone people could volunteer in fixing up Zope 2 for Python 2.5 then? Regards, Martijn ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: Zope on Python 2.5?
I would like to point out that on this thread people are getting too tied up with restrictions about *installing* stuff on the system Python and forgetting that for example, buildout will not install stuff on the system Python, but people might want to run a Zope (2) buildout on Python 2.5 just because it's the Python they have installed. Now, putting Limi's proven incapability to start a discussion without causing major commotion from our fellow developers, let's rephrase the question: Will Zope 2 be supported on Python 2.5, regardless of whether it's a system-installed Python or not? I think we are closely approaching the EOL for Python 2.4. Supposedly when Python 2.6 comes out next year Python 2.4 will be officially discouraged and will not receive any more fixes other than security fixes. I believe this is a critical issue and the interested parts need to work together on it. Maybe the Plone Foundation and the Zope Foundation can work together and setup a bounty to fund some developer to do this work? -- Sidnei da Silva Enfold Systemshttp://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214 ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] z3c.rml svn checkout
This tells you how to use the svn repository: http://www.zope.org/DevHome/Subversion/ZopeSVNFAQ /Tim On Nov 1, 2007, at 1:44 PM, Catalin Constantin wrote: Hello I am trying to checkout latest version of z3c.rml and i get the following error: svn co http://svn.zope.org/z3c.rml/ z3c.rml svn: PROPFIND request failed on '/z3c.rml' svn: PROPFIND of '/z3c.rml': 301 Moved (http://svn.zope.org) Thanks, -- Catalin Constantin ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: Zope on Python 2.5?
On Nov 1, 2007, at 9:50 AM, Sidnei da Silva wrote: I would like to point out that on this thread people are getting too tied up with restrictions about *installing* stuff on the system Python and forgetting that for example, buildout will not install stuff on the system Python, but people might want to run a Zope (2) buildout on Python 2.5 just because it's the Python they have installed. Agreed. I almost mentioned this as an otoh in one of my previous posts. I think buildout should work harder to get along with system Python. I intent to spend some effort on this. Martijn has suggested an option to ignore site-packages which may go a long way. Of course, this has nothing to do with 2.5. :) Jim -- Jim Fulton Zope Corporation ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Zope on Python 2.5?
Hey, [making Zope 2 work on Python 2.5] Sidnei da Silva wrote: [snip] I believe this is a critical issue and the interested parts need to work together on it. Maybe the Plone Foundation and the Zope Foundation can work together and setup a bounty to fund some developer to do this work? That's an idea that certainly deserves some exploration! The Zope Foundation awaits the Plone Foundation's proposals for something like this with great anticipation! Note that I explicitly put the ball to initiate these discussions in their court, as it appears that the Plone project feels a particular urgency here, Alexander Limi having kicked off this discussion. This could finally start some cooperation between the two foundations, something I've been hoping would happen for a long time now. Now we have something concrete. Note that the Zope Foundation indirectly has supported topic a bit, thanks to the summer of code. Nikhil, the summer of code student, worked on supporting the Zope (3) libraries on Python 2.5 already. Nikhil apparently already wants to work on this project. Regards, Martijn ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: Zope on Python 2.5?
On Thursday 01 November 2007, Jim Fulton wrote: I think buildout should work harder to get along with system Python. I intent to spend some effort on this. Martijn has suggested an option to ignore site-packages which may go a long way. Yeah, one of my clients uses workingenv to use system python without all the additional site-packages and then uses this workingenv's python executable for buildout. It would be great, if he would not need to use workingenv in this case. Regards, Stephan -- Stephan Richter CBU Physics Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: SVN: zope.component/trunk/ Optimized un/registerUtility via storing an optimized data structure for
Martijn Faassen wrote: Hanno Schlichting wrote: Log message for revision 81348: Optimized un/registerUtility via storing an optimized data structure for efficient retrieval of already registered utilities. This avoids looping over all utilities when registering a new one. You are changing what looks like persistent datastructures. Are you sure this doesn't introduce backwards compatibility issues? Sorry, you are right. I changed it to only optimize non-persistent registries and fall back on the algorithm which doesn't need an optimized new data structure as before. I also question naming the next release 3.4.1. This is not a bugfix. I think it should come in as 3.5. I'm not sure what criteria determine if something is a feature change and what is not, so I changed the next version on trunk to 3.5. Hanno ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: SVN: zope.component/trunk/ Optimized un/registerUtility via storing an optimized data structure for
Hanno Schlichting wrote: Martijn Faassen wrote: Hanno Schlichting wrote: Log message for revision 81348: Optimized un/registerUtility via storing an optimized data structure for efficient retrieval of already registered utilities. This avoids looping over all utilities when registering a new one. You are changing what looks like persistent datastructures. Are you sure this doesn't introduce backwards compatibility issues? Sorry, you are right. I changed it to only optimize non-persistent registries and fall back on the algorithm which doesn't need an optimized new data structure as before. Does it still install the optimized datastructure if you create a new persistent registry? I also question naming the next release 3.4.1. This is not a bugfix. I think it should come in as 3.5. I'm not sure what criteria determine if something is a feature change and what is not, so I changed the next version on trunk to 3.5. I think the criteria should be very simple: if it's a bugfix, you can release a bugfix release. If it's anything else, make it a feature release. Optimization is a feature, not a bugfix. The combination here would've been particularly bad: people innocently try version 3.4.1 and suddenly find their ZODB is broken. :) Note that I'm actually quite excited to see optimization work - this is why I paid particular attention to your checkin at all. Thanks for looking into this stuff! Regards, Martijn ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: Zope on Python 2.5?
On 11/1/07, Sidnei da Silva [EMAIL PROTECTED] wrote: I think we are closely approaching the EOL for Python 2.4. Supposedly when Python 2.6 comes out next year Python 2.4 will be officially discouraged and will not receive any more fixes other than security fixes. This seems to be a common misconception; I'm not sure why. Python 2.4 has *already* hit EOL. There will only be security fixes released in source form. When a new Python 2.X is released, a final 2.X-1 bugfix release is made and 2.X becomes the maintenance release. 2.X-1 gets critical security fixes only. The unreleased trunk becomes the development version. -Fred -- Fred L. Drake, Jr.fdrake at gmail.com Chaos is the score upon which reality is written. --Henry Miller ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: Zope on Python 2.5?
On 11/1/07, Fred Drake [EMAIL PROTECTED] wrote: This seems to be a common misconception; I'm not sure why. Python 2.4 has *already* hit EOL. There will only be security fixes released in source form. When a new Python 2.X is released, a final 2.X-1 bugfix release is made and 2.X becomes the maintenance release. 2.X-1 gets critical security fixes only. The unreleased trunk becomes the development version. Ouch. I guess we should skip 2.5 and target 2.6 then to save some time :) -- Sidnei da Silva Enfold Systemshttp://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214 ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: SVN: zope.component/trunk/ Optimized un/registerUtility via storing an optimized data structure for
Martijn Faassen wrote: Hanno Schlichting wrote: Martijn Faassen wrote: Hanno Schlichting wrote: Log message for revision 81348: Optimized un/registerUtility via storing an optimized data structure for efficient retrieval of already registered utilities. This avoids looping over all utilities when registering a new one. You are changing what looks like persistent datastructures. Are you sure this doesn't introduce backwards compatibility issues? Sorry, you are right. I changed it to only optimize non-persistent registries and fall back on the algorithm which doesn't need an optimized new data structure as before. Does it still install the optimized datastructure if you create a new persistent registry? No, it doesn't do that at all anymore. The only thing that is speed up is registering and unregistering utilities which shouldn't happen for persistent registries all that often. In a standard Plone site you have about 1800 global utilities and registering those at Zope startup time has been quite slow, as the former algorithm looped through all already registered utilities when adding a new one. I also question naming the next release 3.4.1. This is not a bugfix. I think it should come in as 3.5. I'm not sure what criteria determine if something is a feature change and what is not, so I changed the next version on trunk to 3.5. I think the criteria should be very simple: if it's a bugfix, you can release a bugfix release. If it's anything else, make it a feature release. Optimization is a feature, not a bugfix. The combination here would've been particularly bad: people innocently try version 3.4.1 and suddenly find their ZODB is broken. :) Note that I'm actually quite excited to see optimization work - this is why I paid particular attention to your checkin at all. Thanks for looking into this stuff! We are sitting here in Copenhagen on the Plone performance sprint and found some more interesting pieces... stay tuned ;) Hanno ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] buildbot failure in Zope trunk 2.4 Windows 2000 zc-bbwin6
The Buildbot has detected a failed build of Zope trunk 2.4 Windows 2000 zc-bbwin6. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 3029 Blamelist: berndroessl,faassen,fdrake,geroldboehler,hannosch,jim,jukart,philikon,rossp,srichter,timt,witsch BUILD FAILED: failed svn sincerely, -The Buildbot ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Zope on Python 2.5?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Stephan Richter wrote: On Thursday 01 November 2007, Jim Fulton wrote: I think buildout should work harder to get along with system Python. I intent to spend some effort on this. Martijn has suggested an option to ignore site-packages which may go a long way. Yeah, one of my clients uses workingenv to use system python without all the additional site-packages and then uses this workingenv's python executable for buildout. It would be great, if he would not need to use workingenv in this case. I think that virtualenv is the right answer for folks who need to reuse the system python, but be insulated from its site-packages (and be able to install their own packages without touching the system environment. Ian Bicking, who authored workingenv, has basically dropped further development on it in favor of virtualenv. repoze.project uses virtualenv to create sandboxed Python environments, into which the custom packages are then installed, followed by the installation of scripts, config files, etc. to make the environment ready to run the given application (Zope2, Plone, Grok to date). Tres. - -- === Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHKgjv+gerLs4ltQ4RAvxcAKDHpgsyLkDDupW2JrIQvkZ2KM0mqwCfUEqA 47SlPfsBg62jXGKJ3ubSn64= =qKXa -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] buildbot failure in Zope trunk 2.4 Windows 2000 zc-bbwin6
The Buildbot has detected a failed build of Zope trunk 2.4 Windows 2000 zc-bbwin6. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 3033 Blamelist: geroldboehler,hannosch,jim,witsch BUILD FAILED: failed svn sincerely, -The Buildbot ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Interface.__identifier__
zope.inferface.interface.InterfaceClass.__init__ defines a nice attribute self.__identifier__ that stores self.__module__ + '.' + self.__name__, which is very handy when indexing and searching interfaces in Plone. However, unlike __module__, __identifier__ is not part of the IInterface declaration. Should it be added there to lift this attribute above implementation detail status? It can then also be used in zope.component.interface where it could replace the various usages of __module__ + '.' + __name__. -- Martijn Pieters ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Bad package dependencies
In summary: - Uploading eggs that have loose install_requires dependencies to the cheeseshop is harmful. - Taking non-Zope-the-appserver deployments into account, I'd be suspicious of any install_requires dependency on zope.configuration except in a Zope-the-appserver meta-egg. - Same for the [zcml] extra when specifying 'zope.component' in install_requires. - The dependencies of zope.configuration seem not sane, transitively. - The dependencies of zope.component [zcml] seem not sane, transitively (although 'zope.component' without the [zcml] is reasonably sane). Details: I wanted to go use zope.pagetemplate in a small non-Zope project. When I did easy_install zope.pagetemplate (from PyPI) into a fresh virtual environment, it installed all of the following eggs: ./zope.pagetemplate-3.4.0-py2.4.egg ./zope.tal-3.4.0-py2.4.egg ./zope.tales-3.4.0-py2.4.egg ./zope.interface-3.4.1-py2.4-macosx-10.3-i386.egg ./zope.i18n-3.4.0-py2.4.egg ./zope.i18nmessageid-3.4.3-py2.4-macosx-10.3-i386.egg ./zope.configuration-3.4.0-py2.4.egg ./zope.component-3.4.0-py2.4.egg ./pytz-2007g-py2.4.egg ./zope.schema-3.4.0-py2.4.egg ./zope.deprecation-3.4.0-py2.4.egg ./zope.proxy-3.4.0-py2.4-macosx-10.3-i386.egg ./zope.security-3.4.0-py2.4-macosx-10.3-i386.egg ./zope.event-3.4.0-py2.4.egg ./zope.deferredimport-3.4.0-py2.4.egg ./zope.testing-3.5.1-py2.4.egg ./zope.location-3.4.0-py2.4.egg ./zope.exceptions-3.4.0-py2.4.egg ./zope.traversing-3.4.0-py2.4.egg ./zope.publisher-3.4.1-py2.4.egg ./zope.app.applicationcontrol-3.4.1-py2.4.egg ./zope.app.testing-3.4.1-py2.4.egg ./zope.size-3.4.0-py2.4.egg ./zope.error-3.5.1-py2.4.egg ./zope.app.security-3.4.0-py2.4.egg ./zope.app.publication-3.4.3-py2.4.egg ./zope.app.folder-3.4.0-py2.4.egg ./zope.app.dependable-3.4.0-py2.4.egg ./zope.app.debug-3.4.0-py2.4.egg ./zope.app.container-3.5.2-py2.4-macosx-10.3-i386.egg ./zope.app.component-3.4.1-py2.4.egg ./zope.app.authentication-3.4.1-py2.4.egg ./zope.annotation-3.4.0-py2.4.egg ./zope.app.appsetup-3.4.1-py2.4.egg ./ZODB3-3.8.0b4-py2.4-macosx-10.3-i386.egg ./zope.app.publisher-3.5.0a2-py2.4.egg ./zope.app.pagetemplate-3.4.0-py2.4.egg ./zope.app.form-3.4.1-py2.4.egg ./zope.app.exception-3.4.1-py2.4.egg ./zope.app.error-3.5.1-py2.4.egg ./zope.app.http-3.4.1-py2.4.egg ./zope.dublincore-3.4.0-py2.4.egg ./zope.datetime-3.4.0-py2.4.egg ./zope.copypastemove-3.4.0-py2.4.egg ./zope.app.broken-3.4.0-py2.4.egg ./zope.filerepresentation-3.4.0-py2.4.egg ./zope.lifecycleevent-3.4.0-py2.4.egg ./zope.dottedname-3.4.2-py2.4.egg ./zope.cachedescriptors-3.4.0-py2.4.egg ./zope.app.zapi-3.4.0-py2.4.egg ./zope.thread-3.4-py2.4.egg ./zope.formlib-3.4.0-py2.4.egg ./zope.app.interface-3.4.0-py2.4.egg ./zope.app.session-3.5.1-py2.4.egg ./zdaemon-2.0.1-py2.4.egg ./ZConfig-2.5-py2.4.egg Once it gets past ZConfig, it then failed with: error: Installed distribution zope.traversing 3.4.0 conflicts with requirement zope.traversing=3.5.0a1.dev-r78730 The transitive install_requires dependencies of zope.pagetemplate 3.4.0 can't possibly be right, or at least they're much too conservative. The problem starts in the install_requires of zope.i18n: install_requires=['setuptools', 'pytz', 'zope.i18nmessageid', 'zope.component [zcml]', 'zope.configuration', ], zope.i18n should not depend on zope.configuration in install_requires, because it's only used in it's zcml.py and if you use it as a library (as opposed to as a Zope plugin) you won't load up any of its zcml; even if important stuff gets registered, it's expected that you'll have to do it by hand when it's used as a library. The dependency on 'zope.component [zcml]' is legitimate except for the [zcml] part for the same reason. The install_requires for the zope.pagetemplate setup.py (at least for 3.4.0) should be: install_requires=['setuptools', 'pytz == 2007g', 'zope.i18nmessageid == 3.4.3', 'zope.component == 3.4.0', ], When I build a new zope.i18n (3.4.0) egg with these dependencies, its transitive dependency set when installed is: pytz-2007g-py2.4.egg setuptools-0.6c7-py2.4.egg zope.component-3.4.0-py2.4.egg zope.deferredimport-3.4.0-py2.4.egg zope.deprecation-3.4.0-py2.4.egg zope.event-3.4.0-py2.4.egg zope.i18n-3.4.0-py2.4.egg zope.i18nmessageid-3.4.3-py2.4-macosx-10.3-i386.egg zope.interface-3.4.1-py2.4-macosx-10.3-i386.egg zope.proxy-3.4.0-py2.4-macosx-10.3-i386.egg .. which is acceptable, I think. Once that's done, the additional dependencies imposed by zope.pagetemplate are: zope.pagetemplate zope.tal zope.tales .. and it works as a library: Python 2.4.4 (#1, Oct 17 2007, 20:25:32) [GCC 4.0.1 (Apple Computer, Inc. build 5250)] on darwin Type help, copyright, credits or license for more information. from zope.pagetemplate.pagetemplatefile import
Re: [Zope-dev] Re: Zope on Python 2.5?
On Nov 1, 2007, at 1:28 AM, Andreas Jung wrote: --On 31. Oktober 2007 22:00:46 -0700 Alexander Limi [EMAIL PROTECTED] wrote: On Wed, 31 Oct 2007 21:29:36 -0700, Andreas Jung [EMAIL PROTECTED] wrote: The recommendation is still System python is evil, evil, evil (quoting Jim). Sure, but if you ever want to be able to tell users to do: easy_install plone One other point: easy_install plone make only sense if the underlying machinery generates an isolated environment for your Plone instance. You really don't want to mess up your system python with a hundred Zope or Plone eggs. This is definitely the road to disaster. On distributions that depends on Python for their internal processing/administration (I think Fedora does) you might break the functionality of your system installation significantly in case of broken or misbehaving eggs. So we must be careful about the story we're telling the users. The obviously easiest way is possibly not the best way (in the long term). I think installing into a virtualenv created by a system Python is at least 50% less evil than installing packages directly into the system Python, and reasonable for a development environment, at least in semi- controlled situations (like Apple's Python). - C ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: Zope on Python 2.5?
--On 1. November 2007 23:47:28 -0400 Chris McDonough [EMAIL PROTECTED] wrote: On Nov 1, 2007, at 1:28 AM, Andreas Jung wrote: --On 31. Oktober 2007 22:00:46 -0700 Alexander Limi [EMAIL PROTECTED] wrote: On Wed, 31 Oct 2007 21:29:36 -0700, Andreas Jung [EMAIL PROTECTED] wrote: The recommendation is still System python is evil, evil, evil (quoting Jim). Sure, but if you ever want to be able to tell users to do: easy_install plone One other point: easy_install plone make only sense if the underlying machinery generates an isolated environment for your Plone instance. You really don't want to mess up your system python with a hundred Zope or Plone eggs. This is definitely the road to disaster. On distributions that depends on Python for their internal processing/administration (I think Fedora does) you might break the functionality of your system installation significantly in case of broken or misbehaving eggs. So we must be careful about the story we're telling the users. The obviously easiest way is possibly not the best way (in the long term). I think installing into a virtualenv created by a system Python is at least 50% less evil than installing packages directly into the system Python, and reasonable for a development environment, at least in semi-controlled situations (like Apple's Python). Sure, but users that don't know about virtualenv might run into such problems. Andreas pgpnB1EuLVLRA.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Zope on Python 2.5?
Would it be possible to have a non-system python installed (by default into /opt/python24) by the system python easy_install? I think it would be useful to have eggs that provide commands on the path such as easy_install_nonsystem24, virtualenv_nonsystem24, python_nonsystem24. With a better spelling, of course. Perhaps if non-system pythons were packaged in a way that setuptools could install them, they might become ordinary dependencies of Zope/Plone eggs, which could detect and configure to use them in a virtualenv at setup time. I don't know if setuptools is currently capable of installing packages completely separate from the running environment, or executing another python during setup. However, It seems to me that the most expedient way to encourage widespread use of non-system python is to make them available as a dependency for applications and frameworks that prefer them. After my distribution (Gentoo) updated to python2.5, I made the overdue switch to a buildout-based non-system python. I greatly appreciate the fact that it has no packages installed and never changes, obliging me to use buildout or virtualenv always. I'd like to have the best-practice setup available as an easy_installable package. On my distribution, tools are already available to package complete/correct PyPI entries. Thanks. ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope] Defining a dictionary in ZPT?
Hi I've got this piece of code which is returning a keyerror on 'results' as I haven't set up a dictionary for the variables. I'm not sure what the syntax is for this within the ZPT. I've read about the 'options' dictionary. Can I use that? Thanks ul span tal:define=query here/testquery li tal content=results python: query(id='IT') span tal:replace=results/firstnameFirst Name/spannbsp; /li /span /ul -- michael ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Defining a dictionary in ZPT?
On Thu, Nov 01, 2007 at 12:48:04PM +, michael nt milne wrote: Hi I've got this piece of code which is returning a keyerror on 'results' as I haven't set up a dictionary for the variables. (snip) span tal:define=query here/testquery li tal content=results python: query(id='IT') span tal:replace=results/firstnameFirst Name/spannbsp; /li li tal content doesn't make any sense. I suspect you want that to be: li tal:define=results ... -- Paul Winkler ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Defining a dictionary in ZPT?
yeah I have modified to this li tal:define = query here/testquery tal:repeat=result python:query(id='IT') span tal:replace=python:repeat['result'].firstnameFirst Name/spannbsp; /li but get this as a result. Thanks for the reply. Module Products.PTProfiler.ProfilerPatch, line 32, in __patched_call__ Module Products.PageTemplates.ZRPythonExpr, line 47, in __call__ - __traceback_info__: query(id='IT') Module Python expression query(id='IT'), line 1, in expression AttributeError: Results instance has no __call__ method On 11/1/07, Paul Winkler [EMAIL PROTECTED] wrote: On Thu, Nov 01, 2007 at 12:48:04PM +, michael nt milne wrote: Hi I've got this piece of code which is returning a keyerror on 'results' as I haven't set up a dictionary for the variables. (snip) span tal:define=query here/testquery li tal content=results python: query(id='IT') span tal:replace=results/firstnameFirst Name/spannbsp; /li li tal content doesn't make any sense. I suspect you want that to be: li tal:define=results ... -- Paul Winkler ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev ) -- michael ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Re: Defining a dictionary in ZPT?
michael nt milne napsal(a): yeah I have modified to this li tal:define = query here/testquery tal:repeat=result python:query(id='IT') span tal:replace=python:repeat['result'].firstnameFirst Name/spannbsp; /li 1) don't make spaces around = in HTML attributes: tal:define=query here/testquery 2) Why do you use repeat['result'] ? Can you point us to documentation where did you read it ? tal:replace=result/firstname should work as expected or tal:replace=python:result['firstname'] in case of result is dictionary and you need to use python: for some reason. 3) what testquery returns ? I suppose it returns method, because you are calling this method wit parameter 'id', but I don't think you meant it in this way. -- Radim Novotny ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Calendar Tag Product question
- Original Message - From: Thomas Bennett [EMAIL PROTECTED] fine. Today, November 1, on both calendars not all events are appearing in the calendar from the default view. If you click back to October and then back to November all of the events appear, this also sets the date-calendar parameter in the URL to November 9. I have found that if the date-calendar parameter is 1,2,3, or 4 not all the events will display in the Corporate Calendar or the calendar I wrote so I suspect the Calendar Product itself. It looks like locales dateformat mismatch DDMM with MMDD Take look at your system locales settings, Zope locales setting. Do you have at all machines the same gcc, zope and python version? etc...etc... Regards, JL. ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Re: Defining a dictionary in ZPT?
1) don't make spaces around = in HTML attributes: tal:define=query here/testquery a mistake 2) Why do you use repeat['result'] ? Can you point us to documentation where did you read it ? tal:replace=result/firstname should work as expected or tal:replace=python:result[ 'firstname'] in case of result is dictionary and you need to use python: for some reason. http://wiki.zope.org/ZPT/RepeatVariable requires repeat to be called. I used this as previously using tal:replace=result/firstname produced a keyerror as I had no dictionaries set up. The repeat variable sets-up a dictionary automatically... 3) what testquery returns ? I suppose it returns method, because you are calling this method wit parameter 'id', but I don't think you meant it in this way. testquery returns a ZSQL query which works and is tested. The id variable is totally meant as we are passing through a dynamic variable from a ZPT page through to the ZSQL query. At the moment to simplify things! (required..) this variable is fixed to 'IT'. Thanks for your help On 11/1/07, Radim Novotny [EMAIL PROTECTED] wrote: michael nt milne napsal(a): yeah I have modified to this li tal:define = query here/testquery tal:repeat=result python:query(id='IT') span tal:replace=python:repeat['result'].firstnameFirst Name/spannbsp; /li 1) don't make spaces around = in HTML attributes: tal:define=query here/testquery 2) Why do you use repeat['result'] ? Can you point us to documentation where did you read it ? tal:replace=result/firstname should work as expected or tal:replace=python:result['firstname'] in case of result is dictionary and you need to use python: for some reason. 3) what testquery returns ? I suppose it returns method, because you are calling this method wit parameter 'id', but I don't think you meant it in this way. -- Radim Novotny ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev ) -- michael ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )