November 2008 - Zope-Dev

Zope Tests: 4 OK, 2 Failed
by Zope Tests Summarizer 19 Nov '08

19 Nov '08

Summary of messages to the zope-tests list. Period Tue Nov 18 12:00:00 2008 UTC to Wed Nov 19 12:00:00 2008 UTC. There were 6 messages: 6 from Zope Tests. Test failures ------------- Subject: FAILED (failures=3) : Zope-trunk Python-2.4.5 : Linux From: Zope Tests Date: Tue Nov 18 20:36:54 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010512.html Subject: FAILED (failures=3) : Zope-trunk Python-2.5.2 : Linux From: Zope Tests Date: Tue Nov 18 20:38:24 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010513.html Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.7 : Linux From: Zope Tests Date: Tue Nov 18 20:30:53 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010508.html Subject: OK : Zope-2.9 Python-2.4.5 : Linux From: Zope Tests Date: Tue Nov 18 20:32:23 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010509.html Subject: OK : Zope-2.10 Python-2.4.5 : Linux From: Zope Tests Date: Tue Nov 18 20:33:53 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010510.html Subject: OK : Zope-2.11 Python-2.4.5 : Linux From: Zope Tests Date: Tue Nov 18 20:35:23 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010511.html

1 0

Zope Tests: 4 OK, 2 Failed
by Zope Tests Summarizer 18 Nov '08

18 Nov '08

Summary of messages to the zope-tests list. Period Mon Nov 17 12:00:00 2008 UTC to Tue Nov 18 12:00:00 2008 UTC. There were 6 messages: 6 from Zope Tests. Test failures ------------- Subject: FAILED (failures=3) : Zope-trunk Python-2.4.5 : Linux From: Zope Tests Date: Mon Nov 17 20:38:19 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010506.html Subject: FAILED (failures=3) : Zope-trunk Python-2.5.2 : Linux From: Zope Tests Date: Mon Nov 17 20:39:49 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010507.html Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.7 : Linux From: Zope Tests Date: Mon Nov 17 20:32:19 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010502.html Subject: OK : Zope-2.9 Python-2.4.5 : Linux From: Zope Tests Date: Mon Nov 17 20:33:49 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010503.html Subject: OK : Zope-2.10 Python-2.4.5 : Linux From: Zope Tests Date: Mon Nov 17 20:35:19 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010504.html Subject: OK : Zope-2.11 Python-2.4.5 : Linux From: Zope Tests Date: Mon Nov 17 20:36:49 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010505.html

1 0

Zope Tests: 4 OK, 2 Failed
by Zope Tests Summarizer 17 Nov '08

17 Nov '08

Summary of messages to the zope-tests list. Period Sun Nov 16 12:00:00 2008 UTC to Mon Nov 17 12:00:00 2008 UTC. There were 6 messages: 6 from Zope Tests. Test failures ------------- Subject: FAILED (failures=3) : Zope-trunk Python-2.4.5 : Linux From: Zope Tests Date: Sun Nov 16 20:38:04 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010500.html Subject: FAILED (failures=3) : Zope-trunk Python-2.5.2 : Linux From: Zope Tests Date: Sun Nov 16 20:39:34 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010501.html Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.7 : Linux From: Zope Tests Date: Sun Nov 16 20:32:03 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010496.html Subject: OK : Zope-2.9 Python-2.4.5 : Linux From: Zope Tests Date: Sun Nov 16 20:33:33 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010497.html Subject: OK : Zope-2.10 Python-2.4.5 : Linux From: Zope Tests Date: Sun Nov 16 20:35:03 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010498.html Subject: OK : Zope-2.11 Python-2.4.5 : Linux From: Zope Tests Date: Sun Nov 16 20:36:34 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010499.html

1 0

Request for comments: Devilstick persistence/storage
by Jens W. Klein 17 Nov '08

17 Nov '08

