[Zope-Checkins] SVN: Products.Five/branches/1.4/ Branch off Five 1.4. We're not releasing Five 1.4b yet, but we need a Five
Log message for revision 65584: Branch off Five 1.4. We're not releasing Five 1.4b yet, but we need a Five branch that is geared towards Zope trunk (=Zope 2.10). Rocky should merge his work only to the Five 1.4 branch. Five 1.4 is geared towards Zope 2.9. Changed: A Products.Five/branches/1.4/ -=- Copied: Products.Five/branches/1.4 (from rev 65583, Products.Five/trunk) ___ Zope-Checkins maillist - Zope-Checkins@zope.org http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/trunk/lib/python/OFS/Traversable.py using startswith()
Log message for revision 65598:
using startswith()
Changed:
U Zope/trunk/lib/python/OFS/Traversable.py
-=-
Modified: Zope/trunk/lib/python/OFS/Traversable.py
===
--- Zope/trunk/lib/python/OFS/Traversable.py2006-02-28 16:59:49 UTC (rev
65597)
+++ Zope/trunk/lib/python/OFS/Traversable.py2006-02-28 17:17:12 UTC (rev
65598)
@@ -173,7 +173,7 @@
name = path_pop()
__traceback_info__ = path, name
-if name[0] == '_':
+if name.startswith('_'):
# Never allowed in a URL.
raise NotFound, name
___
Zope-Checkins maillist - Zope-Checkins@zope.org
http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/trunk/lib/python/OFS/Traversable.py reverted all changes (obviously having a bad day today)
Log message for revision 65602: reverted all changes (obviously having a bad day today) Changed: U Zope/trunk/lib/python/OFS/Traversable.py -=- Modified: Zope/trunk/lib/python/OFS/Traversable.py === --- Zope/trunk/lib/python/OFS/Traversable.py2006-02-28 18:09:31 UTC (rev 65601) +++ Zope/trunk/lib/python/OFS/Traversable.py2006-02-28 19:12:01 UTC (rev 65602) @@ -134,11 +134,6 @@ the security machinery. Usually invoked using restrictedTraverse(). -if not isinstance(path, str): -path = [x for x in path if x] - -print 'r',self.absolute_url(1), path - if not path: return self ___ Zope-Checkins maillist - Zope-Checkins@zope.org http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/branches/2.9/ - Missing import of NotFound in webdav.Resource.
Log message for revision 65607: - Missing import of NotFound in webdav.Resource. Changed: U Zope/branches/2.9/doc/CHANGES.txt U Zope/branches/2.9/lib/python/webdav/Resource.py -=- Modified: Zope/branches/2.9/doc/CHANGES.txt === --- Zope/branches/2.9/doc/CHANGES.txt 2006-02-28 19:55:33 UTC (rev 65606) +++ Zope/branches/2.9/doc/CHANGES.txt 2006-02-28 19:56:14 UTC (rev 65607) @@ -14,6 +14,12 @@ to the rules for such a type laid out in the Python docs: http://docs.python.org/api/supporting-cycle-detection.html + After Zope 2.9.1 + +Bugs fixed + + - Missing import of NotFound in webdav.Resource. + Zope 2.9.1 (2006/02/25) Bugs fixed Modified: Zope/branches/2.9/lib/python/webdav/Resource.py === --- Zope/branches/2.9/lib/python/webdav/Resource.py 2006-02-28 19:55:33 UTC (rev 65606) +++ Zope/branches/2.9/lib/python/webdav/Resource.py 2006-02-28 19:56:14 UTC (rev 65607) @@ -24,7 +24,7 @@ from AccessControl import getSecurityManager from Acquisition import aq_base from zExceptions import BadRequest, MethodNotAllowed -from zExceptions import Unauthorized, Forbidden +from zExceptions import Unauthorized, Forbidden, NotFound from zope.interface import implements from ZPublisher.HTTPRangeSupport import HTTPRangeInterface ___ Zope-Checkins maillist - Zope-Checkins@zope.org http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/trunk/ - Missing import of NotFound in webdav.Resource.
Log message for revision 65608: - Missing import of NotFound in webdav.Resource. Changed: U Zope/trunk/doc/CHANGES.txt U Zope/trunk/lib/python/webdav/Resource.py -=- Modified: Zope/trunk/doc/CHANGES.txt === --- Zope/trunk/doc/CHANGES.txt 2006-02-28 19:56:14 UTC (rev 65607) +++ Zope/trunk/doc/CHANGES.txt 2006-02-28 20:02:08 UTC (rev 65608) @@ -197,6 +197,8 @@ Bugs Fixed + - Missing import of NotFound in webdav.Resource + - Collector #1819: fixed method signature of MountedObject.SimpleTrailblazer._construct() Modified: Zope/trunk/lib/python/webdav/Resource.py === --- Zope/trunk/lib/python/webdav/Resource.py2006-02-28 19:56:14 UTC (rev 65607) +++ Zope/trunk/lib/python/webdav/Resource.py2006-02-28 20:02:08 UTC (rev 65608) @@ -31,7 +31,7 @@ from AccessControl.Permissions import webdav_access from Acquisition import aq_base from zExceptions import BadRequest, MethodNotAllowed -from zExceptions import Unauthorized, Forbidden +from zExceptions import Unauthorized, Forbidden, NotFound from zope.interface import implements from ZPublisher.HTTPRangeSupport import HTTPRangeInterface ___ Zope-Checkins maillist - Zope-Checkins@zope.org http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/branches/ajung-final-zpt-integration/ Integration of Z3 ZPT with the current Z2 trunk and Five trunk
Log message for revision 65609: Integration of Z3 ZPT with the current Z2 trunk and Five trunk Changed: A Zope/branches/ajung-final-zpt-integration/ -=- Copied: Zope/branches/ajung-final-zpt-integration (from rev 65608, Zope/trunk) ___ Zope-Checkins maillist - Zope-Checkins@zope.org http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Products.Five/branches/philikon-local-components/ New approach to local components in Zope 2, based on Jim's new component registration
Log message for revision 65631:
New approach to local components in Zope 2, based on Jim's new component
registration
in the jim-adapter branch of Zope 3.
Five.component.browser actually features a CustomizationView which lets you
walk up
to an object, view a list of template-based browser views of that object and
lets
you customize it locally.
The simple doctest passes but some of the details still need to be worked
out. In
particular, the forms really haven't been tested yet nor viewed in their
rendered
form (they most probably are very ugly right now).
Changed:
A Products.Five/branches/philikon-local-components/component/
A Products.Five/branches/philikon-local-components/component/__init__.py
A Products.Five/branches/philikon-local-components/component/browser.py
A Products.Five/branches/philikon-local-components/component/component.txt
A Products.Five/branches/philikon-local-components/component/components.pt
A Products.Five/branches/philikon-local-components/component/configure.zcml
A
Products.Five/branches/philikon-local-components/component/customizeview.pt
A Products.Five/branches/philikon-local-components/component/interfaces.py
A
Products.Five/branches/philikon-local-components/component/templateviews.pt
A Products.Five/branches/philikon-local-components/component/tests.py
U Products.Five/branches/philikon-local-components/site/browser.py
U Products.Five/branches/philikon-local-components/site/localsite.py
U
Products.Five/branches/philikon-local-components/site/tests/sitemanager.txt
U
Products.Five/branches/philikon-local-components/site/tests/test_utility.py
-=-
Added: Products.Five/branches/philikon-local-components/component/__init__.py
===
--- Products.Five/branches/philikon-local-components/component/__init__.py
2006-03-01 00:04:15 UTC (rev 65630)
+++ Products.Five/branches/philikon-local-components/component/__init__.py
2006-03-01 00:34:35 UTC (rev 65631)
@@ -0,0 +1,67 @@
+##
+#
+# Copyright (c) 2006 Zope Corporation and Contributors.
+# All Rights Reserved.
+#
+# This software is subject to the provisions of the Zope Public License,
+# Version 2.1 (ZPL). A copy of the ZPL should accompany this distribution.
+# THIS SOFTWARE IS PROVIDED AS IS AND ANY AND ALL EXPRESS OR IMPLIED
+# WARRANTIES ARE DISCLAIMED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+# WARRANTIES OF TITLE, MERCHANTABILITY, AGAINST INFRINGEMENT, AND FITNESS
+# FOR A PARTICULAR PURPOSE.
+#
+##
+Component browser views
+
+$Id$
+
+from zope.event import notify
+from zope.interface import alsoProvides, noLongerProvides
+from zope.app.publication.zopepublication import BeforeTraverseEvent
+from zope.app.component.interfaces import ISite, IPossibleSite
+
+import ExtensionClass
+from Acquisition import aq_base
+from Products.SiteAccess.AccessRule import AccessRule
+from ZPublisher.BeforeTraverse import registerBeforeTraverse
+from ZPublisher.BeforeTraverse import unregisterBeforeTraverse
+
+# Hook up custom component architecture calls
+import zope.app.component.hooks
+zope.app.component.hooks.setHooks()
+
+class LocalSiteHook(ExtensionClass.Base):
+
+def __call__(self, container, request):
+notify(BeforeTraverseEvent(container, request))
+
+HOOK_NAME = '__local_site_hook__'
+
+def enableSite(obj, iface=ISite):
+Install __before_traverse__ hook for Local Site
+
+# We want the original object, not stuff in between, and no acquisition
+obj = aq_base(obj)
+if not IPossibleSite.providedBy(obj):
+raise TypeError, 'Must provide IPossibleSite'
+hook = AccessRule(HOOK_NAME)
+registerBeforeTraverse(obj, hook, HOOK_NAME, 1)
+
+if not hasattr(obj, HOOK_NAME):
+setattr(obj, HOOK_NAME, LocalSiteHook())
+
+alsoProvides(obj, iface)
+
+def disableSite(obj, iface=ISite):
+Remove __before_traverse__ hook for Local Site
+
+# We want the original object, not stuff in between, and no acquisition
+obj = aq_base(obj)
+if not iface.providedBy(obj):
+raise TypeError('Object must be a site.')
+
+unregisterBeforeTraverse(obj, HOOK_NAME)
+if hasattr(obj, HOOK_NAME):
+delattr(obj, HOOK_NAME)
+
+noLongerProvides(obj, iface)
Property changes on:
Products.Five/branches/philikon-local-components/component/__init__.py
___
Name: svn:eol-style
+ native
Added: Products.Five/branches/philikon-local-components/component/browser.py
===
--- Products.Five/branches/philikon-local-components/component/browser.py
2006-03-01 00:04:15 UTC (rev 65630)
+++
[Zope-Checkins] SVN: Products.Five/branches/philikon-local-components/component/browser.py Use _setObject which actually adds the object to the items list of the container.
Log message for revision 65656: Use _setObject which actually adds the object to the items list of the container. We probably still need to fix up the ZPT class so that it provides the correct manage_* junk (which essentially means creating a subclass with a bunch of mix-ins). Redirect happens on the response. Changed: U Products.Five/branches/philikon-local-components/component/browser.py -=- Modified: Products.Five/branches/philikon-local-components/component/browser.py === --- Products.Five/branches/philikon-local-components/component/browser.py 2006-03-01 05:18:37 UTC (rev 65655) +++ Products.Five/branches/philikon-local-components/component/browser.py 2006-03-01 05:28:58 UTC (rev 65656) @@ -94,7 +94,7 @@ zpt = ZPTPage() zpt.source = unicode(src) -obj._setOb(viewname, zpt) #XXX there could be a naming conflict +obj._setObject(viewname, zpt) #XXX there could be a naming conflict zpt = getattr(obj, viewname) components = obj.getSiteManager() @@ -111,7 +111,7 @@ def customizeTemplate(self, viewname): zpt = self.doCustomizeTemplate(viewname) #TODO use @@absolute_url view -self.request.redirect(zpt.absolute_url() + /manage_workspace) +self.request.RESPONSE.redirect(zpt.absolute_url() + /manage_workspace) class ZPTViewFactory(object): ___ Zope-Checkins maillist - Zope-Checkins@zope.org http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Products.Five/branches/philikon-local-components/component/templateviews.pt correct ZCML info object API
Log message for revision 65659:
correct ZCML info object API
Changed:
U
Products.Five/branches/philikon-local-components/component/templateviews.pt
-=-
Modified:
Products.Five/branches/philikon-local-components/component/templateviews.pt
===
--- Products.Five/branches/philikon-local-components/component/templateviews.pt
2006-03-01 05:30:21 UTC (rev 65658)
+++ Products.Five/branches/philikon-local-components/component/templateviews.pt
2006-03-01 05:31:16 UTC (rev 65659)
@@ -12,7 +12,7 @@
tal:attributes=href
string:@@customizetemplate.html?viewname=${reg/name}
tal:content=reg/name
/a
- as defined in tal:var replace=reg/info/filename /.
+ as defined in tal:var replace=reg/info/file /.
/li
/ul
___
Zope-Checkins maillist - Zope-Checkins@zope.org
http://mail.zope.org/mailman/listinfo/zope-checkins
Re: [Zope3-dev] Re: [Zope-dev] Two visions
Lennart Regebro wrote: I like the vision of Zope2 becoming a set of extra packages you install for Zope3, to get backwards compatibility. Maybe this is the same as what you call Zope 5, maybe not. +1 -- Dmitry Vasiliev (dima at hlabs.spb.ru) http://hlabs.spb.ru ___ 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: [Zope3-dev] Re: [Zope-dev] Two visions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Lennart Regebro a écrit : | OK, some initial, fuzzy comments: | | On 2/27/06, Jim Fulton [EMAIL PROTECTED] wrote: |2) In an alternate vision, Zope 2 evolves to Zope 5. | | - Zope 5 will be the application server generally known as Zope. It | will be backward compatible (to the same degree that Zope 2 | releases are currently backward compatible with previous Zope 2 | releases) with Zope 2. Zope 5 will similarly be backward | compatible with Zope 3 applications built on top of the current | Zope 3 application server. | | Note that Zope 5 will leverage Zope 3 technologies to allow a | variety of configurations, including a Zope 2-like configuration | with implicit acquisition and through-the-web development, and a | Zope 3-like configuration that looks a lot like the current Zope | 3 application server. Maybe, there will be a configuration that | allows Zope 2 and Zope 3 applications to be combined to a | significant degree. | | This overwhelms my complexity sensor. :-) | | I like the vision of Zope2 becoming a set of extra packages you | install for Zope3, to get backwards compatibility. Maybe this is the | same as what you call Zope 5, maybe not. I vote for this one. There's already Five product to help Zope2 products to become to be Zope3 compatible. Now, it's to Zope2 developpers to do the migration step. - -- Encolpe Degoute INGENIWEB (TM) - S.A.S 5 Euros - RC B 438 725 632 17 rue Louise Michel - 92300 Levallois Perret - France web : www.ingeniweb.com - « les Services Web Ingénieux » -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFEBBFHvFPzBBlIZMMRArvxAJ4vp3oOz4Jbs2sRdi5NiTmrgP0OYQCcDOa/ CGBI+hYJG7O+26x3Z40vuFU= =2wf7 -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] Re: [Zope3-dev] Two visions
Jim Fulton wrote: I'd like to get feedback on two possible visions for the future of Zope 2 and Zope 3. 1) Our current vision (AFAIK) is that Zope 3 will eventually replace Zope 2 [snip] 2) In an alternate vision, Zope 2 evolves to Zope 5. [snip] Thoughts? My initial reaction is: don't change the names (or at least be extremely careful about this). Zope 3 has a brand and we'd risk throwing it all away. We also risk being seen as wavering on the course. I don't see the two proposals as mutually exclusive, and I think both are true right now. Zope 3 is replacing Zope 2 for some new applications. Zope 2 is evolving towards Zope 3 for existing applications. I wrote a piece of text about the relationship between Zope 2 and Zope 3 that might help in this discussion: [snip section about Zope being mature] Going forward - We are applying our hard-earned lessons by making Zope better. The web is evolving and so is Zope, continuously striving to further increase Zope's power, flexibility and functionality. A visionary project was started in 2001 to build the next generation of Zope software, `Zope 3`_. Zope 3 uses powerful component technology to further increase the already strong extensibility and flexibility of the Zope platform. The Zope 3 project is benefiting in this from the deep experience of a large community of Zope 2 developers. Zope 2 is not being left behind however: the Zope community initiated a project called Five_ (2 + 3) to bring Zope 3 technology, where mature technology is ported back into the Zope 2 platform to obtain the best of both worlds. Zope 2 now contains Zope 3 technology and will go forward on this path with every release, while Zope 3 is forging ahead to explore new possibilities. Zope 2 and Zope 3 are evolving together this way, both benefiting from each other's strengths, until the differences between the two eventually disappear. Zope 2 and Zope 3 - Zope comes in two flavors, Zope 2 and Zope 3. Zope 2 is a mature, compatible and reliable platform that supports an enormous amounts of features. It's the workhorse of our community. Zope 3 provides a powerful component architecture and a clean, elegant architecture that is a developer's dream. It's our community's thoroughbred. It can be hard to choose between the two. Eventually you won't have to as they're evolving towards each other [Going Forward]. But how do you choose now? Here are some rough guidelines: If you are a hard-core developer, looking for power and flexibility in a clean architecture, and if you are building a new web application, you may want to consider Zope 3. If you want to make use of the rich variety of powerful Zope 2 software, need community, support and stability, consider Zope 2. And don't forget that with the Five_ (2 + 3) project, you can already start using Zope 3 technologies from within the safety of Zope 2. Whether you choose Zope 2 or Zope 3 for your project, you will reach the same future, just by a different path. Which path is better for you we leave up to you. I think the right way to go forward is to stay the course on this. Zope 3 is the future of Zope 2. Zope 2 will continue to evolve in the direction of Zope 3, while Zope 3 forges ahead. The difference between themselves will eventually disappear. Perhaps what I'm describing is already what you describe for Zope 5. I just don't see the reason to actually change the names, or to imply that Zope 3 does *not* have a future as a platform to build on, which could be seen as an implication of going with Zope 5. Changing names and version numbers around is not going to help anyone very much and I think could in fact be damaging. I think we're actually reaching some clarity of where we are going, people are starting to get the idea, and we just need to communicate it better to the wider world, not change our message. The pent-up demand for Zope 3 technology from Zope 2 developers that existed for a long time in the Zope 2 world while Zope 3 was under development has now been safely channeled into Five-related projects - people can actually use Zope 3 technology right now and worry less about the future. The meme Evolution not revolution which I have tried to spread along with Five has taken hold in the various Zope subcommunities. Here's some more of what I wrote: :Q: What's Zope? What's it good for? :A: It's a web application platform that can be used to build web applications, CMSes, etc. :Q: Where's zope coming from? is this some new thing? :A: No, it's mature. We got tons of experience and community and stuff. :Q: By 'mature' do you mean Zope is old cruft? :A: Nope, it's going forward, and has been working on this for years. (Zope 3) :Q: Well what's all this Zope 2 and zope 3 then? should I worry? :A: Nope, we are managing this, you can use either, and get the benefits of both. (Five) I think we can just carry on this message.
[Zope-dev] Re: [Zope3-dev] Re: Two visions
Max M wrote: Jim Fulton wrote: 2) In an alternate vision, Zope 2 evolves to Zope 5. Zope 2 is complicated! It has too many layers of everything. The reason for Zope 3 is to make it simpler for developers. Therefore I believe that any succesfull strategy would require Zope 3 to be usable completely without all the Zope 2 layers. If Zope 3 becomes just another layer on top of Zope 2 - CMF - Plone it will not reduce complexity, as any developer would still need to learn the entire stack. Wherever practical, Zope 2 technologies should be rewritten to Zope 3 technologies to remove layers from the stack. I think these are good points. Five runs the risk of being yet another layer on a stack like Plone, but Five also gives the chance of us stripping off these layers and replacing it with something cleaner, and at the same time Five is giving an impulse to Zope 3 development as things slowly get ported to Zope 3 or written in a Zope 3 style. The Five project has the right attitude to deal with such integration issues. We have been quite successful: In Zope 2.9 it's possible to build modern Zope 3-style apps, using formlib and sqlos and so on (we've done it). In this vision, the Zope 3 project should stay where it is and push things forward. That doesn't mean Five should be ignored by Zope 3 developers, but it should be compartmentalized in people's minds. Zope 3 does innovation, Five does integration, and then the big codebases can move forward using both. 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: Two visions
Philipp von Weitershausen wrote: [snip] I would vote for spelling out Zed (which would also be a little easier to google but might create trademark problems). The namespace package could either be 'z' or 'zed'. Then again, I really should take Jim's side and stay out of naming decisions. Let's please not have a naming discussion again. I think renaming Zope 3 is really bad marketing myself and naming discussions mostly a waste of time... 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: Two visions
Paul Winkler wrote: On Tue, Feb 28, 2006 at 12:31:33AM +0100, Philipp von Weitershausen wrote: I will also note that just because Zope 2 won't die, it doesn't mean we shouldn't clean it up. Eventually, Zope should mostly be reusing things from Zed. +sys.maxint I think this will be the way we get a real forward migration path for an awful lot of us who are still using Zope 2 today, and expect to continue doing so. We may or may not ever port to zope 3, whatever that will mean in the future. More likely we will just incrementally improve and clean up our applications, just as Zope 2 itself will be getting incrementally better and cleaner. We'll have to address deprecation warnings at each upgrade, but at no point will we be forced to do a complete rewrite. And along the way, we'll be gradually getting access to more and more nifty features. I don't see how we need a new vision. This has been the vision (evolution, not revolution) that I've been carrying out with Five for the last few years and thanks to a lot of contributions by a large range of developers, we've been making it work. Can't we just keep going on the way we've been going 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 )
[Zope-dev] Re: [Zope3-dev] Two visions
Hey, I have another comment about Zope 5, sparked by something Jeff Shell wrote. Currently we have a clear path to evolution. Zope 3 evolves at its pace, and Zope 2 evolves mostly by catching up with Zope 3, replacing more and more bits with Zope 3 bits, which often takes considerable ingenuity. We have shown that we have enough developers to sustain this both for Zope 3 and Zope 2 development. We know how to do it. Any shift to a Zope 5 vision where Zope 3 and Zope 2 are profiles of the same application would require a considerable investment of development time that we don't have, or alternatively, endless waiting. Zope 5 will in fact be very similar to one interpretation of the dreaded X in Zope X3: a version of Zope 3 that's backwards compatible with Zope 2. I'm skeptical about ever getting this done in revolution style development, and holding it up as the future will prompt remarks like When is Zope 5 going to be done? while nobody is actually doing anything about it. This is very very bad marketing. I really really want to avoid a repeat of history here... Meanwhile, I think the current path gets us to a future where the difference between Zope 2 and Zope 3 will become less, and it will be more and more possible to write Zope 3 applications in Zope 2, and more and more Zope 2 pieces will be replaced with pieces from Zope 3. This vision has been sold to the community already and we're on track. So, my proposal would be to tone down the vision to what we have already: a co-evolving Zope 3 and Zope 2, with Zope 2 following and Zope 3 leading (or Zope 2 driving Zope 3 forward, however you want to see it). No renaming necessary. No change of course necessary. Zope 2 can stick to Zope 2 features as long as necessary so there's no rush to replicate Zope 2 functionality in Zope 3 any time soon. At the same time, Zope 2 requirements can drive the evolution of Zope 3. I know I sound conservative here, but I'm actually happy with the way things are working now. Let's not fix what isn't broken. We can make incremental steps to making it better, and I'm glad people are starting to understand the ideas behind Five, but I don't see the need for a change of direction. 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: [Zope3-dev] Re: [Zope-dev] Re: Two visions
Martijn Faassen wrote: Philipp von Weitershausen wrote: [snip] I would vote for spelling out Zed (which would also be a little easier to google but might create trademark problems). The namespace package could either be 'z' or 'zed'. Then again, I really should take Jim's side and stay out of naming decisions. Let's please not have a naming discussion again. I think renaming Zope 3 is really bad marketing myself and naming discussions mostly a waste of time... Regards, Martijn please, not Z, it is an oscar-winning film from the 70's about political corruption, military coup d'état, .. http://www.bbc.co.uk/bbcfour/cinema/features/z.shtml /JM ___ 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: [Zope3-dev] Re: [Zope-dev] Re: Two visions
On Tuesday 28 February 2006 07:22, Martijn Faassen wrote: I don't see how we need a new vision. This has been the vision (evolution, not revolution) that I've been carrying out with Five for the last few years and thanks to a lot of contributions by a large range of developers, we've been making it work. Can't we just keep going on the way we've been going then? +1, I totally agree. 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 )
Re: [Zope-dev] Zope 2.9 releases for Windows?
On Mon, Feb 27, 2006 at 08:23:16PM +, Chris Withers wrote: | Sidnei da Silva wrote: | Basically you need (a properly licensed) VC 7, and Python 2.4.2 | installed. Not much else has changed. Unfortunately we haven't gotten | around setting up VC 7 here. | | Okay, once I have those two, then what do I do to end up with a binary | distro for Zope 2.9.1? Run 'inst/WinBuilders/buildout zope'. Ah, you need Inno 5.x too. See inst/WinBuilders/README.txt for the complete instructions. -- Sidnei da Silva Enfold Systems, LLC. http://enfoldsystems.com ___ 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: [Zope3-dev] Two visions
On Tuesday 28 February 2006 03:58, Shane Hathaway wrote: Unfortunately, this discussion is too fuzzy for me to understand exactly what's being proposed. How about something concrete: will the Zope 3 in vision #2 have a ZMI, and will typical ZODB objects have a __parent__ and __name__? (Either yes or no is fine, but maybe or sometimes is a lot harder to interpret.) I agree. 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: [Zope3-dev] Two visions
Martijn Faassen wrote: So, my proposal would be to tone down the vision to what we have already: a co-evolving Zope 3 and Zope 2, with Zope 2 following and Zope 3 leading (or Zope 2 driving Zope 3 forward, however you want to see it). No renaming necessary. No change of course necessary. Zope 2 can stick to Zope 2 features as long as necessary so there's no rush to replicate Zope 2 functionality in Zope 3 any time soon. At the same time, Zope 2 requirements can drive the evolution of Zope 3. An emphatic +1. -- Benji York Senior Software Engineer 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: Two visions
Stephan Richter wrote: 1) Our current vision (AFAIK) is that Zope 3 will eventually replace Zope 2 2) In an alternate vision, Zope 2 evolves to Zope 5. As you probably know already, I am -1 on the second proposal, since it will disallow us to finally get rid of the old Zope 2 code. Either way we're not getting rid of the old Zope 2 code for a while. Anyways, since I think the vision has too littel technical detail for my taste, I would really like to see some prototyping before I give my final vote. I'm not really sure how you think we should do that... Prototyping an entire vision is a lot of work ;) I just want to be ensured that I do not have to deal with additional overhead (i.e. learn Zope 2 again), but can develop Zope 3 applications as I like it. I really don't think you'd have to learn Zope 2 again. As I noted in my short response to Jim's proposal, a) you'll be able to continue to create web apps with just the Zed components. There won't be a zed.app or so, but zed.publisher would be the WSGI-capable publishing machinery that you can use to (given appropriate publication objects or whatever will be there in the future) publish objects using views and whatever we have not right now. b) Zope 5 will use zed functionality all over the place. Our current efforts with Five are providing a good deal of this already and we're going to continue with that. Having to learn Zope 2 all over again will probably not mean the same thing in the context of Zope 5 as it does right now. Philipp ___ 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: Two visions
Martijn Faassen wrote: I will also note that just because Zope 2 won't die, it doesn't mean we shouldn't clean it up. Eventually, Zope should mostly be reusing things from Zed. +sys.maxint I think this will be the way we get a real forward migration path for an awful lot of us who are still using Zope 2 today, and expect to continue doing so. We may or may not ever port to zope 3, whatever that will mean in the future. More likely we will just incrementally improve and clean up our applications, just as Zope 2 itself will be getting incrementally better and cleaner. We'll have to address deprecation warnings at each upgrade, but at no point will we be forced to do a complete rewrite. And along the way, we'll be gradually getting access to more and more nifty features. I don't see how we need a new vision. This has been the vision (evolution, not revolution) that I've been carrying out with Five for the last few years and thanks to a lot of contributions by a large range of developers, we've been making it work. Can't we just keep going on the way we've been going then? In many ways, that's precisely the idea. However, I agree with Jim when he says that we currently have a Zope 2 wanting to become like Zope 3 and a Zope 3 wanting to get all that what Zope 2 has. That'll leave us with two Zopes for a while. Zope 3 is exploding into several bits and pieces. That is good. The question is whether one of those (larger) pieces will also be an app server or whether one app server that evolves just the way we've been evolving it since Zope 2.8 is enough. I think focusing on one app server and a dedicated set of libraries would be a good alternative to two concurring app servers. Philipp ___ 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: Two visions
Philipp von Weitershausen wrote: Martijn Faassen wrote: [snip] I don't see how we need a new vision. This has been the vision (evolution, not revolution) that I've been carrying out with Five for the last few years and thanks to a lot of contributions by a large range of developers, we've been making it work. Can't we just keep going on the way we've been going then? In many ways, that's precisely the idea. However, I agree with Jim when he says that we currently have a Zope 2 wanting to become like Zope 3 and a Zope 3 wanting to get all that what Zope 2 has. I don't see how that is a however. This situation is exactly right in my opinion. That'll leave us with two Zopes for a while. Yes, having two Zopes is in my opinion completely unavoidable for the forseeable future. Zope 3 is exploding into several bits and pieces. That is good. The question is whether one of those (larger) pieces will also be an app server or whether one app server that evolves just the way we've been evolving it since Zope 2.8 is enough. I'm not sure what you mean here. I expect Zope 3 to keep the pieces it has right now, including the appserver bits. Nobody is proposing we throw away code, right? If someone has the time to replace Zope 2's appserver with what's in Zope 3, then that would be good and we'll see that happen some Zope 2 releases in the future. Calling that Zope 5 is not going to make it happen any faster. explosion, whether Zope 3 is going to be managed as a number of components or as a single story doesn't matter much for this. Presumably we'll still have Zope 3 releases that I can run, say, the documentlibrary on. For the component integrators (but that's mostly the Zope core developers) things will change. From the developer's perspective, and the deployer's perspective using Zope not that much will change - you'll still install Zope 2 or Zope 3. Perhaps the way you install it is different, but a Zope developer or deployer would typically still end up installing something that's called Zope. I think focusing on one app server and a dedicated set of libraries would be a good alternative to two concurring app servers. I don't see how else we can get there than by the route we've been taking: continuous evolution with small steps. Saying we'll have Zope 5 in the future which will include both still means we need to get there. I don't see how introducing a new name in the mix is going to help anyone, and I think in fact it will hurt. We make a commitment we'll do something, but nobody is actually signing up to actually do it in the foreseeable future. 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: [Zope3-dev] Re: Two visions
--On 28. Februar 2006 16:06:55 +0100 Philipp von Weitershausen [EMAIL PROTECTED] wrote: I think focusing on one app server and a dedicated set of libraries would be a good alternative to two concurring app servers. +1 -aj pgpe9Th17c7O9.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: [Zope3-dev] Re: Two visions
Philipp von Weitershausen wrote: Stephan Richter wrote: 1) Our current vision (AFAIK) is that Zope 3 will eventually replace Zope 2 2) In an alternate vision, Zope 2 evolves to Zope 5. As you probably know already, I am -1 on the second proposal, since it will disallow us to finally get rid of the old Zope 2 code. Either way we're not getting rid of the old Zope 2 code for a while. Yes, the Zope 2 codebase is going to stay. It isn't going to stay for everybody in all Zope related projects, and it's already quite doable to keep Zope 2 in the background while developing new software for Zope 2, but the codebase isn't going to disappear. This doesn't mean it should be there for people who are building new applications. [snip] I really don't think you'd have to learn Zope 2 again. As I noted in my short response to Jim's proposal, a) you'll be able to continue to create web apps with just the Zed components. There won't be a zed.app or so, but zed.publisher would be the WSGI-capable publishing machinery that you can use to (given appropriate publication objects or whatever will be there in the future) publish objects using views and whatever we have not right now. b) Zope 5 will use zed functionality all over the place. Our current efforts with Five are providing a good deal of this already and we're going to continue with that. Having to learn Zope 2 all over again will probably not mean the same thing in the context of Zope 5 as it does right now. Could you please stop using a new name for Zope 3 or the zope package? You can explain this perfectly well using the existing, well established names. I'll rewrite it to demonstrate this: a) you'll be able to continue to create web apps with just the Zope 3 components. There won't be a zope.app anymore, but zope.publisher would be the WSGI-capable publishing machinery that you can use to (given appropriate publication objects or whatever will be there in the future) publish objects using views and whatever we have not right now. This is a proposal for the evolution of Zope 3. Zope 3 is already going in this direction. b) Zope 2 will use Zope 3 functionality all over the place. Our current efforts with Five are providing a good deal of this already and we're going to continue with that. Having to learn Zope 2 all over again will probably not mean the same thing in the context of Zope 2 + Five as it does right now. This is what we are actually doing with Zope 2 right now, starting with Five on top of Zope 2.7, and continued further with Zope 2.8, Zope 2.9 and presumably Zope 2.10 and beyond. It's nothing new, and it will take more effort and time to get further. Renaming this to Zed or Zope 5 is not going to make anyone's life simpler or easier, nor will it make any development go faster than it does now. Instead we're going to confuse everybody with completely uncalled for name changes. 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: [Zope3-dev] Re: Two visions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Martijn Faassen wrote: Max M wrote: Jim Fulton wrote: 2) In an alternate vision, Zope 2 evolves to Zope 5. Zope 2 is complicated! It has too many layers of everything. The reason for Zope 3 is to make it simpler for developers. Therefore I believe that any succesfull strategy would require Zope 3 to be usable completely without all the Zope 2 layers. If Zope 3 becomes just another layer on top of Zope 2 - CMF - Plone it will not reduce complexity, as any developer would still need to learn the entire stack. Wherever practical, Zope 2 technologies should be rewritten to Zope 3 technologies to remove layers from the stack. I think these are good points. Five runs the risk of being yet another layer on a stack like Plone, but Five also gives the chance of us stripping off these layers and replacing it with something cleaner, and at the same time Five is giving an impulse to Zope 3 development as things slowly get ported to Zope 3 or written in a Zope 3 style. The Five project has the right attitude to deal with such integration issues. We have been quite successful: In Zope 2.9 it's possible to build modern Zope 3-style apps, using formlib and sqlos and so on (we've done it). In this vision, the Zope 3 project should stay where it is and push things forward. That doesn't mean Five should be ignored by Zope 3 developers, but it should be compartmentalized in people's minds. Zope 3 does innovation, Five does integration, and then the big codebases can move forward using both. I think the other major point is the door #2 proposal takes pressure off of Zope3: under that regime, Zope3 does not need to grow all the features present in Zope2, which door #1 *does* imply. Tres. - -- === Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFEBHBA+gerLs4ltQ4RAs22AJ44rNQIZB9HCt1S6fp7s36Hq68MNgCgv37w PHiyspa7XahkllCJmueEU5w= =ZyJQ -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 )
Re: [Zope3-dev] Re: [Zope-dev] Two visions
On Mon, 2006-02-27 at 17:06 +0100, Lennart Regebro wrote: OK, some initial, fuzzy comments: ... You are thinking about things like TTW development and such? Among other things. Zope 2 is more mature than Zope 3 in a lot of areas. WebDAV and process management are a couple of examples that occur to me off the top of my head. ... - Zope 5 will be the application server generally known as Zope. It will be backward compatible (to the same degree that Zope 2 releases are currently backward compatible with previous Zope 2 releases) with Zope 2. Zope 5 will similarly be backward compatible with Zope 3 applications built on top of the current Zope 3 application server. Note that Zope 5 will leverage Zope 3 technologies to allow a variety of configurations, including a Zope 2-like configuration with implicit acquisition and through-the-web development, and a Zope 3-like configuration that looks a lot like the current Zope 3 application server. Maybe, there will be a configuration that allows Zope 2 and Zope 3 applications to be combined to a significant degree. This overwhelms my complexity sensor. :-) Sorry, I'm not sure why. I like the vision of Zope2 becoming a set of extra packages you install for Zope3, to get backwards compatibility. Maybe this is the same as what you call Zope 5, maybe not. I see Zope 5 being a combination of Zope 2 and Zope 3, keeping the best of both. - There wouldn't be confusion about 2 Zopes. This is definitely true... And given some of the discussion over the last month or two, I think this is pretty important. Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ 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: [Zope3-dev] Two visions
On Feb 28, 2006, at 9:30 AM, Benji York wrote: Martijn Faassen wrote: So, my proposal would be to tone down the vision to what we have already: a co-evolving Zope 3 and Zope 2, with Zope 2 following and Zope 3 leading (or Zope 2 driving Zope 3 forward, however you want to see it). No renaming necessary. No change of course necessary. Zope 2 can stick to Zope 2 features as long as necessary so there's no rush to replicate Zope 2 functionality in Zope 3 any time soon. At the same time, Zope 2 requirements can drive the evolution of Zope 3. An emphatic +1. Heh, in retrospect, my I guess we should go with plan 2 post comes off a bit like Marc Antony's speech in Julius Caesar: Friends, Romans, countrymen, lend me your ears; I come to bury Caesar, not to praise him; The evil that men do lives after them, The good is oft interréd with their bones, So let it be with Caesar. ...Then Antony goes on to praise Caesar. :-) I'm also +1 on Martijn's approach: let's keep Zope 3 around, and stay the course. Also, On Feb 28, 2006, at 10:06 AM, Philipp von Weitershausen wrote: I think focusing on one app server and a dedicated set of libraries would be a good alternative to two concurring app servers. ...if the single app server is based on acquisition, __bobo_traverse__ and friends, objectValues and friends, ZCatalog, and so on, I'd rather have two, thanks: at least I can have one I like. Gary___ 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: [Zope3-dev] Re: Two visions
On 2/28/06, Tres Seaver [EMAIL PROTECTED] wrote: I think the other major point is the door #2 proposal takes pressure off of Zope3: under that regime, Zope3 does not need to grow all the features present in Zope2, which door #1 *does* imply. I still would like to know wich these missing features are. Unless it's TTW development, which, as mentioned, I think should be viewed as a separate set of packages. Most Zope3 developers do not want or need it. -- Lennart Regebro, Nuxeo http://www.nuxeo.com/ CPS Content Management http://www.cps-project.org/ ___ 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: [Zope3-dev] Re: [Zope-dev] Two visions
Jim Fulton wrote: [snip] I see Zope 5 being a combination of Zope 2 and Zope 3, keeping the best of both. I think we already have Zope 5, and it's called Zope 2.9. Perhaps I'm wrong. If so, how does Zope 5 differ from Zope 2.9? 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: [Zope3-dev] Re: Two visions
Tres Seaver wrote: [snip] In this vision, the Zope 3 project should stay where it is and push things forward. That doesn't mean Five should be ignored by Zope 3 developers, but it should be compartmentalized in people's minds. Zope 3 does innovation, Five does integration, and then the big codebases can move forward using both. I think the other major point is the door #2 proposal takes pressure off of Zope3: under that regime, Zope3 does not need to grow all the features present in Zope2, which door #1 *does* imply. What I'm confused about is that we've already solidly gone through door #2 a while ago. Since we went through door #1 once people started developing pure Zope 3 applications, I don't see the either-or of these visions. Sure, there is pressure on Zope 3 for features that aren't there yet. Overall I think that's good. The pressure shouldn't be artificial and just a point by point comparison with Zope 2, but if actual projects need a feature in Zope 3 they can start building it and that's only good. What is new here? What is the concrete proposal besides juggling around names confusing everybody? 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] Two visions
Martijn Faassen wrote: I see Zope 5 being a combination of Zope 2 and Zope 3, keeping the best of both. I think we already have Zope 5, and it's called Zope 2.9. I'd rather say it's called Zope 2.15 or something :). Philipp ___ 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: [Zope3-dev] Re: [Zope-dev] Two visions
On 2/28/06, Jim Fulton [EMAIL PROTECTED] wrote: Zope 2 is more mature than Zope 3 in a lot of areas. WebDAV and process management are a couple of examples that occur to me off the top of my head. Ah, and here I got an answer to the question I just posted. :) Much of Zope2 maturity is there in a thorougly non-reusable way. We won't get WebDAV support for Zope3 objects by including some old crufty Zope2 code. This means that for most of these features, we will have to build something new anyway. This overwhelms my complexity sensor. :-) Sorry, I'm not sure why. Not the text, the result. :) Zope2 + Zope3 + Five is a MASSIVE complexity, and I think it is important that we don't make things more complex than necessary. I think the best vision for the Zope future is to have: 1. A set of basic non-webby techniques. This is ZODB, zope.interfaces, zope.components and all that. 2. An object publisher, that publishes the ZODB objects built with the techniques in point 1, including user handling, security, traversal, yadayadaydad. This would be known as Zope3. 3. An extension to Zope3 that includes the shim to support two modules called Products, all the old default products, and the support to make the Zope3 publisher publish these type of objects. In other words, a Zope2 backwards compatibility product. The steps to get here involves stuff like replacing Zope2s security with Zope3 security, replacing Zope2s publisher with Zope3s publisher, and so on, until Zope2 is almost nothing more than a set of products. 4. Other extension sets for Zope3, like z3ecm, for making ecm systems, and z3ttw for through-the-web development. Now, there may be something that is obviously unfeasable with all this. But it sure is much less overwhelmingly complex than some sort of Zope5. I see Zope 5 being a combination of Zope 2 and Zope 3, keeping the best of both. Doesn't that mean we only keep Zope3? ;-) And given some of the discussion over the last month or two, I think this is pretty important. Yup. -- Lennart Regebro, Nuxeo http://www.nuxeo.com/ CPS Content Management http://www.cps-project.org/ ___ 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: [Zope3-dev] Re: [Zope-dev] Two visions
On Tue, 2006-02-28 at 17:29 +0100, Martijn Faassen wrote: Jim Fulton wrote: [snip] I see Zope 5 being a combination of Zope 2 and Zope 3, keeping the best of both. I think we already have Zope 5, and it's called Zope 2.9. Perhaps I'm wrong. If so, how does Zope 5 differ from Zope 2.9? Are you kidding? Zope 5 will be backward compatible with Zope 2 and Zope 3. It will allow configurations that look a lot like Zope 3. It will have the best of both systems, and improvements to both. It is where we put all of out app-server efforts. Among other things, it will have Zope 3's publisher and security model. It will provide support for non-developers much the way Zope 2 does now, but with better solutions that ZClasses. And, it will allow us to cleanly separate the efforts on an application server, from out work on widely usable components. Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ 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: [Zope3-dev] Two visions
Gary Poster wrote: [snip] On Feb 28, 2006, at 10:06 AM, Philipp von Weitershausen wrote: I think focusing on one app server and a dedicated set of libraries would be a good alternative to two concurring app servers. ...if the single app server is based on acquisition, __bobo_traverse__ and friends, objectValues and friends, ZCatalog, and so on, I'd rather have two, thanks: at least I can have one I like. I can see where Philipp is coming from: yes, it would be good to collapse the Zope 2 and Zope 3 communities into one if that frees up more development resources and lets us do less duplicate work. This cannot however be done by big steps or mandate or changing names, and this is where I think I disagree with Philipp somewhat. We're on the right track already. The communities are merging into a single community. Just compare today with the situation just one year ago - massive changes everywhere, and positive ones. Merging communities can be done by making it easier for people from the communities to work together (for instance by working on Five) and by evangelizing (you can use Zope 3 in Zope 2, today). It's fairly subtle work and it takes a long time. Philipp is doing great on all these fronts and without him Five wouldn't be where it is today. I just don't understand how the current zed/Zope 5 proposals would make everything go faster or be easier or be clearer... 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] Two visions
Philipp von Weitershausen wrote: Martijn Faassen wrote: I see Zope 5 being a combination of Zope 2 and Zope 3, keeping the best of both. I think we already have Zope 5, and it's called Zope 2.9. I'd rather say it's called Zope 2.15 or something :). Seriously, we are developing applications that use huge chunks of Zope 3 technology and are portable to Zope 3 in a short time right now, on Zope 2.9. Zope 2.10 and further will make it all even better of course, but let's not forget what we already have right now. It's a lot. 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: SVN: Zope/trunk/lib/python/OFS/Traversable.py using startswith()
Why? x[0] is much faster than x.startswith().
Or do you expect to have empty path components?
Florent
Andreas Jung wrote:
Log message for revision 65598:
using startswith()
-=-
Modified: Zope/trunk/lib/python/OFS/Traversable.py
===
--- Zope/trunk/lib/python/OFS/Traversable.py2006-02-28 16:59:49 UTC (rev
65597)
+++ Zope/trunk/lib/python/OFS/Traversable.py2006-02-28 17:17:12 UTC (rev
65598)
@@ -173,7 +173,7 @@
name = path_pop()
__traceback_info__ = path, name
-if name[0] == '_':
+if name.startswith('_'):
# Never allowed in a URL.
raise NotFound, name
--
Florent Guillaume, Nuxeo (Paris, France) Director of RD
+33 1 40 33 71 59 http://nuxeo.com [EMAIL PROTECTED]
___
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-Checkins] SVN: Zope/trunk/lib/python/OFS/Traversable.py using startswith()
On 2/28/06, Andreas Jung [EMAIL PROTECTED] wrote:
-if name[0] == '_':
+if name.startswith('_'):
Just a question: Is this only a matter of stylistic changes, or is
there some, like, speedup involved?
--
Lennart Regebro, Nuxeo http://www.nuxeo.com/
CPS Content Management http://www.cps-project.org/
___
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: [Zope3-dev] Re: [Zope-dev] Two visions
Jim Fulton wrote: On Tue, 2006-02-28 at 17:29 +0100, Martijn Faassen wrote: Jim Fulton wrote: [snip] I see Zope 5 being a combination of Zope 2 and Zope 3, keeping the best of both. I think we already have Zope 5, and it's called Zope 2.9. Perhaps I'm wrong. If so, how does Zope 5 differ from Zope 2.9? Are you kidding? No, I'm not kidding. Zope 2.9 is the closest thing to Zope 5 that we have today, that people can work with. Zope 2.10 will hopefully be closer too, and so on. Zope 5 will be backward compatible with Zope 2 and Zope 3. It will allow configurations that look a lot like Zope 3. Sounds like the original vision of Zope 3 without the X. I thought we never got around to developing this stuff the last time. What changed? It will have the best of both systems, and improvements to both. Zope 2.9 has a lot of two systems. It doesn't have improvements to both, as we see that's clearly the mandate of the Zope 3 project, not of the Zope 2 or Five projects. We improve Zope 2 by taking bits of Zope 3. Mixing these things up into a Zope 5 puddle risks mixing it all up a lot. It is where we put all of out app-server efforts. Among other things, it will have Zope 3's publisher and security model. It will provide support for non-developers much the way Zope 2 does now, but with better solutions that ZClasses. And, it will allow us to cleanly separate the efforts on an application server, from out work on widely usable components. When do you think all this work will be finished? Who will work on it? What do we do in the mean time? What do we tell people? Do you really feel comfortable promising all that? How are we not on the course to reaching this featureset, eventually, anyway? I don't see how *saying* what Zope 5 will contain will make it *exist* any time sooner. These sound like useful evolution proposals for Zope 2 and Zope 3 to me... The current story of Zope 2, Five and Zope 3 gets us in the right direction (Zope 5, if you want to call it that, though I would definitely want to introduce yet another name in the mix), step by step. We don't promise too much to people. We don't raise the wrong expecations anymore. Everyone in the community is on board. We are already doing the work that's required to reach the ideal of Zope 5. You could rename Zope 2.10 to Zope 5.0, but I don't see what good that would do except to confuse people. It won't contain the features you list unless someone actually does all that work. The alternative is to put Zope 5 in the nebulous future when all the work you list is done, and it'll be just like our mythical Zope 3 without the X then - confusing people and raising the wrong expectations. 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] [JOB] Python/Zope Dev, Rockville, MD | 60-100k | Relo OK
Python/Zope Dev, Rockville, MD | 60-100k | Relo OK Job Description: The main part of our development will take place in our Rockville, MD office. We are looking for a developer who will work from this office. The envisioned services are web applications and thorough knowledge and expertise in developing these kinds of applications is essential. We seek core competencies in web application development, both on the client side creating rich internet applications (RIA/AJAX) and on the server side of the application. Fine tuning and scalability expertise is of interest. Next to technical and computer science expertise, the developer should be comfortable in a multi-disciplinary context and should be able to explain technical issues to smart but not-so-technical colleagues. Familiarity with the biomedical domain and language is a plus. Qualifications: Python / Zope / Java / Object Oriented Programming, HTML / CSS / XML / JavaScript / Rich Internet Applications (RIA / AJAX), Linux / Windows. Candidates should be willing to work in the MD, VA, D.C. area and be authorized to work in the USA. Relocation assistance provided. This is an on-site, salaried position in Rockville, MD. Please no offshore or telecommuters. To be considered, please submit your resume, a paragraph highlighting your Python / Zope experience and your salary requirements to [EMAIL PROTECTED] Python/Zope Jobs: http://groups.yahoo.com/group/pythonzopejobs Open Source Jobs: http://groups.yahoo.com/group/opensourcejobs -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.375 / Virus Database: 268.1.1/270 - Release Date: 2/27/2006 ___ 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: [Zope3-dev] Re: [Zope-dev] Two visions
On Feb 28, 2006, at 12:33 PM, Martijn Faassen wrote: Jim Fulton wrote: Are you kidding? No, I'm not kidding. +1 to what Martijn said in this email (not quoting the whole thing to save precious bandwith). ___ 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 Linux zc-buildbot
The Buildbot has detected a failed build of Zope trunk 2.4 Linux zc-buildbot. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 3389 Blamelist: andreasjung,ctheune BUILD FAILED: failed test 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] 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: 3389 Blamelist: andreasjung,ctheune BUILD FAILED: failed test 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 )
Re: [Zope-dev] Inhibit URL-traversal
Dario Lopez-Kästen wrote at 2006-2-13 08:06 +0100: ... It can -- with some difficulties: Templates and scripts are called because they define index_html as None. If you give a template or script a non-None index_html, then this object will be called instead of the template/script. I see. Is this possible to do on FS-based scripts/templates? It is, but you have to work a bit: You derive your own classes from the original ones and provide an appropriate index_html definition. You register your classes to handle the appropriate extensions. Note, that the last registration wins over previous ones. You might need to force an import of the module/s performing the other registration/s in your module to ensure that your registration is indeed the last one. -- Dieter ___ 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: 3396 Blamelist: andreasjung,chrism,nathan,sidnei BUILD FAILED: failed failed slave lost 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] ZClass Replacement Volunteer
I am considering volunteering to rewrite ZClasses. Who do I speak to? Chris ___ 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-Checkins] SVN: Zope/trunk/lib/python/OFS/Traversable.py using startswith()
Lennart Regebro wrote:
-if name[0] == '_':
+if name.startswith('_'):
Just a question: Is this only a matter of stylistic changes, or is
there some, like, speedup involved?
In general, using str.startswith and str.endswith is a failsafe because
''.startswith('_') simply returns False, ''[0] == '_' raises a KeyError.
So, if you really know that your string has at least the length you're
trying to test it against, using the index/slice notation is ok. In all
other cases I would prefer str.startswith and str.endswith.
Philipp
___
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: ZClass Replacement Volunteer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Christopher Lozinski wrote: I am considering volunteering to rewrite ZClasses. Who do I speak to? You're in the right place. The usual mode for such a thing is to draft a proposal, outlining the risks and proposing a solution, and then to submit it for review here. Tres. - -- === Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFEBLSy+gerLs4ltQ4RAiMVAJ95d4LBKq7q2AmtPdgwbfremW5kogCgjCKB wJ0doFwam9kko9EPNfpoFjc= =tIf2 -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 )
Re: [Zope-dev] ZClass Replacement Volunteer
--On 28. Februar 2006 10:31:04 -1000 Christopher Lozinski [EMAIL PROTECTED] wrote: I am considering volunteering to rewrite ZClasses. Who do I speak to? You can basically start this as your own project. Starting Zope 2.10 are officially deprecated. Any new development for Zope 2 and 3 must follow the common rules (ZPT, unittests, styleguides). -aj pgplwxpFyLR0x.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 )
Re: [Zope-dev] Re: [Zope-Checkins] SVN: Zope/trunk/lib/python/OFS/Traversable.py using startswith()
--On 28. Februar 2006 21:41:24 +0100 Philipp von Weitershausen
[EMAIL PROTECTED] wrote:
Lennart Regebro wrote:
-if name[0] == '_':
+if name.startswith('_'):
Just a question: Is this only a matter of stylistic changes, or is
there some, like, speedup involved?
In general, using str.startswith and str.endswith is a failsafe because
''.startswith('_') simply returns False, ''[0] == '_' raises a KeyError.
So, if you really know that your string has at least the length you're
trying to test it against, using the index/slice notation is ok. In all
other cases I would prefer str.startswith and str.endswith.
But Lennart is right that in this case name should in general never be an
empty string and in addition startswith() is in this case 100% slower
than using slicing.
-aj
pgpiYM5OXCXJu.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 )
Re: [Zope-dev] Re: [Zope-Checkins] SVN: Zope/trunk/lib/python/OFS/Traversable.py using startswith()
But Lennart is right that in this case name should in general never be an empty string and in addition startswith() is in this case 100% slower than using slicing. No, I'm not, Florent is. I just asked. :-) -- Lennart Regebro, Nuxeo http://www.nuxeo.com/ CPS Content Management http://www.cps-project.org/ ___ 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: Two visions
Martijn Faassen wrote: I think focusing on one app server and a dedicated set of libraries would be a good alternative to two concurring app servers. ...if the single app server is based on acquisition, __bobo_traverse__ and friends, objectValues and friends, ZCatalog, and so on, I'd rather have two, thanks: at least I can have one I like. I can see where Philipp is coming from: yes, it would be good to collapse the Zope 2 and Zope 3 communities into one if that frees up more development resources and lets us do less duplicate work. This cannot however be done by big steps or mandate or changing names, and this is where I think I disagree with Philipp somewhat. I don't think we disagree here. Like you, Martijn, I believe in evolution. I find the idea of Zope 3 not having to catch up with Zope 2 very appealing. We can continue to evolve Zope 2 instead. And yes, Gary, this means we will eventually get rid of or provide alternatives to crufty Zope 2 APIs. Zope 2.9 has already deprecated one particular Zope 2 API (the event stuff), I expect upcoming versions to do more like that. We're on the right track already. The communities are merging into a single community. Just compare today with the situation just one year ago - massive changes everywhere, and positive ones. You're absolutely right. So focusing the effort in the app server development department seems only logical. I just don't understand how the current zed/Zope 5 proposals would make everything go faster or be easier or be clearer... It just articulates in papal words what has been going on so far and what might be the future for Zope 3 vs. Zope 2. Leaving aside Jim's naming suggestion, door #2 is a clear vision for the continuation of Zope 2 and Zope 3 in a common platform. It is nothing that is done today or tomorrow. There no immediate speed ups in development, only long-term ones, hopefully. I spend a fair amount of time on Five development just to reproduce Zope 3 features in Zope 2. On the other hand, a lot of people spend a fair amount of time on bringing Zope 2 features to Zope 3. Why couldn't these efforts be consolidated? Will the consolidation product (Zope 5) be backward compatible with Zope 2.9 as we have it now? Probably not, there's an evolution path to it. Will we be able to evolve to it? I certainly think so. Perhaps it has been misunderstood, but Jim's door #2 proposal doesn't really make any technical claims nor promises, it is just a vision to focus efforts in certain things. It's an effort roadmap. And it is actually very close to the lines of thinking that let you, Martijn, (and eventually myelf) start or embrace the Five project. I see it as the logical Zope roadmap resulting from the Five efforts. In a way we should be happy that the Five effort showed that Zope 2 is still important but is also willing to evolve. By the way, I think Terry Hancock made some very good points regarding marketing issues. However, as a core developer, I would tend my vision is blurred on this particular issue :). Philipp ___ 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] Squishdot on Zope 2.9.X with Python 2.4.2
On 28 Feb 2006, at 07:26, Dennis Allison wrote: Are there any known compatibilty problems? -d I guess a more appropriate question would be Has anyone ever done this?, with a likely answer of no ;) Chris might have tried it. jens ___ 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] Squishdot on Zope 2.9.X with Python 2.4.2
Yup, it does seem a bit strange, but I'd rather not maintain multiple versions of Zope if I can avoid it. And I have a user that wants to experiment with and/or use Squishdot. On Tue, 28 Feb 2006, Jens Vagelpohl wrote: On 28 Feb 2006, at 07:26, Dennis Allison wrote: Are there any known compatibilty problems? -d I guess a more appropriate question would be Has anyone ever done this?, with a likely answer of no ;) Chris might have tried it. jens ___ 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 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] product security changes from 2.8 to 2.8.5 ?
Ed Colmar wrote: Now I see get a name error when trying to access it. *Error Type: NameError* *Error Value: name 'send_password_reminder' is not defined If you gave us the whole traceback we might have a clue how to help you... Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ 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] Squishdot on Zope 2.9.X with Python 2.4.2
Dennis Allison wrote: Yup, it does seem a bit strange, but I'd rather not maintain multiple versions of Zope if I can avoid it. And I have a user that wants to experiment with and/or use Squishdot. Try it and see. I personally haven't, but I'd be interested in fixing any problems that do arise... Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ 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] Memory Leak Debugging
Hi All, A few weeks ago I posted this message to the list but we still haven't resolved our memory leak, mainly because we have no idea where to look. So having trawled around a few forums I decided to install the LeakFinder product onto our development server and click around a little watching the refcounts. Here I noticed that Products.Silva.Image.Image DateTime.DateTime.DateTime had the largest number of references. So following the LeakFinder instructions I attempted to patch each of these classes. I started with the Products.Silva.Image.Image class and continued to click around to return some results, unfortunately this never returned any results at all so that wasn't much help. Next I patched the DateTime.DateTime.DateTime class which returned a huge amount of information on the results tab. So I'm now hoping someone could help me in deciphering these results and explain what exactly should I be looking for here? And it would also be useful to know why the Products.Sivla.Image.Image class doesn't return any results at all. Hope someone can help. Jon -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jonathan Bowlas Sent: 15 February 2006 11:49 To: zope@zope.org Subject: RE: [Zope] Memory Leak Debugging Hi All, We're having serious problems with performance running Silva CMS on Zope 2.7.8-final, python 2.3.5, linux2 set up on a machine with 2.5GB RAM. There are currently only about 65 users and around 2000 documents in the CMS but it seems to run for a week, then the RAM fills up and crashes so we have to restart the server manually. The Zope logs aren't much help as I enquired on the Zope list and their response was we need more RAM. But surely 2.5GB is enough. I've also checked Control_Panel/DebugInfo for any refcounts with significant jumps and Products.Silva.Image.Image seems to be the culprit: 11.32am 11.36am Products.Silva.Image.Image 56203 58153 +1950 Acquisition.ImplicitAcquirerWrapper 44825 45151 +326 So we've tried to figure out which kind of request triggers these refcount jumps by creating a separate instance with a very small ZODB Cache (so it gets filled up soon), and clicked around a little, watching the refcounts but we cannot seem to replicate it. So basically this is a plea for help from an expert Zope debugger who can assist us in finding the source of the problem so we can resolve it. Or alternatively someone who can give us a set of instructions that we can follow that will enable us to locate the problem, I've googled it and there are no clear answers. FYI we have the following products installed on our Zope instance. Annotations 0.4.3 BTreeFolder2-1.0.1 DocFinderTab (0.5.2) External Method-1-0-0 FileSystemSite 1.4.2 Formulator 1.10 Groups 0.4 IssueTrackerProduct (0.6.13) LDAPUserFolder (2.3) MIMETools MailHost-1-3-0 OFSP-1-0-0 PageTemplates-1-4-0 ParsedXML 1.4 PlacelessTranslationService (1.0) PluginIndexes ProxyIndex 1.2 PythonScripts-2-0-0 Sessions Silva 1.4.1 SilvaBlog 0.4.2 SilvaCustomAutoTOC 0.9 SilvaDocument 1.4.1 SilvaDocumentPatches 1.3b6-1 SilvaExtETHLDAP 0.7 SilvaExternalSources 0.10.3 SilvaMetadata 0.10 SilvaNewsNetwork 2.0 SilvaReferenceChecker 0.2 SilvaStylesheets 0.6.2 SilvaUCLAttributes 0.7 - (A UCL product*) Silva UCL Gallery 0.1 - (A UCL product*) SilvaUCLSubjectAudienceFilters 0.6 - (A UCL product*) SilvaViews 0.11 SiteAccess-2-0-0 SiteErrorLog Sprout 0.6.2 StandardCacheManagers-1-1-0 TemporaryFolder Transience Tropos (1.9.12) XMLWidgets-Pluggable 0.13 (CVS/UNRELEASED) ZCTextIndex ZCatalog-2-2-0 ZGadflyDA ZMySQLDA 2.0.8 ZODBMountPoint ZOracleDA ZReST (1.1) ZSQLMethods Zope Tutorial 1.2 kupu 1.3.2 z3locales 0.1 If you require any further information do not hesitate to ask. Hope someone can help. Jon Bowlas University College London ___ 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 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] Squishdot on Zope 2.9.X with Python 2.4
OK, I'll do that. My post was to learn whether I was walking into a mine field... On Tue, 28 Feb 2006, Chris Withers wrote: Dennis Allison wrote: Yup, it does seem a bit strange, but I'd rather not maintain multiple versions of Zope if I can avoid it. And I have a user that wants to experiment with and/or use Squishdot. Try it and see. I personally haven't, but I'd be interested in fixing any problems that do arise... Chris -- ___ 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] Squishdot on Zope 2.9.X with Python 2.4
On Tuesday 28 February 2006 07:10, Dennis Allison wrote: OK, I'll do that. My post was to learn whether I was walking into a mine field... In my experience, unless you are using Zope 3 technologies in Zope 2 (via Five) there is very little difference from a Product development point of view between Zope 2.8 and 2.9. Of course it's possible, but unlikely, that a product uses some no longer supported features from Python. Also, the triggering of manager_after* hooks now happens through events in 2.9 which can have some unexpected consequences in certain cases. I, however, know nothing about Squishdot. Alec ___ 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] ac_acquire error happens after inheriting from Folder
All,
I have a class called Contact
that is now inheriting from Folder. After I did this, I get the following error
when attempting to add a new Contact:
Exception Type
AttributeErrorException Value aq_acquire
Traceback (innermost
last):
* Module
ZPublisher.Publish, line 101, in publish * Module
ZPublisher.mapply, line 88, in mapply * Module
ZPublisher.Publish, line 39, in call_object * Module
Shared.DC.Scripts.Bindings, line 306, in __call__ * Module
Shared.DC.Scripts.Bindings, line 343, in _bindAndExec *
Module Products.PythonScripts.PythonScript, line 323, in
_exec * Module None, line 27, in
validateContact PythonScript at
/validateContact used for /contacts Line
27 * Module Shared.DC.Scripts.Bindings, line 306, in
__call__ * Module Shared.DC.Scripts.Bindings, line 343, in
_bindAndExec * Module Products.PythonScripts.PythonScript,
line 323, in _exec * Module None, line 39, in
addContact PythonScript at /addContact
used for /contacts Line
39 * Module Products.CMS.cmsContact, line 42, in
manage_addContact * Module AccessControl.Role, line 172,
in manage_permission * Module AccessControl.Role, line 82,
in ac_inherited_permissions * Module OFS.ObjectManager,
line 211, in _subobject_permissions
AttributeError:
aq_acquire
I thought it might be due to
not having an __ac_permissions__ in my class definition but that didn't seem to
change anything and Folder already has this so my Contact class should pick up
__ac_permissions__ from Folder. In the above traceback, line 42 in
manage_addContact is this (the part inside the if statement is line 42):
#change permissions based on value of
private
if
private==True:
self.manage_permission('View',['Authenticated','Content
Manager','Manager'])
else:
self.manage_permission('View',acquire=1)
Any ideas would be much
appreciated. The error is clearly related to inheriting from Folder as it wasn't
there before. I just don't know why the error happens.
Thanks,
Tom Palermo
Senior Web
Developer
Constella Group,
LLC
___
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] ZOPE/Python Stellenangebote
[Please excuse this job offer in german language] Gallileus GmbH (Erfurt) sucht Entwickler Wir suchen ab März 2006 einen ZOPE-/Python-Entwickler, sowie einen Webentwickler, beide zur Festanstellung in Erfurt. Zusätzlich suchen wir für die selben Bereiche Praktikanten und studentische Hilfskräfte. Weitere Informationen unter http://www.gallileus.info/about/jobs/ Mit freundlichen Grüssen, Sascha Ottolski -- Gallileus - the power of knowledge Gallileus GmbH http://www.gallileus.info/ Puschkinstraße 1 fon +49-(0)361/541 43 80 99084 Erfurt fax +49-(0)361/541 43 79 [EMAIL PROTECTED] ___ 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] ac_acquire error happens after inheriting from Folder
Palermo, Tom wrote at 2006-2-28 11:25 -0500: I have a class called Contact that is now inheriting from Folder. After I did this, I get the following error when attempting to add a new Contact: Exception Type AttributeError Exception Value aq_acquire Only acquisition wrappers have the aq_acquire method. Looks at if your object were not an acquisition wrapper... -- Dieter ___ 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] Memory Leak Debugging
Jonathan Bowlas wrote at 2006-2-28 13:20 -: ... I've also checked Control_Panel/DebugInfo for any refcounts with significant jumps and Products.Silva.Image.Image seems to be the culprit: 11.32am 11.36am Products.Silva.Image.Image 56203 58153 +1950 Acquisition.ImplicitAcquirerWrapper 44825 45151 +326 Looks as it you would leak acquisition wrappers... This can e.g. happen when you (or some extension product) store acquisition wrappers in REQUEST outside of other or form. Almost surely, other causes (e.g. caching acquisition wrappers) are possible, too. -- Dieter ___ 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] Zope/Plone logon security strategy etc
michael nt milne wrote at 2006-2-28 15:51 +: I'm probably missing something really obvious but am wondering how you actually implement your product on a live plone site. I've got it installed. Do you just customise the login form that comes with the product and use that on the site? I fear you do not understand the essence of HTTP authentication: For any kind of HTTP authentication (whether basic or digest), it is the browser which gathers the login information. Therefore, you do not have a login form (you can customize on the server). Instead, the browser uses its login dialog (which you might customize, if you are using e.g. Mozilla or Firefox, but is usually out of the server's reach). As written in the documentation on my website, DigestAuth currently only contains a DigestAuthCrumbler which works similar to the CookieCrumbler. More precisely: It takes digest auth information, verifies it and (if successful) presents it like basic auth information to the remaining parts of Zope. The CookieCrumbler works very similar: it takes the information from a cookie and presents it like basic auth information to the remaining parts of Zope. The DigestAuthCrumbler is a bit less transparent. It *MUST* know the user's password in order to verify the validity of the presented auth information (more precisely, a special hash would be sufficient, but usual user folders do not support such hashes). Therefore, it can only be used together with UserFolders providing access to the clear text password. -- Dieter ___ 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] ac_acquire error happens after inheriting from Folder
Hi Dieter,
I figured it out after googling around for a few hours. In my
manage_addContact method, I'm now getting the object after it's instantiated
like so:
#instantiate a contact object
self._setObject(id, newContact)
#get the new instance
obj = self._getOb(id)
#change permissions based on value of private
if private==True:
obj.manage_permission('View',['Authenticated','Content
Manager','Manager'])
else:
obj.manage_permission('View',acquire=1)
It's still kinda weird though, because when Contact was just a SimpleItem
(ie. Not an ObjectManager) I did not need to do this. I was able to write
the above as newContact.manage_permission... and it worked. At least
that's how I remember it. Why is my Contact class considered an acquisition
wrapper after inheriting Folder, when prior to this, it was not?
Anyhow, for those of you who, like me, are somewhat new to writing Zope
products, I've found this site to be pretty useful (particularly chapter 4):
http://www.upfrontsystems.co.za/courses/zope/
One more question, when I get my object via self._getOb(id), is that any
different than doing dispatcher.getOb(id). If there is difference, what is
it and which way is better/worse?
Thanks,
Tom
-Original Message-
From: Dieter Maurer [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 28, 2006 1:54 PM
To: Palermo, Tom
Cc: 'zope@zope.org'
Subject: Re: [Zope] ac_acquire error happens after inheriting from Folder
Palermo, Tom wrote at 2006-2-28 11:25 -0500:
I have a class called Contact that is now inheriting from Folder. After
I did this, I get the following error when attempting to add a new Contact:
Exception Type AttributeError
Exception Value aq_acquire
Only acquisition wrappers have the aq_acquire method.
Looks at if your object were not an acquisition wrapper...
--
Dieter
___
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] product security changes from 2.8 to 2.8.5 - SOLVED
hey All It appears that I have solved it... My process in moving over the product from the old server was to blame. Here's what I did: export all of the zodb contents, and tarball the python product. Then I imported the zodb contents into the new server, and un-tarred the product. This resulted in the error of not finding the python methods, even though it appeard to be connected. So, I added the product form the add menu, and copy/pasted the zodb contents, and now it's all happy. For future refrence, is there a call to conenct this class back into the zodb filesystem after it has been moved to a new instance? Thanks for all the help! -e- ___ 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] Trapping exceptions
Sorry if this is a silly question but I've not found anything via Google or zope.org. I am using a MailHost in a Python script. I need to trap error conditions. When I run without trapping I can get exception SMTPSenderRefused. I inserted trapping - eg try: context.mailman.send(vmessage,mto=vto,mfrom=vfrom,subject='Message from web site') except SMTPSenderRefused: vsenderok=False else: vsenderok=True This gave error global name 'SMTPSenderRefused' is not defined I tried importing smtplib and adding it to the except line and then got a permissions problem. You are not allowed to access SMTPSenderRefused in this context I'd appreciate any help with this. Regards Tony ___ 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] Trapping exceptions
Tony Middleton wrote: This gave error global name 'SMTPSenderRefused' is not defined I tried importing smtplib and adding it to the except line and then got a permissions problem. You are not allowed to access SMTPSenderRefused in this context I'd appreciate any help with this. You may put this code into external method - then you'll have no problem with permissions or, if you really need this, you may declare necessary modules as permitted to Zope - this is described in Products/PythonScripts/module_access_examples.py. -- Maciej Wisniowski ___ 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] External Methods newbie question
Hello,I see I can only execute python functions in external methods. Is there any way to execute the whole file, not just a certain function? In linux I created a python script, and it doesn't have functions. I just want to execute the whole file. I tried using "self" or "init" for function names in Zope and it doesn't want to do it, telling me "The specified object, init, was not found in module, test."Is there a way to execute a file?(another question: is there a way to execute bash commands in linux? or is external methods only good for python?)Thanks in advance guys!! Yahoo! Mail Use Photomail to share photos without annoying attachments.___ 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] External Methods newbie question
--On 28. Februar 2006 17:14:50 -0800 Alric Aneron [EMAIL PROTECTED] wrote: Hello, I see I can only execute python functions in external methods. Is there any way to execute the whole file, not just a certain function? In linux I created a python script, and it doesn't have functions. I just want to execute the whole file. I tried using self or init for function names in Zope and it doesn't want to do it, telling me The specified object, init, was not found in module, test. Is there a way to execute a file? This is basically a Pyhthon question. Look at os.system(), the subprocess module, popenX callsthe Python Library Reference is your friend. -aj pgpIA6YvPZudO.pgp Description: PGP signature ___ 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] External Methods newbie question
I don't understand your question regarding 'execute the whole file'? Why can't you just put all of the python commands you want into an external method, then use a single 'main-line function' to call the 'sub-functions' as needed? python has a command called 'commands' which can be used for executing bash commands. hth Jonathan - Original Message - From: Alric Aneron To: zope@zope.org Sent: Tuesday, February 28, 2006 8:14 PM Subject: [Zope] External Methods newbie question Hello,I see I can only execute python functions in external methods. Is there any way to execute the whole file, not just a certain function? In linux I created a python script, and it doesn't have functions. I just want to execute the whole file. I tried using "self" or "init" for function names in Zope and it doesn't want to do it, telling me "The specified object, init, was not found in module, test."Is there a way to execute a file?(another question: is there a way to execute bash commands in linux? or is external methods only good for python?)Thanks in advance guys!! Yahoo! MailUse Photomail to share photos without annoying attachments. ___Zope maillist - Zope@zope.orghttp://mail.zope.org/mailman/listinfo/zope** No cross posts or HTML encoding! **(Related lists - http://mail.zope.org/mailman/listinfo/zope-announcehttp://mail.zope.org/mailman/listinfo/zope-dev ) ___ 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] External Methods newbie question
--On 28. Februar 2006 20:26:13 -0500 Jonathan [EMAIL PROTECTED] wrote: python has a command called 'commands' which can be used for executing bash commands. talk about modules, not commands. -aj pgpBHzYiv1PtN.pgp Description: PGP signature ___ 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] External Methods newbie question
thanks guys, I'll tryAndreas Jung [EMAIL PROTECTED] wrote: --On 28. Februar 2006 20:26:13 -0500 Jonathan <[EMAIL PROTECTED]> wrote: python has a command called 'commands' which can be used for executing bash commands.talk about modules, not commands.-aj Yahoo! Mail Bring photos to life! New PhotoMail makes sharing a breeze. ___ 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] External Methods newbie question
To executed a whole file you need to wrap it as a function -- def foo( self ): the script and call foo as an external method. The self argument gives the context. Python provides several modules which give access to execute bash commands, linux commands, etc. Look at the modules subprocess and commands. On Tue, 28 Feb 2006, Alric Aneron wrote: Hello, I see I can only execute python functions in external methods. Is there any way to execute the whole file, not just a certain function? In linux I created a python script, and it doesn't have functions. I just want to execute the whole file. I tried using self or init for function names in Zope and it doesn't want to do it, telling me The specified object, init, was not found in module, test. Is there a way to execute a file? (another question: is there a way to execute bash commands in linux? or is external methods only good for python?) ___ 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-DB] News Item properties
On 2006-02-27 at 17:31:09 [+0100], [EMAIL PROTECTED] wrote: Ciao, sto cercando di visualizzare su un page template zope (che tra l'altro e' l'home page index_html) l'ultima news inserita via plone. Ciao, scrive al'inglese per favore. Charlie Clark -- Charlie Clark eGenix.com Professional Python Services directly from the Source Python/Zope Consulting and Support ...http://www.egenix.com/ mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ mxODBC, mxDateTime, mxTextTools ...http://python.egenix.com/ 2005-10-17: Released mxODBC.Zope.DA 1.0.9http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! ___ Zope-DB mailing list Zope-DB@zope.org http://mail.zope.org/mailman/listinfo/zope-db
Re: [Zope-DB] News Item properties
On 2006-02-28 at 09:40:29 [+0100], [EMAIL PROTECTED] wrote: the fact is that I should have also the first 500 characters of the news (an abstract to put in the home page with a link of the entirely news) I tryed with: span tal:replace=python:test(obj.Dcoument, obj.Dcoument, obj.getId) Extended Calendar Product /span span tal:replace=python:test(obj.Text, obj.Text, obj.getId) Extended Calendar Product /span span tal:replace=python:test(obj.Content, obj.Content, obj.getId) Extended Calendar Product /span span tal:replace=python:test(obj.Body, obj.Body, obj.getId) Extended Calendar Product /span but I cannot show out the content... I have looked on references, on google and on zope 'doc' tab but nothing at all... Please redirect your question to the Plone list. This list is for questions about Zope and relational databases and the ZODB. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source Python/Zope Consulting and Support ...http://www.egenix.com/ mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ mxODBC, mxDateTime, mxTextTools ...http://python.egenix.com/ 2005-10-17: Released mxODBC.Zope.DA 1.0.9http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! ___ Zope-DB mailing list Zope-DB@zope.org http://mail.zope.org/mailman/listinfo/zope-db
Re: [Zope-DB] Partial Data Replication to postgreSQL.
Charlie Clark wrote: You can use APE to configure where data which is normally stored in the ZODB is stored. APE is dead, Shane said so himself... Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ Zope-DB mailing list Zope-DB@zope.org http://mail.zope.org/mailman/listinfo/zope-db
[Zope-DB] DCOracle2 installation problem
Title: DCOracle2 installation problem I downloaded DCOracle2-1.2.tgz and I am trying to install DCOracle on Fedora Core 3, I am using Oracle client libraries version 9.2, $ORACLE_HOME is correctly set, but when I try to build from the source files I get the following error message saying something about missing header files in my $ORACLE_HOME/rdbms/demo/ directory... Do you have anu clue? ---following is a complete build log from my machine-- [EMAIL PROTECTED] DCOracle2]# make (cd src; \ ./testora python) Checking ORACLE_HOME...passed. Checking for Oracle version...Oracle 9i found. (cd src; \ cp -p Setup.in Setup ) (cd src; \ make -f Makefile.pre.in boot PYTHON=python || ./setuperrors; \ make dummy || ./setuperrors) make[1]: Entering directory `/home/dcausevic/DCOracle2/src' rm -f *.o *~ rm -f *.a tags TAGS config.c Makefile.pre python sedscript rm -f *.so *.sl so_locations VERSION=`python -c import sys; print sys.version[:3]`; \ installdir=`python -c import sys; print sys.prefix`; \ exec_installdir=`python -c import sys; print sys.exec_prefix`; \ make -f ./Makefile.pre.in VPATH=. srcdir=. \ VERSION=$VERSION \ installdir=$installdir \ exec_installdir=$exec_installdir \ Makefile make[2]: Entering directory `/home/dcausevic/DCOracle2/src' sed -n \ -e '1s/.*/1i\\/p' \ -e '2s%.*%# Generated automatically from Makefile.pre.in by sedscript.%p' \ -e '/^VERSION=/s/^VERSION=[ ]*\(.*\)/[EMAIL PROTECTED]@]%\1%/p' \ -e '/^CC=/s/^CC=[ ]*\(.*\)/[EMAIL PROTECTED]@]%\1%/p' \ -e '/^CCC=/s/^CCC=[ ]*\(.*\)/[EMAIL PROTECTED]@]%CCC=\1%/p' \ -e '/^LINKCC=/s/^LINKCC=[ ]*\(.*\)/[EMAIL PROTECTED]@]%\1%/p' \ -e '/^OPT=/s/^OPT=[ ]*\(.*\)/[EMAIL PROTECTED]@]%\1%/p' \ -e '/^LDFLAGS=/s/^LDFLAGS=[ ]*\(.*\)/[EMAIL PROTECTED]@]%\1%/p' \ -e '/^DEFS=/s/^DEFS=[ ]*\(.*\)/[EMAIL PROTECTED]@]%\1%/p' \ -e '/^LIBS=/s/^LIBS=[ ]*\(.*\)/[EMAIL PROTECTED]@]%\1%/p' \ -e '/^LIBM=/s/^LIBM=[ ]*\(.*\)/[EMAIL PROTECTED]@]%\1%/p' \ -e '/^LIBC=/s/^LIBC=[ ]*\(.*\)/[EMAIL PROTECTED]@]%\1%/p' \ -e '/^RANLIB=/s/^RANLIB=[ ]*\(.*\)/[EMAIL PROTECTED]@]%\1%/p' \ -e '/^MACHDEP=/s/^MACHDEP=[ ]*\(.*\)/[EMAIL PROTECTED]@]%\1%/p' \ -e '/^SO=/s/^SO=[ ]*\(.*\)/[EMAIL PROTECTED]@]%\1%/p' \ -e '/^LDSHARED=/s/^LDSHARED=[ ]*\(.*\)/[EMAIL PROTECTED]@]%\1%/p' \ -e '/^CCSHARED=/s/^CCSHARED=[ ]*\(.*\)/[EMAIL PROTECTED]@]%\1%/p' \ -e '/^LINKFORSHARED=/s/^LINKFORSHARED=[ ]*\(.*\)/[EMAIL PROTECTED]@]%\1%/p' \ -e '/^prefix=/s/^prefix=\(.*\)/s%^prefix=.*%prefix=\1%/p' \ -e '/^exec_prefix=/s/^exec_prefix=\(.*\)/s%^exec_prefix=.*%exec_prefix=\1%/p' \ /usr/lib/python2.3/config/Makefile sedscript echo /[EMAIL PROTECTED]@/d sedscript echo /^installdir=/s%=.*%= /usr% sedscript echo /^exec_installdir=/s%=.*%=/usr% sedscript echo /^srcdir=/s%=.*%= .% sedscript echo /^VPATH=/s%=.*%= .% sedscript echo /^LINKPATH=/s%=.*%= % sedscript echo /^BASELIB=/s%=.*%= % sedscript echo /^BASESETUP=/s%=.*%= % sedscript sed -f sedscript ./Makefile.pre.in Makefile.pre /usr/lib/python2.3/config/makesetup \ -m Makefile.pre -c /usr/lib/python2.3/config/config.c.in Setup -n /usr/lib/python2.3/config/Setup make -f Makefile do-it-again make[3]: Entering directory `/home/dcausevic/DCOracle2/src' /usr/lib/python2.3/config/makesetup \ -m Makefile.pre -c /usr/lib/python2.3/config/config.c.in Setup -n /usr/lib/python2.3/config/Setup make[3]: Leaving directory `/home/dcausevic/DCOracle2/src' make[2]: Leaving directory `/home/dcausevic/DCOracle2/src' make[1]: Leaving directory `/home/dcausevic/DCOracle2/src' make[1]: Entering directory `/home/dcausevic/DCOracle2/src' make[1]: `dummy' is up to date. make[1]: Leaving directory `/home/dcausevic/DCOracle2/src' ( cd src; \ make || ./builderrors) make[1]: Entering directory `/home/dcausevic/DCOracle2/src' gcc -pthread -fPIC -DNDEBUG -O2 -g -pipe -m32 -march=i386 -mtune=pentium4 -D_GNU_SOURCE -fPIC -I/usr/include/python2.3 -I/usr/include/python2.3 @DEFS@ -I/u01/app/oracle/product/9.2/rdbms/demo -I/u01/app/oracle/product/9.2/network/public -I/u01/app/oracle/product/9.2/plsql/public -I/u01/app/oracle/product/9.2/rdbms/public -DORACLE9i -c ././dco2.c -o ./dco2.o gcc: @DEFS@: No such file or directory In file included from /usr/include/python2.3/Python.h:8, from ././dco2.c:125: /usr/include/python2.3/pyconfig.h:850:1: warning: _POSIX_C_SOURCE redefined In file included from /usr/include/stdio.h:28, from ././dco2.c:92: /usr/include/features.h:150:1: warning: this is the location of the previous definition make[1]: *** [dco2.o] Error 1 make[1]: Leaving directory `/home/dcausevic/DCOracle2/src' --- There were errors building the dco2 module. This could be because of a coding error in the dco2 module, or because your Oracle environment is not set up properly. Please double check that your Oracle environment is properly established, and that the proper header files exist (e.g. $ORACLE_HOME/rdbms/demo/*.h). If you still have problems, check for updates to DCOracle2 on http://www.zope.org or check out the mailing list
