The following supporters have open issues assigned to them in this collector
(http://www.zope.org/Collectors/CMF).
Assigned and Open
tseaver
- "CMF needs View-based TypeInformation",
[Accepted] http://www.zope.org/Collectors/CMF/437
yuppie
- "purge_old in runAllImportSteps
Previously yuppie wrote:
> Wichert Akkerman wrote:
> >Previously yuppie wrote:
> >>- The exports created by the new components handler are still flawed,
> >>ISiteRoot and placeless components are not exported correctly.
> >
> >I'm quite sure I fixed that: I was able to export the components and
>
Previously yuppie wrote:
> Wichert Akkerman wrote:
> >Previously yuppie wrote:
> >>- The exports created by the new components handler are still flawed,
> >>ISiteRoot and placeless components are not exported correctly.
> >
> >I'm quite sure I fixed that: I was able to export the components and
>
Previously yuppie wrote:
> - It might be useful to review the docstrings in CMFCore.utils and
> interfaces._tools. There are misleading comments like "BBB: for use in
> 'getToolByName'; in the future, prefer
> 'zapi.getUtility(IActionsTool)'." Seems not all docs reflect the latest
> tools-as-
Previously Jens Vagelpohl wrote:
> I'm supposed to do a CMF 2.1.0 release today, but the state of these
> issues is unclear. Wichert, did you look at it? There are no checkins
> into either CMF or GS as far as I can see. Export now yields this:
I took care of the GenericSetup changes as far as
Hi!
Wichert Akkerman wrote:
Previously yuppie wrote:
Wichert Akkerman wrote:
Previously yuppie wrote:
- The exports created by the new components handler are still flawed,
ISiteRoot and placeless components are not exported correctly.
I'm quite sure I fixed that: I was able to export the co
Previously yuppie wrote:
> Hi!
>
>
> Wichert Akkerman wrote:
> >Previously yuppie wrote:
> >>Wichert Akkerman wrote:
> >>>Previously yuppie wrote:
> - The exports created by the new components handler are still flawed,
> ISiteRoot and placeless components are not exported correctly.
> >>
Wichert Akkerman wrote:
Previously yuppie wrote:
Wichert Akkerman wrote:
I get something else: if I import this:
the export looks like this:
That seems to be a similar but different bug.
this is caused by the zope.component.registerUtility not storing the
factory method but the return
Previously yuppie wrote:
> The check for aq_base should be fine, but your example shows a second
> issue: type() is used to get the factory. That only works if the class
> is the factory.
>
> So there seems to be indeed a need to store somewhere the factory name :(
I think we need that to get t
Wichert Akkerman wrote:
Previously yuppie wrote:
The check for aq_base should be fine, but your example shows a second
issue: type() is used to get the factory. That only works if the class
is the factory.
So there seems to be indeed a need to store somewhere the factory name :(
I think we
Summary of messages to the cmf-tests list.
Period Mon Aug 6 12:00:00 2007 UTC to Tue Aug 7 12:00:00 2007 UTC.
There were 11 messages: 11 from CMF Unit Tests.
Tests passed OK
---
Subject: OK : CMF-1.5 Zope-2.7 Python-2.3.6 : Linux
From: CMF Unit Tests
Date: Mon Aug 6 21:33:32 EDT 2
Previously yuppie wrote:
> Wichert Akkerman wrote:
> >Previously yuppie wrote:
> >>The check for aq_base should be fine, but your example shows a second
> >>issue: type() is used to get the factory. That only works if the class
> >>is the factory.
> >>
> >>So there seems to be indeed a need to st
Hi!
Wichert Akkerman wrote:
Previously yuppie wrote:
Wichert Akkerman wrote:
Previously yuppie wrote:
The check for aq_base should be fine, but your example shows a second
issue: type() is used to get the factory. That only works if the class
is the factory.
So there seems to be indeed a
Hi!
Previously yuppie wrote:
> Wichert Akkerman wrote:
> >But we can't know if component or factory is used. What if someone uses
> >a factory which returns a component with a __module__ set?
>
> Don't know what __module__ usually looks like if the component is
> created at registration time. I
I want to look at http://dev.plone.org/plone/ticket/6855 before we tag
GS 1.3.1; it might be a GenericSetup bug.
Wichert.
--
Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
Previously Wichert Akkerman wrote:
> I want to look at http://dev.plone.org/plone/ticket/6855 before we tag
> GS 1.3.1; it might be a GenericSetup bug.
This turned out to be a bug in plone.app.form.
Wichert.
--
Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things.
http://www.wigg
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sorry for my silence yesterday - there was apparently a cable cut
where I live so I've been without phone and internet all day and all
night yesterday.
Looks like everything is in place now, thanks to Wichert and Yvo. If
there are no other urg
17 matches
Mail list logo