I would like to request comments on our idea how to use different storages for our new model-driven approch with the name Devilstick. You dont need to know devilstick or its ideas in depth to give valuable input. More it would helps us to get input from people knowing zopes persistency layer in depth. Devilstick is model driven framework to describe and manage data inside and outside ZODB. some more information at http://devilstickproject.net At Blackforest sprint in august we researched how the goal to support different storages than ZODB can be achieved. After first thinking about an own layer we got there the idea of using the usal persistence and transaction API of zope. IIRC it was a result of a conversation between Florian Friesdorf and Roger Ineichen and probably others. Today is the last day of Bolzano sprint. We researched a lot how it currently works with ZODB and discussed about how to use all this framework for devilstick. Our outcome is a document describing what we found and how we want to use all this. It follows here. for the devilstick-team Jens Klein ========================================================================= ----------------------------------- Introduction to Devilstick Storages ----------------------------------- This document describes the future. One of Devilsticks power is to support different storages than ZODB easily. The storage layer uses 100% zopes persistency implementation. At some entry point we enter the model driven world of devilstick: We hit 'Cage'. The Cage itself is not a data-access-object (DAO). But its the bridge to the otherstorage layer. Inside Devilstick DAOs are still persistent objects. They may still live in ZODB. But they can live complete outside if it is needed. They may live in SQL-databases, in LDAP, filesystem or fetched over a webservice. For more about DAOs and its API please read API.txt. Excursus: Zopes Persistence Framework ------------------------------------- Classic zope objects are derived from 'persistence.Persistent'. Those objects are tracking themselfes for modifications. Once a modification is detected it joins it's data-manager to the current transaction-manager. All this happens in zope fully transparent. The data-manager is the key to the storage layer. Zope is designed to use different data-managers. Datamanagers are described well in 'transaction.interfaces.IDataManager'. They care about storing all data in a 2-phase commit. There is usally one data-manager for all modified object of one database. Transaction-manager collects all datamanagers (which are called resources inside the transaction-manager) with modifications. Once the transaction is committed the 2-phase commit is started: 1st 'tpc_begin' is called on each data-manager, 2nd the 'commit' is called for each, then 'tpc_vote' and finally 'tpc_finish'. After creation of a persistent object it has an attribute called '_p_jar' set to 'None'. _p_jar gets a datamanager set - almost magically - after it was added to a container. The datamanager taken there is copied over from the containers _p_jar attribute. Container and new object are marked as modifed and the datamanager joins the transaction. On commit both are written to the database. Devilstick persistency ---------------------- To provide other storages we alreay have a powerful framework: the persistent api and transaction api. Devilstick uses both. To use a different storage simply a new data-manager is needed. Anyway, for several uses-cases its fine to stay in the ZODB. Such a alternative datamanager might work different inside than the current ZODB one. Since we deal with SQL or LDAP we want to update a database with one query for several objects involved. So on commit we may need to look at the modified objects and build one sql-query from a bunch of modifications. Frameworks like SQLAlchemy may help us here for SQL and others are probably available for different use-cases. Entry-Points: Cages ------------------- We need one point where the datamanager is switched to a different storage.A model is assigned and there the world of generic DAOs is entered. This entry point is called 'Cage'. A cage is still persistent in the ZODB and uses the zopes default data-manager. A cage has the root container DAO (which is a generic molecule DAO) set as an attribute. Here some example code how it looks like: >>> cage = Cage() >>> cage._p_jar None >>> somezodbcontainer._p_jar <Connection at ... > >>> somezodbcontainer['data'] = cage >>> cage._p_jar <Connection at ... > >>> cage._root None >>> cage.model = 'examplemodel' >>> cage._root <Molecule at ...> >>> cage._root._p_jar <MyStoragesDataManager at ...> The cage also bridges the container API of the root molecule. It simplifies the usage of the API and avoids to introduce a extra access step on the cage. This way its more intuitive. >>> cage._root.keys() ['m1', 'm2', 'm3'] >>> cage.keys() ['m1', 'm2', 'm3'] >>> cage['m1] is cage._root['m1'] True

