I'd like to discuss possible improvements to have profile extensions
check some dependencies. This will require a way to express
dependencies, which in the general case can be extremely complex -- but
we probably don't need that.
Use cases
-
1. When installing CMFDefault:default, I'm of
On Wednesday 06 April 2005 08:14 am, Tres Seaver wrote:
> Florent Guillaume wrote:
> > Dieter Maurer <[EMAIL PROTECTED]> wrote:
> >>In our regular profiles, "listFilteredActionsFor" belongs to
> >>the top consumers of CPU time.
> >>
> >>Recently, I found the main culprit (in CMF 1.4):
> >>
> >>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Florent Guillaume wrote:
> Dieter Maurer <[EMAIL PROTECTED]> wrote:
>
>>In our regular profiles, "listFilteredActionsFor" belongs to
>>the top consumers of CPU time.
>>
>>Recently, I found the main culprit (in CMF 1.4):
>>
>> It is the completely u
Dieter Maurer <[EMAIL PROTECTED]> wrote:
> In our regular profiles, "listFilteredActionsFor" belongs to
> the top consumers of CPU time.
>
> Recently, I found the main culprit (in CMF 1.4):
>
>It is the completely unnecessary:
>
> if not action in catlist:
>
> In our case, "listFilte
The following supporters have open issues assigned to them in this collector
(http://www.zope.org/Collectors/CMF).
Assigned and Open
chrisw
- "Limit the roles that can create specified types of content.",
[Accepted] http://www.zope.org/Collectors/CMF/114
gregweb
- "CMFUid.U
Dieter Maurer wrote:
yuppie wrote at 2005-4-4 20:59 +0200:
...
2.) I prefer to see the correct import in each file and to use utils
just for the fallback.
But, then you get a nasty "try: ... except:" in hundred of
files rather than just a single one.
Eight files in CMF, not hundreds of files for
