Martin Aspeli wrote:
Tres Seaver wrote:
That said, I suppose this should be either a conditional import or
moved to a higher level altogether.
- -1 to the conditional import; + 1 to moving the code.
Agree.
That sounds like the cleanest solution to me too.
Any idea on how this will be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martijn Faassen wrote:
Martin Aspeli wrote:
Tres Seaver wrote:
That said, I suppose this should be either a conditional import or
moved to a higher level altogether.
- -1 to the conditional import; + 1 to moving the code.
Agree.
That
Martijn Faassen wrote:
Martin Aspeli wrote:
Martijn Faassen wrote:
[snip]
So, what's the plan to clean up this mess? Can the Plone specific
stuff be cleared up from the branches into a Plone-specific package
and a new release be made that works for both Plone and the rest of
the Zope world?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Aspeli wrote:
Martijn Faassen wrote:
Martin Aspeli wrote:
Martijn Faassen wrote:
[snip]
So, what's the plan to clean up this mess? Can the Plone specific
stuff be cleared up from the branches into a Plone-specific package
and a new
Tres Seaver wrote:
That said, I suppose this should be either a conditional import or moved
to a higher level altogether.
- -1 to the conditional import; + 1 to moving the code.
Agree.
It seems to me it's also in the best interest of the Plone developers to
have this cleaned up, right?
Martijn Faassen wrote:
Hi there,
So, I am trying to look at five.customerize in the context of Silva. I
look at the SVN, and see the trunk is significantly older than various
Plone-related branches. Hm, odd.
I thought, let's download the 0.2 sources from the cheeseshop. I
download them.
Martin Aspeli wrote:
Martijn Faassen wrote:
[snip]
So, what's the plan to clean up this mess? Can the Plone specific
stuff be cleared up from the branches into a Plone-specific package
and a new release be made that works for both Plone and the rest of
the Zope world?
I thought it was ...