2 1

Zope Tests: 4 OK, 2 Failed
by Zope Tests Summarizer 16 Nov '08

16 Nov '08

Summary of messages to the zope-tests list. Period Sat Nov 15 12:00:00 2008 UTC to Sun Nov 16 12:00:00 2008 UTC. There were 6 messages: 6 from Zope Tests. Test failures ------------- Subject: FAILED (failures=3) : Zope-trunk Python-2.4.5 : Linux From: Zope Tests Date: Sat Nov 15 20:36:57 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010494.html Subject: FAILED (failures=3) : Zope-trunk Python-2.5.2 : Linux From: Zope Tests Date: Sat Nov 15 20:38:27 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010495.html Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.7 : Linux From: Zope Tests Date: Sat Nov 15 20:30:56 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010490.html Subject: OK : Zope-2.9 Python-2.4.5 : Linux From: Zope Tests Date: Sat Nov 15 20:32:26 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010491.html Subject: OK : Zope-2.10 Python-2.4.5 : Linux From: Zope Tests Date: Sat Nov 15 20:33:56 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010492.html Subject: OK : Zope-2.11 Python-2.4.5 : Linux From: Zope Tests Date: Sat Nov 15 20:35:27 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010493.html

1 0

Re: [Zope-dev] SVN: ZODB/trunk/src/ZODB/tests/testConfig.py Import ClientStorage earlier to avoid a spurious test warning about
by Tres Seaver 15 Nov '08

15 Nov '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jim Fulton wrote: > Log message for revision 92950: > Import ClientStorage earlier to avoid a spurious test warning about > leaving a thread behind. > > > Changed: > U ZODB/trunk/src/ZODB/tests/testConfig.py > > -=- > Modified: ZODB/trunk/src/ZODB/tests/testConfig.py > =================================================================== > --- ZODB/trunk/src/ZODB/tests/testConfig.py 2008-11-14 23:08:38 UTC (rev 92949) > +++ ZODB/trunk/src/ZODB/tests/testConfig.py 2008-11-14 23:08:40 UTC (rev 92950) > @@ -14,11 +14,11 @@ > > import transaction > import unittest > +import ZEO.ClientStorage > import ZODB.config > import ZODB.POSException > import ZODB.tests.util > > - > class ConfigTestBase(ZODB.tests.util.TestCase): > > def _opendb(self, s): Would that be worth a backport (would it work, I guess I mean, on older versions of ZODB)? Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver(a)palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJHyol+gerLs4ltQ4RAqz9AJwJmenOmLF1CHHOIsHGsBCia2S++QCeL+oz Yyh67sN+G3f17hEUUMBK2BE= =Quh4 -----END PGP SIGNATURE-----

1 0

Re: [Zope-dev] [Checkins] SVN: zope.sendmail/trunk/ Copied over the UtilityTerm and UtilityVocabulary implementation from zope.app.component to avoid a dependency.
by Benji York 15 Nov '08

15 Nov '08

