Hi Jens!
Jens Vagelpohl wrote:
Using just the ActionsTool right now in order to get that all set up and
then move to the other tools, I've gotten almost always there, but there
is one set of tests that refuse to run right now, the ones in
CMFCore.exportimport.tests.test_actions which derive
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19 Nov 2006, at 16:47, yuppie wrote:
I did not want to step on your toes, so I planned to modernize the
exportimport tests *after* you are done with your local utilities
changes. But I can make this high priority if it should be done
On Sun, 2006-19-11 at 14:37 +0100, Jens Vagelpohl wrote:
Using just the ActionsTool right now in order to get that all set up
and then move to the other tools, I've gotten almost always there,
but there is one set of tests that refuse to run right now, the ones
in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rocky Burt wrote:
On Sun, 2006-19-11 at 14:37 +0100, Jens Vagelpohl wrote:
Using just the ActionsTool right now in order to get that all set up
and then move to the other tools, I've gotten almost always there,
but there is one set of tests
On Sun, 2006-19-11 at 12:59 -0500, Tres Seaver wrote:
Rocky Burt wrote:
But we shouldn't have to specify ``context=site`` should we?
getUtility should automatically figure out what the nearest chain of
sites should be and look for local utilities in each one of them
automatically no?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19 Nov 2006, at 18:59, Tres Seaver wrote:
Export actions tool.
site = context.getSite()
- -tool = getToolByName(site, 'portal_actions', None)
+tool = getUtility(IActionsTool, context=site)
This looks like it will be
