[Zope-dev] zope-tests - FAILED: 2, OK: 36, UNKNOWN: 3
This is the summary for test reports received on the zope-tests list between 2011-08-12 00:00:00 UTC and 2011-08-13 00:00:00 UTC: See the footnotes for test reports of unsuccessful builds. An up-to date view of the builders is also available in our buildbot documentation: http://docs.zope.org/zopetoolkit/process/buildbots.html#the-nightly-builds Reports received Bluebream / Python2.4.6 64bit linux Bluebream / Python2.5.5 64bit linux Bluebream / Python2.6.5 64bit linux [1]FAILED (errors=1) : Zope-2.13-alltests Python-2.6.6 : Linux [2]FAILED (failures=1) : Zope-trunk-alltests Python-2.6.6 : Linux [3]UNKNOWN : winbot / ZODB_dev py_270_win32 ZTK 1.0 / Python2.4.6 Linux 64bit ZTK 1.0 / Python2.5.5 Linux 64bit [4]ZTK 1.0 / Python2.6.5 Linux 64bit [5]ZTK 1.0dev / Python2.4.6 Linux 64bit ZTK 1.0dev / Python2.5.5 Linux 64bit ZTK 1.0dev / Python2.6.5 Linux 64bit Zope 3.4 KGS / Python2.4.6 64bit linux Zope 3.4 KGS / Python2.5.5 64bit linux Zope 3.4 Known Good Set / py2.4-32bit-linux Zope 3.4 Known Good Set / py2.4-64bit-linux Zope 3.4 Known Good Set / py2.5-32bit-linux Zope 3.4 Known Good Set / py2.5-64bit-linux Zope-2.10 Python-2.4.6 : Linux Zope-2.11 Python-2.4.6 : Linux Zope-2.12 Python-2.6.6 : Linux Zope-2.12-alltests Python-2.6.6 : Linux Zope-2.13 Python-2.6.6 : Linux Zope-trunk Python-2.6.6 : Linux winbot / ZODB_dev py_254_win32 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win64 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 winbot / ztk_11 py_270_win64 winbot / ztk_dev py_254_win32 winbot / ztk_dev py_265_win32 winbot / ztk_dev py_265_win64 winbot / ztk_dev py_270_win32 winbot / ztk_dev py_270_win64 Non-OK results -- [1]UNKNOWN FAILED (errors=1) : Zope-2.13-alltests Python-2.6.6 : Linux https://mail.zope.org/pipermail/zope-tests/2011-August/048105.html [2]UNKNOWN FAILED (failures=1) : Zope-trunk-alltests Python-2.6.6 : Linux https://mail.zope.org/pipermail/zope-tests/2011-August/048107.html [3]UNKNOWN UNKNOWN : winbot / ZODB_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2011-August/048086.html [4]FAILED ZTK 1.0 / Python2.6.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-August/048124.html [5]FAILED ZTK 1.0dev / Python2.4.6 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-August/048094.html ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.interface versions, ZTK 1.0 and later
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/12/2011 02:46 PM, Tres Seaver wrote: > %< > Proposal > > - Revert ZTK 1.0 to use zope.interface 3.6.1. (We can skip this part > if the next step goes quickly). > > - Create a 3.6 branch in SVN, and revert all the post-3.6.1 changes > on it. Release a new 3.6.6 from this branch, possibly after applying > a new, more minimal fix for LP #570942. > > - Bump ZTK 1.0 to use the zope.interface 3.6.6. > > - Freeze development on the 3.6 branch. > > - Release a 3.7.0 version from the trunk, with all the porting > changes intact. Update ZTK 1.1 to use 3.7.0, > %< > Done. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software "Excellence by Design"http://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk5GvUoACgkQ+gerLs4ltQ4BDgCgtVyxaWLwfusKVZxoi2CrCayH zpAAn1ZeUD1vgb1lKq5F0smOovz1qbQz =aO2L -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [BlueBream] pagination in bluebream
Hello all,
Thanks for the replies.
On Fri, 2011-08-12 at 10:34 -0400, Tres Seaver wrote:
> That is the accepted mode. For many applications using pagination,
> the percentage of page views which ever use anything but the first
> batch is pretty tiny. Note as well that zope.catalog returns its
> result as sets of "document IDs", rather than the real objects, so you
> don't pay the cost of pulling the "early" items into the object cache:
> you only need to reify the objects for the "current" batch.
Then I will go with catalog approach. In this regard I need one more
clarification.
Say I have an object with following interface
class IMyObject(Interface):
id = TextLine(title=u'Object ID')
name = TextLine(title=u'Name')
...
and say I have registered the catalog like this
catalog['object_id'] = TextIndex('id', IMyObject)
The 'id' field is same as the key value under which the MyObject is
stored in its parent container. And say if the 'id' field value always
starts with a 'p' so its values are like 'p0001', 'p0002' etc.
So, while searching the catalog I query like this
catalog.apply({'object_id': 'p*'})
I get all the objects from the container as desired :) My problem is
solved, but out of curiosity I am asking this. If I query like this
catalog.apply({'object_id': '*'})
I get the following error
ParseError: Query contains only common words: '*'
So, How do I query a catalog to return all its objects?
I guess I can trust the order of objects returned while querying with
_limit option. Because I will be querying for the same keywords n number
of times with just the changing _limit values. Am I right?
Is there any detailed documentation explaining the query format to be
used while querying the catalog other than the documentation in pypi of
zope.catalog?
Thanks
Regards
--
Joshua Immanuel
HiPro IT Solutions Private Limited
http://hipro.co.in
signature.asc
Description: This is a digitally signed message part
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Pluggable template engine
On Sat, Aug 13, 2011 at 11:33 AM, Malthe Borch wrote: > I will merge this branch if there are no objections. No objections - only thanks and cheers :) Hanno ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Pluggable template engine
I will merge this branch if there are no objections. \malthe On 20 July 2011 17:24, Malthe Borch wrote: > I've refactored the ``pagetemplate`` module to realistically support > plugging in an alternative implementation of the parser and > interpreter. > > http://svn.zope.org/zope.pagetemplate/branches/engine-as-component/ > > Two new interfaces are added which serve as the plugging point see > ``IPageTemplateEngine`` and ``IPageTemplateProgram`` in this module: > > http://svn.zope.org/zope.pagetemplate/branches/engine-as-component/src/zope/pagetemplate/interfaces.py?rev=122300&view=markup > > I'd like to propose merging this into trunk. > > \malthe > ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
