[Zope-Annce] Technical Preview of Blob support in ZODB
Hi everybody, the ZODB team is proud to announce a technical preview of a Blob implementation for ZODB. Blobs are used to efficiently storage large amounts of binary data within a database. This implementation uses real files on the file system in combination with any ZODB storage (FileStorage, ...) and native support for ZEO clusters. It is efficient in terms of memory and CPU usage. As this is a technical preview announcement, please notice that this code might crash your computer, delete your data, and destroy your homework. Now, have a look at http://www.zope.org/Members/ctheune/ZODB-blobs.tar.gz This is a more or less recent ZODB 3.6 based branch with the additional Blob support. Check out the documentation in http://svn.zope.org/ZODB/branches/blob-merge-branch/src/ZODB/Blobs/ to see how to use the blobs. Feedback is welcome on [EMAIL PROTECTED] You should be able to use this ZODB with any recent Zope version (2.9 and 3 trunk). Cheers, Christian -- gocept gmbh co. kg - forsterstraße 29 - 06112 halle/saale - germany www.gocept.com - [EMAIL PROTECTED] - phone +49 345 122 9889 7 - fax +49 345 122 9889 1 - zope and plone consulting and development signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Zope-Announce maillist - Zope-Announce@zope.org http://mail.zope.org/mailman/listinfo/zope-announce Zope-Announce for Announcements only - no discussions (Related lists - Users: http://mail.zope.org/mailman/listinfo/zope Developers: http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope-dev] Branches finished for merging.
Do we want to include optional twisted in 2.10 too? It works now, for http. :-) Haven't tried the ftp yet, but if I finish it until tomorrow? ___ 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: request.debug needed for Zope 3 ZPT engine
Philipp von Weitershausen wrote: Several components that we'd like to use in Zope2, such as the SequenceEngine from Zope3, use the Zope 3 ZPT engine to render some things. (This has nothing to do with Zope 2 using or not using the Zope 3 ZPT engine.) The Zope 3 ZPT engine, in particular zope.app.pagetemplate.ViewPageTemplateFile, makes the assumption that 'request' properly implements IBrowserRequest. The Zope 2 request doesn't implement all of it, but it's close enough to make most of the Zope 3 stuff work. ViewPageTemplateFile, however, uses the 'debug' property of the request (it's specified in the request interface). This 'debug' property is an instance of DebugFlags and basically is a debugging switch for ZPT and other things. The Zope 2 request obviously doesn't have this 'debug' property. In the past we've usually added the necessary properties to the Zope 2 request in such cases. We could do this again, however: The Zope 2 request allows form data access through the __getattr__ protocol (the Zope 3 request does this through __getitem__). request.debug would shadow a potential 'debug' form variable and might break applications that make use of this form variable (I would expect there are at least a couple). Note that the obvious workaround is to use request.form['debug'] or request.cookies['debug'], depending on where you get the variable from. I would even say that this should be the preferred way of getting to form variables or cookies. But given the antiqueness of the Zope 2 API and no truly encouraged way of accessing things, there is to be expected code that relies on request.debug being the form variable. I would still vote for introducing the change. At some point (perhaps even in Zope 2.10), we'll want to use more and more of the Zope 3 ZPT engine. This problem would reoccur then. I'm therefore going to introduce the change on the zope33-port branch, as it is necessary for getting Five 1.5 (see Five's zope33-port branch) and Zope 2 to work with Zope 3.3. We can't potentially break currently perfectly working applications. I'd propose either: - introduce a config flag somewhere (zope.conf), off by default, switching the zope 2 REQUEST.debug to not using form/cookies/others but the proper attribute that zope 3 expects, - or make a deep hack in zope 2 request's __getattr__ for the 'debug' case to check the caller stack for the few cases we know are needed from zope 3 code (zpt engine for instance), and at the same time emit a warning that direct access to REQUEST.debug is deprecated and that people should use __getitem__ access. Do we also want to think about deprecating __getattr__ access to REQUEST in general? Given that the zope 2 core is not cleaned of it (I'm sure -- though I haven't looked), it would mean total deprecation wouldn't be done before 1.5 years anyway... Florent -- 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: Branches finished for merging.
On Sat, 2006-29-04 at 13:21 +0200, Laurence Rowe wrote: Lennart Regebro wrote: Do we want to include optional twisted in 2.10 too? It works now, for http. :-) Haven't tried the ftp yet, but if I finish it until tomorrow? If it is optional (and not default) I don't see why not, it'll make it easier to test with real sites to give it some battle hardening. +1 from me (being optional and not default of course) - Rocky -- Rocky Burt ServerZen Software -- http://www.serverzen.com News About The Server -- http://www.serverzen.net ___ 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/branches/easter-sprint_traversal-refactor/lib/python/ZPublisher/BaseRequest.py Now using an adapter. Two tests fail in Five, and I don't know why.
I know this code was just refactored and exists in stock Zope 2, but it made me see this: Lennart Regebro wrote: +class DefaultPublishTraverse(object): [...] +# Ensure that the object has a docstring, or that the parent +# object has a pseudo-docstring for the object. Objects that +# have an empty or missing docstring are not published. +doc = getattr(subobject, '__doc__', None) +if doc is None: +doc = getattr(object, '%s__doc__' % name, None) This should avoid acquisition and be performed on aq_base(object) I believe. Florent -- 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 2.10: Remaining tasks
Philipp von Weitershausen wrote: The feature freeze date for the June release is only days away. It was planned to be May 1st, but due to lots of pending branches, we might let it slip for a *couple* of days (not more!). I've compiled a rough list of outstanding tasks for Zope 2.10: http://www.zope.org/Wikis/DevSite/Projects/Zope2.10/Tasks Please complete and/or correct this list. It is up to the release managers (Stephan, Andreas) and the Pope to decide the exact feature freeze date, but I would suggest that we start merging those branches real soon. Another small task I know Julien Anguenot would like to do is fix the zpt engine (in Zope 3 I guess now) to work properly with mixed html/xhtml inclusion of macros. He's done most of the work with Fred Drake at the end of last year, but never got around to intergrate it. He's on a project deadline for now, but I believe will be available in the next few day (around wednesday?) to check that in. It could even be seen as a bugfix, really. Florent -- 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] [ANN] TextIndexNG 3.1.9 released
I am pleased to announce the release of TextIndexNG V 3.1.9. TextIndexNG V 3 is a complete new implementation based on Zope 3 technologies and can be used both in Zope 2.8 or in Zope 3. What's new? - multi-field indexing and query support - multi-lingual support - configurable converters (through ZCML) - new indexing API (allowing you to hook your custom content types with TextIndexNG through Zope 3 adapters). Changes in V 3.1.9: - added explicit check for the existence of the extension module so TextIndexNG3 will now fail at startup time with an exception instead of failing when creating new index instances - added UI support for valid word separators - added IObjectWrapper interface to core indexer engine to provide generic support for objects wrapped into some kind of wrapper. The purpose of the interface is to attach IObjectWrapper to wrapper classes using five:implements without having the need to modify exisiting code. - added support to deal better with indexing CMF content where the content object is wrapped inside a CMFCore.CatalogTool.IndexableObjectWrapper instance. TextIndexNG3/adapters/configure.zcml contains some commented configurations to attach a marker interface to IndexableObjectWrapper and in an addition an adapter to extract the wrapped object without having the need to add some CMF knowledge to the core indexing engine - added IExtensibleIndexableObjectWrapper for better integration with Plone (whose CatalogTool wraps Plone objects as ExtensibleIndexableObjectWrapper instances) - optimized internal datastructures (existing indexes should be cleared and reindexed) Requirements: - Zope 2.8+, Zope 3.2+ Download: http://sf.net/projects/textindexng Project page: http://opensource.zopyx.biz/OpenSource/TextIndexNG3 For installation and documentation issues refer to doc/README.txt from the archive. It's basically the same procedure as with former versions except you *need* to recompile the extension modules. Windows binaries of the required extension modules are currently not available (any volunteers?). TextIndexNG V 3 is published under the ZPL. Andreas Jung --- - Andreas JungZOPYX Ltd. Co KG- - E-mail: [EMAIL PROTECTED] Web: www.zopyx.com, www.zopyx.de - --- pgp5GQMvBILEP.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 )
[Zope] ImportError: No module named CMFActionIcons:1.5
Hi all, I've just apt-installed zope2.8.6 and CMF1.5 on Debian Sarge courtesy of backports.org: zope-cmf1.5 zope-cmfactionicons1.5 zope-cmfcalendar1.5 zope-cmfcore1.5 zope-cmfdefault1.5 zope-cmfsetup1.5 zope-cmftopic1.5 zope-cmfuid1.5 zope-dcworkflow1.5 I believe Debian does things slightly different so here's where everything lives: Zope home:/usr/lib/zope2.8 Zope software home: /usr/lib/zope2.8/lib/python/ Instance directory: /var/lib/zope2.8/instance CMF packages: /usr/share/zope/Products I've created an instance and added a 'products /usr/share/zope/Products' directive in that instance's zope.conf but CMF is not being imported on start up, and I'm getting the following event log message for each of the CMF packages mentioned above: 2006-04-29T12:36:05 ERROR Zope Could not import Products.CMFActionIcons:1.5 Traceback (most recent call last): File /usr/lib/zope2.8/lib/python/OFS/Application.py, line 698, in import_product product=__import__(pname, global_dict, global_dict, silly) ImportError: No module named CMFActionIcons:1.5 Any help much appreciated. sdt ___ 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] InterfaceError: already closed
Jeff Gentry wrote at 2006-4-28 15:52 -0400: I have a Product which uses ZPsycoPG (and thus psycopg), currently running on 3 systems. On two of them I never see this, but on the third I get intermittent errors of the nature: Interface Error: already closed. When you report errors, you must include full information, including at least error type, error value and traceback. You find all this information in your error_log object (in Zope's Root Folder). -- 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 )
[Zope] Re: ImportError: No module named CMFActionIcons:1.5
Quoth Igor Stroh [EMAIL PROTECTED]: Any help much appreciated. Debian has a tool called `dzhandle` (zope-common package), it allows you to create instances for different zope versions and add products to those instances. So in order to use zope products installed from debian packages, you basically need to do the following: 1) run `dzhandle -z2.8 make-instance $name-of-your-instance -m manual` (see `man dzhandle` for further details) 2) run `dzhandle -z2.8 add-product $name-of-your-instance \ CMFCore CMFDefault DCWorkflow CMFSetup CMFTopic CMFUid CMFCalendar CMFActionIcons` Ah... something of a documentation black hole, or I'm just looking but not finding. Many thanks Igor. sdt P.S. Apologies to anyone who is subscribed to the General list and the CMF list. I decided on second thoughts that my query was more suited to the General list and should have included a word or two of explanation before posting for the second time. ___ 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 2.8.5 becomes unresponsive.
I have had zopes like that on different linux versions. Following identified reasons on the different installations: 1. LDUF timeout(s) where -1 After upgrading LDUF where you could set timeouts and linux/zope version the operation -1 timeout caused deadlock and no response from zope for 5-15 minutes, depending on the timeout in the system call. Setting the timeout 0 solved it on this instance. 2. LinguaPlone had a bug or something, Jodok found this and it's fixed on the trunk. 3. Suspect: CacheFu - Memcache broken On Fedora 3 zope 2.8.x, I hade CacheFu and no debug on so I didn't see that the Memcache product in CacheFu was broken due missing memcache module. After turning the zope into debug and removing the Memcache product it has worked perfect. Hope this helps. /Sasha ___ 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 2.8.5 becomes unresponsive.
Am 29.04.2006, 21:36 Uhr tat Sasha Vincic [EMAIL PROTECTED] schraben: I have had zopes like that on different linux versions. Following identified reasons on the different installations: 1. LDUF timeout(s) where -1 [...] 2. LinguaPlone had a bug or something, Jodok found this and it's fixed on the trunk. [...] 3. Suspect: CacheFu - Memcache broken [...] Another thing I came across some times: 4. some method called while working on a request executed a HTTP GET for something else inside the same Zope instance (e.g. via urllib). Have some of these requests running simultanously and chances are pretty big that they'll hang around endlessly waiting for each other to finish and free up a Zope thread to answer their own sub-request. This will typically result in very little to almost no CPU usage. Good luck! Jo. -- internetmanufaktur jo- Berlin, Germany |||meder--- fon: ++49-30-44 04 27 82 http://www.meder.de/ fax: ++49-30-44 04 30 95 Kollwitzstr. 75 mob: ++49-170- 2 98 89 97 10435 Berlin ---http://www.meder.de/keys/jo-pubkey.txt ___ 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 )
