Hey,
Dan Korostelev wrote:
[snip]
>>
>> What about the other use case of , i.e. declaring implemented
>> interfaces, as in
>>
>>
>>
>>
>
> +1. That's kinda strange to have it in zope.security.
>
> I think, the better place to move zcml directives is zope.component,
> as it already depend
wiki.zope.org is down. The hosting centre operator just sent a mail
that they have power outages and the location at which wiki.zope.org
sits is affected.
Christian
--
Christian Theune · c...@gocept.com
gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany
http://gocept.com · t
On Thu, Jan 29, 2009 at 4:01 AM, Martijn Faassen wrote:
> I believe it'd be nicer to extract any ZCML related stuff from
> zope.component at some point and put it into zope.componentzcml or
> something like that. We could then decide to move the and
> directives in there as well.
+1
This makes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jan 29, 2009, at 14:42 , Christian Theune wrote:
> wiki.zope.org is down. The hosting centre operator just sent a mail
> that they have power outages and the location at which wiki.zope.org
> sits is affected.
All services should be restored. One
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martijn Faassen wrote:
> Log message for revision 95421:
> Remove zope.app.component dependency. Declare zope.app.dependable
> dependency which should've been declared already.
> Modified: zope.container/trunk/src/zope/container/testing.py
> ===
Tres Seaver wrote:
> W! zope.container is a new module, not in zope.app: why are we
> injecting a dependency on zope.app.folder here? Logically,
> zope.app.folder ought to depend on zope.container, and not vice versa.
> We should be mocking those objects, I think.
One step at the time. Tak
Hello,
Seems like lovely.recipe.importchecker fails on python 2.5 with:
File
"/home/adi/.buildout/eggs/lovely.recipe-1.0.0a1-py2.5.egg/lovely/recipe/importchecker/importchecker.py",
line 313, in main
db.findModules()
File
"/home/adi/.buildout/eggs/lovely.recipe-1.0.0a1-py2.5.egg/lovely
On Thursday 29 January 2009, Martijn Faassen wrote:
> > W! zope.container is a new module, not in zope.app: why are we
> > injecting a dependency on zope.app.folder here? Logically,
> > zope.app.folder ought to depend on zope.container, and not vice versa.
> > We should be mocking those obje
On Thursday 29 January 2009, Wolfgang Schnerring wrote:
> @@ -5,6 +5,8 @@
> 3.4.2 (unreleased)
> --
>
> +- Use zope.container instead of zope.app.container.
> +
I think that changing a dependency like this, should cause a new major
release, in this case 3.5.0. Changing the dep
Stephan Richter wrote:
> On Thursday 29 January 2009, Wolfgang Schnerring wrote:
>> @@ -5,6 +5,8 @@
>> 3.4.2 (unreleased)
>> --
>>
>> +- Use zope.container instead of zope.app.container.
>> +
>
> I think that changing a dependency like this, should cause a new major
> release,
Hi there,
We're currently updating references to zope.app.container to
zope.container where appropriate. We just ran into zope.app.locales,
which contains translations for various strings with the id
zope.app.container.
The tool to update the zope.pot file is installed in bin/i18nextract.
Unf
Hi there,
After a lot of work we have progress to report on the dependency
reduction front:
http://faassen.n--tree.net/blog/view/weblog/2009/01/29/0
It's been a lot of work to get this far and there's a huge amount of
work to be done still, but there is progress!
The second dependency graph i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martijn Faassen wrote:
> Hi there,
>
> After a lot of work we have progress to report on the dependency
> reduction front:
>
> http://faassen.n--tree.net/blog/view/weblog/2009/01/29/0
>
> It's been a lot of work to get this far and there's a huge a
Hello,
we are holding a mini sprint at Marijn Faassen's place this week with
the main goal of reducing dependencies between Zope packages.
One result of this effort is that now the non-ZMI parts of
zope.app.container have been factored out into zope.container, and
only the ZMI-related bits (zope.a
14 matches
Mail list logo