On Fri, Nov 14, 2008 at 7:23 PM, Hanno Schlichting <plone(a)hannosch.info> wrote: > Log message for revision 92953: > Copied over the UtilityTerm and UtilityVocabulary implementation from zope.app.component to avoid a dependency. Instead of duplicating the code there should be a zope.utilityvocabulary package that both zope.sendmail and zope.app.component can use. > Changed: > U zope.sendmail/trunk/CHANGES.txt > U zope.sendmail/trunk/buildout.cfg > U zope.sendmail/trunk/setup.py > D zope.sendmail/trunk/src/zope/sendmail/DEPENDENCIES.cfg > U zope.sendmail/trunk/src/zope/sendmail/vocabulary.py > > -=- > Modified: zope.sendmail/trunk/CHANGES.txt > =================================================================== > --- zope.sendmail/trunk/CHANGES.txt 2008-11-14 23:08:44 UTC (rev 92952) > +++ zope.sendmail/trunk/CHANGES.txt 2008-11-15 00:23:04 UTC (rev 92953) > @@ -4,6 +4,9 @@ > 3.5.1 (unreleased) > ------------------ > > +- Copied over the UtilityTerm and UtilityVocabulary implementation from > + zope.app.component to avoid a dependency. > + > - work around a problem when smtp quit fails, the mail was considered not > delivered where just the quit failed > > > Modified: zope.sendmail/trunk/buildout.cfg > =================================================================== > --- zope.sendmail/trunk/buildout.cfg 2008-11-14 23:08:44 UTC (rev 92952) > +++ zope.sendmail/trunk/buildout.cfg 2008-11-15 00:23:04 UTC (rev 92953) > @@ -2,8 +2,6 @@ > develop = . > parts = test coverage-test coverage-report > > -find-links = http://download.zope.org/distribution/ > - > [test] > recipe = zc.recipe.testrunner > eggs = zope.sendmail > > Modified: zope.sendmail/trunk/setup.py > =================================================================== > --- zope.sendmail/trunk/setup.py 2008-11-14 23:08:44 UTC (rev 92952) > +++ zope.sendmail/trunk/setup.py 2008-11-15 00:23:04 UTC (rev 92953) > @@ -43,7 +43,6 @@ > 'zope.interface', > 'zope.schema', > 'zope.security', > - 'zope.app.component', > ], > include_package_data = True, > zip_safe = False, > > Deleted: zope.sendmail/trunk/src/zope/sendmail/DEPENDENCIES.cfg > =================================================================== > --- zope.sendmail/trunk/src/zope/sendmail/DEPENDENCIES.cfg 2008-11-14 23:08:44 UTC (rev 92952) > +++ zope.sendmail/trunk/src/zope/sendmail/DEPENDENCIES.cfg 2008-11-15 00:23:04 UTC (rev 92953) > @@ -1,9 +0,0 @@ > -transaction > -# zope.app for UtilityVocabulary > -zope.app > -zope.component > -zope.configuration > -zope.i18nmessageid > -zope.interface > -zope.schema > -zope.security > > Modified: zope.sendmail/trunk/src/zope/sendmail/vocabulary.py > =================================================================== > --- zope.sendmail/trunk/src/zope/sendmail/vocabulary.py 2008-11-14 23:08:44 UTC (rev 92952) > +++ zope.sendmail/trunk/src/zope/sendmail/vocabulary.py 2008-11-15 00:23:04 UTC (rev 92953) > @@ -17,11 +17,155 @@ > """ > __docformat__ = 'restructuredtext' > > +import zope.component > from zope.interface import classProvides > +from zope.interface import implements > +from zope.interface import Interface > +from zope.schema.interfaces import ITokenizedTerm > from zope.schema.interfaces import IVocabularyFactory > +from zope.schema.interfaces import IVocabularyTokenized > from zope.sendmail.interfaces import IMailDelivery > -from zope.app.component.vocabulary import UtilityVocabulary > > + > +class UtilityTerm(object): > + """A term representing a utility. > + > + The token of the term is the name of the utility. Here is a brief example > + on how the IVocabulary interface is handled in this term as a > + utility: > + > + >>> from zope.interface.verify import verifyObject > + >>> from zope.schema.interfaces import IVocabulary > + >>> term = UtilityTerm(IVocabulary, 'zope.schema.interfaces.IVocabulary') > + >>> verifyObject(ITokenizedTerm, term) > + True > + > + >>> term.value > + <InterfaceClass zope.schema.interfaces.IVocabulary> > + >>> term.token > + 'zope.schema.interfaces.IVocabulary' > + > + >>> term > + <UtilityTerm zope.schema.interfaces.IVocabulary, instance of InterfaceClass> > + """ > + implements(ITokenizedTerm) > + > + def __init__(self, value, token): > + """Create a term for value and token.""" > + self.value = value > + self.token = token > + > + def __repr__(self): > + return '<UtilityTerm %s, instance of %s>' %( > + self.token, self.value.__class__.__name__) > + > + > +class UtilityVocabulary(object): > + """Vocabulary that provides utilities of a specified interface. > + > + Here is a short example of how the vocabulary should work. > + > + First we need to create a utility interface and some utilities: > + > + >>> class IObject(Interface): > + ... 'Simple interface to mark object utilities.' > + > + >>> class Object(object): > + ... implements(IObject) > + ... def __init__(self, name): > + ... self.name = name > + ... def __repr__(self): > + ... return '<Object %s>' %self.name > + > + Now we register some utilities for IObject > + > + >>> from zope.component import provideUtility > + >>> object1 = Object('object1') > + >>> provideUtility(object1, name='object1') > + >>> object2 = Object('object2') > + >>> provideUtility(object2, name='object2') > + >>> object3 = Object('object3') > + >>> provideUtility(object3, name='object3') > + >>> object4 = Object('object4') > + > + We are now ready to create a vocabulary that we can use; in our case > + everything is global, so the context is None. > + > + >>> vocab = UtilityVocabulary(None, interface=IObject) > + >>> import pprint > + >>> pprint.pprint(vocab._terms.items()) > + [(u'object1', <UtilityTerm object1, instance of Object>), > + (u'object2', <UtilityTerm object2, instance of Object>), > + (u'object3', <UtilityTerm object3, instance of Object>)] > + > + Now let's see how the other methods behave in this context. First we can > + just use the 'in' opreator to test whether a value is available. > + > + >>> object1 in vocab > + True > + >>> object4 in vocab > + False > + > + We can also create a lazy iterator. Note that the utility terms might > + appear in a different order than the utilities were registered. > + > + >>> iterator = iter(vocab) > + >>> terms = list(iterator) > + >>> names = [term.token for term in terms] > + >>> names.sort() > + >>> names > + [u'object1', u'object2', u'object3'] > + > + Determining the amount of utilities available via the vocabulary is also > + possible. > + > + >>> len(vocab) > + 3 > + """ > + implements(IVocabularyTokenized) > + classProvides(IVocabularyFactory) > + > + # override these in subclasses > + interface = Interface > + nameOnly = False > + > + def __init__(self, context, **kw): > + utils = zope.component.getUtilitiesFor(self.interface, context) > + self._terms = dict( > + (name, UtilityTerm(self.nameOnly and name or util, name)) > + for name, util in utils) > + > + def __contains__(self, value): > + """See zope.schema.interfaces.IBaseVocabulary""" > + return value in (term.value for term in self._terms.values()) > + > + def getTerm(self, value): > + """See zope.schema.interfaces.IBaseVocabulary""" > + try: > + return [term for name, term in self._terms.items() > + if term.value == value][0] > + except IndexError: > + raise LookupError(value) > + > + def getTermByToken(self, token): > + """See zope.schema.interfaces.IVocabularyTokenized""" > + try: > + return self._terms[token] > + except KeyError: > + raise LookupError(token) > + > + def __iter__(self): > + """See zope.schema.interfaces.IIterableVocabulary""" > + # Sort the terms by the token (utility name) > + values = self._terms.values() > + values.sort(lambda x, y: cmp(x.token, y.token)) > + return iter(values) > + > + def __len__(self): > + """See zope.schema.interfaces.IIterableVocabulary""" > + return len(self._terms) > + > + > class MailDeliveryNames(UtilityVocabulary): > """Vocabulary with names of mail delivery utilities > > > _______________________________________________ > Checkins mailing list > Checkins(a)zope.org > http://mail.zope.org/mailman/listinfo/checkins > -- Benji York Senior Software Engineer Zope Corporation

