Hey,
On 10/20/07, Tres Seaver [EMAIL PROTECTED] wrote:
Martijn Faassen wrote:
[snip]
Since this appears to be a rare case that is the exception, what about
using the new ZCML exclude framework for this case? You need to know
what you are doing, but this use case is for people who know
Hey,
On 10/20/07, Dieter Maurer [EMAIL PROTECTED] wrote:
[snip]
Zope 2 had (for products) all three things together.
It was felt that this was a too tight coupling. Therefore, for Zope 3
the paradigma explicit is better than implicit (a paradigma, that I
personally dislike and find wrong)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martijn Faassen wrote:
Hey,
On 10/20/07, Lennart Regebro [EMAIL PROTECTED] wrote:
On 10/20/07, Martijn Faassen [EMAIL PROTECTED] wrote:
I'd say it is a general concern of a framework to try to avoid how often
you need to repeat yourself. Right
Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martijn Faassen wrote:
Tres Seaver wrote:
Wichert Akkerman wrote:
[snip]
So I turned things around: if I state in my egg information that I
require another package that means I need to have that package
available and
Martijn Faassen wrote at 2007-10-20 03:15 +0200:
...
I'd say it is a general concern of a framework to try to avoid how often
you need to repeat yourself. Right now you to use a Zope 3 package you
need to do the following things:
* list the egg in your setup.py dependencies
* load the ZCML
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martijn Faassen wrote:
Tres Seaver wrote:
Wichert Akkerman wrote:
[snip]
So I turned things around: if I state in my egg information that I
require another package that means I need to have that package
available and functional. Which suggests
Fred Drake wrote:
On 10/17/07, Martin Aspeli [EMAIL PROTECTED] wrote:
Right - but you're building an application, and you're pretty
experienced with Zope. A lot of Plone users just want to install a
plug-in (a product), basically. Before, they just dropped it into a
It sounds like your
Tres Seaver wrote:
Wichert Akkerman wrote:
[snip]
So I turned things around: if I state in my egg information that I
require another package that means I need to have that package
available and functional. Which suggests that its zcml has to be loaded
before mine. And that is exactly what I am
Hey,
Martin Aspeli wrote:
Fred Drake wrote:
[snip]
For example, say you want to install oi.plum. You need to add the line
'oi.plum' twice - once under 'eggs' and once under 'zcml' in your
buildout.cfg. Forget the latter, and the package doesn't work properly
(or at all).
I actually really
On Friday 19 October 2007 21:17, Martijn Faassen wrote:
Tres Seaver wrote:
I may not *want* the other package's ZCML to be loaded: some of its
policies may not be appropriate for my application.
+1. Happens to me all the time.
Since this appears to be a rare case that is the exception,
Martin Aspeli wrote:
Fred Drake wrote:
On 10/17/07, Wichert Akkerman [EMAIL PROTECTED] wrote:
A common issue we are seeing is that we have eggs depending on each
other, but they still need to load the zcml from those dependencies
somehow. As a temporary solution to play with the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wichert Akkerman wrote:
Martin Aspeli wrote:
Fred Drake wrote:
On 10/17/07, Wichert Akkerman [EMAIL PROTECTED] wrote:
A common issue we are seeing is that we have eggs depending on each
other, but they still need to load the zcml from
On Oct 17, 2007, at 8:04 PM, Ross Patterson wrote:
...
I'm new to eggs, but maybe both sides could be satisfied with an
approach like extra_requires?
Extras are evil. See other posts of mine for explanations of why.
You could list oi.plum [zope.zcml] when
you require oi.plum *and* its ZCML
Tres Seaver wrote:
I may not *want* the other package's ZCML to be loaded: some of its
policies may not be appropriate for my application. I think that the
library vs. pluggable application distinction is valid here: maybe
you want to define an entry point in the egg which a given pluggable
On Oct 18, 2007, at 8:17 AM, Tres Seaver wrote:
I may not *want* the other package's ZCML to be loaded: some of its
policies may not be appropriate for my application. I think that the
library vs. pluggable application distinction is valid here:
maybe
you want to define an entry point in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Aspeli wrote:
Tres Seaver wrote:
I may not *want* the other package's ZCML to be loaded: some of its
policies may not be appropriate for my application. I think that the
library vs. pluggable application distinction is valid here:
Fred Drake wrote:
On 10/17/07, Wichert Akkerman [EMAIL PROTECTED] wrote:
A common issue we are seeing is that we have eggs depending on each
other, but they still need to load the zcml from those dependencies
somehow. As a temporary solution to play with the concept I added
something simple to
On 10/17/07, Martin Aspeli [EMAIL PROTECTED] wrote:
The main win, IMHO, is to avoid the requirement for people to install
slugs for third party products. Slugs suck - they are confusing to
explain and people forget them all the time. Buildout makes it a bit
easier, but it's still not a
Fred Drake wrote:
On 10/17/07, Martin Aspeli [EMAIL PROTECTED] wrote:
The main win, IMHO, is to avoid the requirement for people to install
slugs for third party products. Slugs suck - they are confusing to
explain and people forget them all the time. Buildout makes it a bit
easier, but it's
Martin Aspeli [EMAIL PROTECTED] writes:
Fred Drake wrote:
On 10/17/07, Martin Aspeli [EMAIL PROTECTED] wrote:
The main win, IMHO, is to avoid the requirement for people to install
slugs for third party products. Slugs suck - they are confusing to
explain and people forget them all the time.
On 10/17/07, Martin Aspeli [EMAIL PROTECTED] wrote:
Right - but you're building an application, and you're pretty
experienced with Zope. A lot of Plone users just want to install a
plug-in (a product), basically. Before, they just dropped it into a
It sounds like your concerns center around
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wichert Akkerman wrote:
A common issue we are seeing is that we have eggs depending on each
other, but they still need to load the zcml from those dependencies
somehow. As a temporary solution to play with the concept I added
something simple to
22 matches
Mail list logo
