-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
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
import them
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
import them
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 I
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
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.
I'm quite sure I fixed
Wichert Akkerman wrote:
Previously yuppie wrote:
Wichert Akkerman wrote:
I get something else: if I import this:
utility interface=foo.IBar factory=foo.bar/
the export looks like this:
utility interface=foo.IBar object=/
That seems to be a similar but different bug.
this is caused by
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 the
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
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 store somewhere the
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 did
Hi!
Jens Vagelpohl wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5 Aug 2007, at 20:15, yuppie 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
yuppie wrote:
AFAICS the premature GenericSetup 1.3 release has the biggest issues:
- There are also some usability issues (strange ordering; strange
interface names including '_tools' and '_content';
Ordering and dotted names are fixed now. This makes it much easier to
read the diffs.
Hi!
Jens Vagelpohl wrote:
On 2 Aug 2007, at 13:55, Wichert Akkerman wrote:
Previously yuppie wrote:
1.) Exporting the ISiteRoot utility, 'object' should be empty. But I get
this instead:
utility interface=Products.CMFCore.interfaces._content.ISiteRoot
object=SITE_ID/
2.) By
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5 Aug 2007, at 20:15, yuppie 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
Am 31.07.2007 um 17:17 schrieb Tres Seaver:
'imperative' indicates that the profile executes arbitrary Python
code;
'declarative' indecates that the profile applies external
configuration
data, read from one or more data files in the profile.
Running two imperative profiles, A and B, may
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
import them
Hi!
Jens Vagelpohl wrote:
On 20 Jul 2007, at 11:00, Wichert Akkerman wrote:
Previously Jens Vagelpohl wrote:
Next step: What needs fixing for the final?
There has been a surprising lack of response to this question. Since I
need a CMF 2.1-final for Plone in a few weeks that could be very
yuppie wrote:
Jens Vagelpohl wrote:
On 20 Jul 2007, at 11:00, Wichert Akkerman wrote:
Previously Jens Vagelpohl wrote:
Next step: What needs fixing for the final?
There has been a surprising lack of response to this question. Since I
need a CMF 2.1-final for Plone in a few weeks that could
Am 31.07.2007 um 15:51 schrieb yuppie:
AFAICS the premature GenericSetup 1.3 release has the biggest issues:
I'm behind the loop on GenericSetup having only encountered it when
writing a content type for a single site. I would appreciate an
explanation of the difference between
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Charlie Clark wrote:
Am 31.07.2007 um 15:51 schrieb yuppie:
AFAICS the premature GenericSetup 1.3 release has the biggest issues:
I'm behind the loop on GenericSetup having only encountered it when
writing a content type for a single site. I
Previously yuppie wrote:
Hi!
Jens Vagelpohl wrote:
On 20 Jul 2007, at 11:00, Wichert Akkerman wrote:
Previously Jens Vagelpohl wrote:
Next step: What needs fixing for the final?
There has been a surprising lack of response to this question. Since I
need a CMF 2.1-final for Plone
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
import them again. Has that been broken
Wichert Akkerman wrote:
Previously Jens Vagelpohl wrote:
Next step: What needs fixing for the final?
There has been a surprising lack of response to this question. Since I
need a CMF 2.1-final for Plone in a few weeks that could be very
positive news for me but I have a suspicion that some
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alright, I'm going to do the following today/tonight:
- - do a GS 1.3 beta and create a GS 1.3 branch, and put a release on
zope.org
- - point the GS external on the CMF 2.1 branch to the GS 1.3 beta tag
- - run all unit tests for the CMF 2.1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jens Vagelpohl wrote:
Alright, I'm going to do the following today/tonight:
- do a GS 1.3 beta and create a GS 1.3 branch, and put a release on
zope.org
- point the GS external on the CMF 2.1 branch to the GS 1.3 beta tag
- run all unit
27 matches
Mail list logo