4 3

Zope Tests: 4 OK, 2 Failed
by Zope Tests Summarizer 15 Nov '08

15 Nov '08

Summary of messages to the zope-tests list. Period Fri Nov 14 12:00:00 2008 UTC to Sat Nov 15 12:00:00 2008 UTC. There were 6 messages: 6 from Zope Tests. Test failures ------------- Subject: FAILED (failures=3) : Zope-trunk Python-2.4.5 : Linux From: Zope Tests Date: Fri Nov 14 20:37:42 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010488.html Subject: FAILED (failures=3) : Zope-trunk Python-2.5.2 : Linux From: Zope Tests Date: Fri Nov 14 20:39:12 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010489.html Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.7 : Linux From: Zope Tests Date: Fri Nov 14 20:31:41 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010484.html Subject: OK : Zope-2.9 Python-2.4.5 : Linux From: Zope Tests Date: Fri Nov 14 20:33:12 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010485.html Subject: OK : Zope-2.10 Python-2.4.5 : Linux From: Zope Tests Date: Fri Nov 14 20:34:42 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010486.html Subject: OK : Zope-2.11 Python-2.4.5 : Linux From: Zope Tests Date: Fri Nov 14 20:36:12 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010487.html

1 0

Update on Zope2 egg and correct / minimal dependencies
by Hanno Schlichting 14 Nov '08

