us humans can read quoted printable text while
base64 looks like line noice, and in my experience spamfilters tend to
consider base64 encoded emails more likely to spam.
Wichert.
--
Wichert Akkerman wich...@wiggy.net It is simple to make things.
http://www.wiggy.net/ It is hard
content object gets this
treatment.
Could it be that this considers dexterity content to be opaque items? I
have some code where events are recursively re-dispatched by CMF and I
suspect this is why.
Wichert.
--
Wichert Akkerman wich...@wiggy.net It is simple to make things.
http
have enough
time to work on it this week.
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http
.
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
Previously Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wichert Akkerman wrote:
I have a use case where I need to put additional restrictions on object
creation, in particular I need to restrict the maximum depth of items
inside of a container of a specific type
new features.
I looked at the code in zope.container and frankly it scared me. I found
the documentation and code hard to follow, and the usage of
sys._getframe() made me drop the idea of using it.
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http
Previously Wichert Akkerman wrote:
I have a use case where I need to put additional restrictions on object
creation, in particular I need to restrict the maximum depth of items
inside of a container of a specific type. The ideal place to put such a
restriction seems
I have a use case where I need to put additional restrictions on object
creation, in particular I need to restrict the maximum depth of items
inside of a container of a specific type. The ideal place to put such a
restriction seems to be the isConstructionAllowed method on the FTI.
Currently
Previously yuppie wrote:
Wichert Akkerman wrote:
I have a use case where I need to put additional restrictions on object
creation, in particular I need to restrict the maximum depth of items
inside of a container of a specific type. The ideal place to put such a
restriction seems
that's a bad idea please speak up.
I think we are targetting Plone 4 at CMF 2.2 and Zope 2.11 at the
moment, so that would be bad for us.
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/ It is hard to make things simple
a greater and greater
effort to ensure backwards compatibility for all kinds of
combinations. So, what do we want to support?
My vote for CMF 2.2: Zope 2.11 and 2.12
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net
not convinced this is a showstopper, so I plan to release 3.3
based on the current 3.3rc3 and delay this until 3.3.1.
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/ It is hard to make things simple
objects with multiple
workflows correctly.
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http
.
- GS 1.4.2.2 is used in Plone 3.2.2.
- GS 1.4.2.2 is used in Plone 3.3rc1.
- GS trunk (1.5) is used in Plone trunk (4.0).
I'm planning to switch to GS 1.5 for Plone 3.4.
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net
stored in the setup tool's list of completed steps.
-1
This is a radical change in behaviour, and I'm not convinced it is
better. There may be good reasons to skip certain upgrade steps when you
move from one source to another, which is no longer possible with your
proposal.
Wichert.
--
Wichert
.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See https
Previously Jens Vagelpohl wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 18, 2009, at 16:12 , Wichert Akkerman wrote:
Previously Miles wrote:
We have quite a lot of copy-and-paste code here in order to support
using a custom MemberData class for members in particular
.
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See
or managed in svn.zope.org, as long as there is the license is
acceptable.
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Zope-CMF maillist
Previously Jens Vagelpohl wrote:
On Mar 10, 2009, at 10:01 , Wichert Akkerman wrote:
Previously Jens Vagelpohl wrote:
In general, commercial adoption of a software stack is made easier if
it is not accompanied by a whole soup of different licenses. The
fewer
licenses, the better. I'm
.
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See https
solutions:
- add a BBB import to import from Globals
- from App.class_init import default__class_init__ as InitializeClass
Does anyone have preferences?
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/ It is hard to make things
Previously yuppie wrote:
Wichert Akkerman wrote:
Currently GenericSetup trunk no longer runs on Zope 2.10. If I try to
run the tests I get this:
File /src/Products.GenericSetup/Products/GenericSetup/registry.py, line
23, in ?
from App.class_init import InitializeClass
Previously Wichert Akkerman wrote:
Previously Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I would like to get a 1.5 release of GenericSetup out over the holidays.
Here is what I have on the roadmap:
- Clean up the sphinx docs for the package, incorporating
.
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See
Previously yuppie wrote:
Wichert Akkerman wrote:
Previously yuppie wrote:
If you really need to run GenericSetup on older versions I'd prefer your
first solution (BBB import from Globals) because it makes sure modules
are imported in the right order.
I see no good reasons
Previously Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wichert Akkerman wrote:
Previously Tres Seaver wrote:
Are there open bug reports on such problems? Also, we might not even
support running on Zope 2.10.x with this release, if it is too painful
to resolve
too many stylistic ones as well.
+1
This goes in two ways: some bits of CMFCore should probably be in
CMFDefault as well.
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple to make things.
http://www.wiggy.net/ It is hard to make things simple
Previously Raphael Ritz wrote:
Charlie Clark wrote:
Am 18.02.2009 um 21:51 schrieb Wichert Akkerman:
In my opinion a copy should produce a full copy, including all state
and
history.
Not sure I would agree here.
For a move (cutpaste) yes but for a copy I think
there are too
Previously Charlie Clark wrote:
Am 25.02.2009 um 14:18 schrieb Wichert Akkerman:
There are many use cases for both options. One aspect is that it is
extremely hard to not get the current behaviour. We had to hire
Philipp
to write z3c.unconfigure for us just to be able to create
Previously Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wichert Akkerman wrote:
Previously Charlie Clark wrote:
Am 25.02.2009 um 16:10 schrieb Wichert Akkerman:
The workflow tool is not a factor at all here. The problem is that CMF
registers some event handlers
.
Does it make sense to keep old workflow history records after copy and
paste? Or can we just remove the complete workflow_history attribute
before notifyCreated is called?
In my opinion a copy should produce a full copy, including all state and
history.
Wichert.
--
Wichert Akkerman wich
running under Python 2.5 (and maybe
even 2.6).
Anyone have other stuff they would like to see in the mix (and can help
land)?
I want to extend the upgrade step logic a bit to allow you to call
single steps from other profiles. Should be a simple change.
Wichert.
--
Wichert Akkerman wich
?
I don't like to remove CMF's portal_setup registration *if* CMF itself
is not affected by this issue.
Imho registering portal_setup as a utility as long as any CMF tool uses
self.REQUEST is problematic since it makes it impossible for
import/export steps to use such tools.
Wichert.
--
Wichert
Previously Jens Vagelpohl wrote:
On Nov 16, 2008, at 22:30 , Wichert Akkerman wrote:
Previously yuppie wrote:
I don't like to remove CMF's portal_setup registration *if* CMF
itself
is not affected by this issue.
Imho registering portal_setup as a utility as long as any CMF tool
including the possibility to specify the path (or
relative content URL) to the folder in ZMI.
Shouldn't it use restrictedTraverse? Is there a special reason you want
to bypass security?
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net
. This can be very useful when you run
upgrades for a base profile which load (steps from a) profile from an
add-on package.
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:
Previously Rob Miller wrote:
hi all,
i've got a GenericSetup branch called 'ra-depends-tag' with a working
implementation of a genericsetup:upgradeDepends ZCML tag. this tag can
be used anywhere that you could use a genericsetup:upgradeStep tag
directly
where possible?
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman
Previously Jens Vagelpohl wrote:
On Sep 23, 2008, at 17:01 , Wichert Akkerman wrote:
Currently CMFCore and zope.dublincore duplicate some of the DC
interfaces. zope.dublincore even has an ICMFDublinCore interface
explicitly dublicing CMFCore's version.
Are there any objections
Previously Martin Aspeli wrote:
Wichert Akkerman wrote:
Previously Martin Aspeli wrote:
Hi Yuppie,
1.) CMF add views adapt not only container and request, but also the
type info object. This way the views can't be accessed directly and
have
self.fti available.
This is quite
Previously Martin Aspeli wrote:
Wichert Akkerman wrote:
Previously Martin Aspeli wrote:
Wichert Akkerman wrote:
Previously Martin Aspeli wrote:
Hi Yuppie,
1.) CMF add views adapt not only container and request, but also the
type info object. This way the views can't be accessed
Previously Jens Vagelpohl wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 18, 2008, at 09:56 , Wichert Akkerman wrote:
I'm not the greatest artist in the world, if anyone dislikes a
particular icon please feel free to replace it with something that
makes sense to a normal
a concept of action-overrides: a
set of actions that override or extend the global list of actions for
a specific context. That is something that I've wanted a few times and
could replace per-type actions.
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net
) from its icon.
Easier customization - no need to let people touch the action itself?
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Zope-CMF
Previously Maurits van Rees wrote:
Currently this buildout (cmf-21 at least) pulls in
Products.GenericSetup 1.4.1 from the cheese shop. I am curious: why
is it not in the src/ here?
Why should it? GenericSetup is not a real part of CMF and has its own
releases.
Wichert.
--
Wichert Akkerman
when making changes? I'm using a simple buildout that pulls
them all in:
http://svn.dataflake.org/svn/sandboxes/cmf-21/
http://svn.dataflake.org/svn/sandboxes/cmf-trunk/
Can you move/copy those to svn.zope.org?
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make
Previously Jens Vagelpohl wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 10, 2008, at 07:53 , Wichert Akkerman wrote:
Previously Wichert Akkerman wrote:
Ah, I complained about that to Jens: he pinned the CMF eggs to an
exact
version of GenericSetup, which makes them
direction here.
GS introduces new features, but I am not aware of any backwards
incompatible changes. Am I correct in that?
GS trunk drops some long-deprecated bits which CMF isn't using anyway,
but 1.4 should be fully backwards compatible with 1.3.
Wichert.
--
Wichert Akkerman [EMAIL
',
u'http://namespaces.zope.org/genericsetup'
, u'exportStep')
/snip
It was probably pure luck that that used to work before: CMFCore's
testing.py forgot to load meta.zcml from GenericSetup. I've fixed that
and the tests run fine now.
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple
Previously Maurits van Rees wrote:
Wichert Akkerman, on 2008-09-08:
While working on plonenext I get an error when trying to install
the Products.CMFDefault egg. This is the buildout -vv output:
(...)
While:
Installing instance.
Getting distribution for 'Products.CMFDefault
Previously Wichert Akkerman wrote:
Previously Maurits van Rees wrote:
Wichert Akkerman, on 2008-09-08:
While working on plonenext I get an error when trying to install
the Products.CMFDefault egg. This is the buildout -vv output:
(...)
While:
Installing instance.
Getting
is not very informative. Does anyone know what might cause this?
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Zope-CMF maillist - Zope-CMF
later this month.
+1
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman
Previously Robert Niederreiter wrote:
When providing a metadata.xml file, GenericSetup's registerProfile
directive crashes if dependencies/dependencies is provided as empty
tag with a key error (GS v 1.4.1)
Can you submit a bugreport to launchpad?
Wichert.
--
Wichert Akkerman [EMAIL
a portal type's behaviour that are stored in
various places: versioning settings, markup configuration, workflow
chains, etc.
I suppose there is no reason not to use annotations on the FTI right
now; perhaps we should investigate migrating some things in that
direction.
Wichert.
--
Wichert Akkerman
://mail.zope.org/pipermail/cmf-tests/2008-July/009280.html
These are my fault; I'll look at them tonight.
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple
tips from someone who knows this code
well.
For some unknown reason CMF explicitly encoded that behaviour in
__bobo_traverse__. It's bitten Plone as well.
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make
that hurts GenericSetup
in several places: it is impossible to determine if a factory or an object
was registered. Without knowing that information it is also impossible
to reliably do an export. Once that has been corrected in zope.component
GenericSetup can be adjusted.
Wichert.
--
Wichert Akkerman
Previously Jens Vagelpohl wrote:
On Jun 11, 2008, at 14:31 , Wichert Akkerman wrote:
Previously Jens Vagelpohl wrote:
Hi guys,
I'm wondering about the need to provide tarballs for GenericSetup
through zope.org alongside the tarball on PyPI. It's extra work and
the GenericSetup pages
for Plone 3.1.x maintenance releases. We may
switch to the egg variant for Plone 3.2, but not before.
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple
Previously Maurits van Rees wrote:
Wichert Akkerman, on 2008-05-29:
Previously Philipp von Weitershausen wrote:
But personally I like having it inside the main
folder, so in your example above it would be
incf.applications/incf/applications/HISTORY.txt
There's some benefit
anyway and that can easily be
used to include everything in doc/ or other places.
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Zope-CMF maillist
Previously Maurits van Rees wrote:
Wichert Akkerman, on 2008-05-29:
Previously Maurits van Rees wrote:
Wichert Akkerman, on 2008-05-29:
Previously Philipp von Weitershausen wrote:
But personally I like having it inside the main
folder, so in your example above it would
Previously Maurits van Rees wrote:
Wichert Akkerman, on 2008-05-29:
Previously Maurits van Rees wrote:
Wichert Akkerman, on 2008-05-29:
Previously Maurits van Rees wrote:
Wichert Akkerman, on 2008-05-29:
Previously Philipp von Weitershausen wrote:
But personally I like having
see when I unpack
something. I don't want to be forced to delve into 3 or 4
subdirectories.
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple
head (checkout those
bruises!) for weeks on how to add a thumbnail of an existing image to
an edit form. Do I need to develop a special widget which will call
the appropriate method?
Perhaps collective.namedfile has a suitable widget.
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED
Previously Charlie Clark wrote:
Am 21.04.2008 um 08:59 schrieb Wichert Akkerman:
The eggified CMF already required setuptools to make sure the Products
namespace is setup correctly. Considering that entire python community
appears to be moving to egg, Zope2 is going to be distributed
will be using the eggified version.
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org
Previously yuppie wrote:
Wichert Akkerman wrote:
Previously yuppie wrote:
Until recently, the Products themselves didn't use setuptools. Revision
85287 (http://svn.zope.org/?rev=85287view=rev) changed that. It is no
longer possible to run CMF without setuptools installed
Plone 3.1rc1 is scheduled for release this Wednesday. I would like to
include a new GenericSetup release to get r84623 in. Would it be
possible for someone (Jens or Tres I assume) to make a new release?
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http
Previously Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wichert Akkerman wrote:
The improvements GenericSetup 1.4/trunk has over the 1.3 series are a
big part of Plone 3.1. With that moving towards it first alpha release
this Friday it would be practical
Previously Jens Vagelpohl wrote:
On Mar 7, 2008, at 09:37 , Wichert Akkerman wrote:
Previously Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wichert Akkerman wrote:
The improvements GenericSetup 1.4/trunk has over the 1.3 series
are a
big part of Plone 3.1
that.
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See
in the Zope 2.10 branch?
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See
, that's why I would have to do
the beta either tomorrow or after 1/1.
I see 2.1.1 final isn't out yet. Can you do that today or tomorrow? That
and a i18n test failure are the the only blockers for Plone 3.0.5 at the
moment.
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make
Previously Damien Baty (ML) wrote:
Hello,
Le 27/12/07 9:49, Wichert Akkerman a écrit :
Previously Damien Baty (ML) wrote:
[...]
For the record, I have proposed a patch that let us automatically
register a permission if the profile explicitly asks for it, with
something like
Previously Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Damien Baty (ML) wrote:
Hello,
Le 27/12/07 9:49, Wichert Akkerman a écrit :
Previously Damien Baty (ML) wrote:
[...]
For the record, I have proposed a patch that let us automatically
register
Previously Wichert Akkerman wrote:
Previously yuppie wrote:
But I agree there should be a way to remove obsolete and broken local
steps. A method that removes local duplicates of global steps and a
method that removes broken steps would be useful. Not sure if they
should be run
on.
That suggests that registering permissions in a GS profile is too late
in the game.
To me it makes a lot more sense to register permissions and their
default roles in zcml.
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard
Previously yuppie wrote:
Hi!
Wichert Akkerman wrote:
Previously yuppie wrote:
GenericSetup trunk has global step registries. I propose to use the new
ZCML directive for registering all GenericSetup and CMF import and
export steps globally. And to remove the import_steps.xml
that is.
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
step, and
adding new ones and removing and adding back only those that have changed.
See https://bugs.launchpad.net/zope-cmf/+bug/161682
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple
=my.package.SomePermission
title=My Package: Some permission
/
I _think_ that should then let you then import a rolemap for it.
That only creates a bridge between Z2 and Z3 permissions.
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net
.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http
Previously Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wichert Akkerman wrote:
I did some work on a wichert-dependencies branch for GenericSetup today.
It works quite simple: runAllImportStepsFromProfile will now look for
required contexts in the profile metadata
Previously Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wichert Akkerman wrote:
I did some work on a wichert-dependencies branch for GenericSetup today.
It works quite simple: runAllImportStepsFromProfile will now look for
required contexts in the profile metadata
://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature requests
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple
. AFAICS this supersedes
the import step version approach.
+1
I want to suggest also deprecating the metadata logic that uses
version.txt profile version number if there is no metadata.xml which
defines one.
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http
.
+1, especially if you can merge the changes from GS trunk into
Products.GenericSetup and put a clear warning in the old location.
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple
look
at collective.revelation for example.
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http
this is harmless.
Exporting should always be a safe operation.
- If we deprecate profile-based registration and eventually remove it
we can simplify a lot of code.
I intend to merge this branch into trunk next week.
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things
, ie. real Python code?
It's called acquisition and it works everywhere. Try it.
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Zope-CMF
the wrong place: when the instance is created it is
not placed in an acquisition context yet.
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple
Previously Charlie Clark wrote:
Am 30.10.2007 um 17:40 schrieb Wichert Akkerman:
__init__ is indeed the wrong place: when the instance is created it is
not placed in an acquisition context yet.
That would indeed explain things!!! Is it okay to call a method which
does this from
that they are not is useful: it allows you to move a bugreport
from one product to another.
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Zope-CMF maillist
Previously Jens Vagelpohl wrote:
On 25 Oct 2007, at 12:40, Wichert Akkerman wrote:
I remember one of the popular objections was that the launchpad mails
did not contain as much context as the current collector emails. Has
that changed?
I've been going back and forth with Steve about
.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http
and protect that
with a permission.
Wichert.
--
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org
1 - 100 of 167 matches
Mail list logo