14 Nov '08

Hi. I had some time to work on the Zope2 egg and the correct / minimal dependency set. The current work is at: svn://svn.zope.org/repos/main/Zope2.buildout/trunk This gives you a Zope2 egg in a buildout environment with the latest releases of all dependencies included. The Zope2 egg itself installs fine into a virtualenv via 'python setup.py develop' as well. Running the tests via bin/test results in one broken test in Five's aq_legacy.txt right now. It is a test interdependency failure, as the Five tests pass on their own. In terms of dependencies, we have 38 direct dependencies on zope.* packages and 13 other dependencies (ZODB3, docutils, ...). Including the indirect dependencies we pull in 65 zope.* packages in total. A classic Zope2 tarball so far included 103 zope.* packages. Thanks to tl.eggdeps, Rok Garbas [1] and Marius Gedminas [2] I made updated dependency graphs for all direct zope.* dependencies of Zope2 [3]. I tried to trim these via 'tred' as Marius suggested, but all non-trivial graphs have circular dependencies, which made 'tred' produce useless output for me. If you want to continue to help on sanitizing the dependencies, sorting the graphs by size [4] is a good starting point. You can see that circular dependencies exist for all of: zope.location, zope.publisher, zope.security and zope.traversing. All the packages whose dependency graph is more than 1 megabyte clearly have a problem. The dot files are quite good to read for those. I'll continue to work on this, feel free to jump in :) Hanno [1] http://sharbas.blogspot.com/2008/09/repozeplone-dependecy-graph.html [2] http://mg.pov.lt/blog/simplifying-dependency-graphs.html [3] http://hannosch.eu/zope2-dependencies [4] http://hannosch.eu/zope2-dependencies/?S=D

1 0

Re: [Zope-dev] SVN: Zope2.buildout/trunk/setup.py First round of minimizing our dependency set to the correct one.
by Tres Seaver 14 Nov '08

14 Nov '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Wichert Akkerman wrote: > Previously Hanno Schlichting wrote: >> Log message for revision 92938: >> First round of minimizing our dependency set to the correct one. > > For future changes can you please not reindent the code at the same > time? It is impossible to see what changed now. > > Wichert. > This might help: $ svn diff -r 92937:92938 -x -uw \ svn+ssh://svn.zope.org/repos/main/Zope2.buildout/trunk Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver(a)palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJHfjs+gerLs4ltQ4RAjGaAKCovre6sMBkXYDeZd5FXC+K62UxdQCggc2n zO8oLiHwaiCPuM5VOTUSs9Y= =4Ro/ -----END PGP SIGNATURE-----

1 0