-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/16/2011 11:55 AM, Sascha Welter wrote:
(Fri, Apr 15, 2011 at 02:39:26PM +0200) Hanno Schlichting
wrote/schrieb/egrapse:
I assume this kind of thing has been discussed and the decision has been
taken on judging backwards compatibility vs.
On Sunday 17 April 2011, Tres Seaver wrote:
Moving a big old application across multiple major versions at onece
of any platform is likely to be painful: even projects which are
careful about backward compatibility (Zope has historically been very
good at this) will have issued deprecation
Am 17.04.2011, 13:46 Uhr, schrieb William Heymann k...@aesaeion.com:
I have spent some time looking at other frameworks and most just don't
look very promising to me. For grok my biggiest issue was fail open. It
looks like the default is allow everything unless explicitely denied and
I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
(Sun, Apr 17, 2011 at 07:10:07AM -0400) Tres Seaver wrote/schrieb/egrapse:
Moving a big old application across multiple major versions at onece
of any platform is likely to be painful:
Tres,
I know how to move an app to newer zope versions. My
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
(Sun, Apr 17, 2011 at 02:58:12PM +0200) Charlie Clark wrote/schrieb/egrapse:
As for an explanation of how to use events or simply getting a grasp of
using the ZCA in Zope 2 I can highly recommend Philip von Weiterhausen's
book on Zope 3. In
Am 17.04.2011, 16:08 Uhr, schrieb Sascha Welter zopel...@betabug.ch:
The term CatalogPathAwareness was not found in the archives of
zope-dev in the last 6 years or so. Can any zope developer deprecate or
remove things on their own without discussion?
Technically, yes. In general there is
Am 17.04.2011, 17:15 Uhr, schrieb Sascha Welter zopel...@betabug.ch:
Charlie,
I really like this quote from the Pyramid documentation:
While the ZCA is an excellent tool with which to build a framework such
as Pyramid, it is not always the best tool with which to build an
application due to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/17/2011 10:08 AM, Sascha Welter wrote:
(Sun, Apr 17, 2011 at 07:10:07AM -0400) Tres Seaver wrote/schrieb/egrapse:
Moving a big old application across multiple major versions at onece
of any platform is likely to be painful:
Tres,
I know
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tres and all,
so it looks like I came over as a total jerk who rides a personal attack
on Hanno. That is of course not my intention, not at all. I am sorry for
that.
I am grateful for every improvement to the code and it looks like Hanno
did a great
On Sat, Apr 16, 2011 at 3:36 AM, William Heymann k...@aesaeion.com wrote:
What about developers who build on zope 2.x
and use it very successfully, what should they switch to?
My personal recommendation would be to either use Django or Pyramid.
If you want to stay even closer to Zope, Grok
(Fri, Apr 15, 2011 at 02:39:26PM +0200) Hanno Schlichting wrote/schrieb/egrapse:
I assume this kind of thing has been discussed and the decision has been
taken on judging backwards compatibility vs. the benefits of doing this?
The particular code was unused for several years,
Sigh. Sorry
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Zope Developers,
I've asked about this on the zope@ list, without getting any replies.
Talking about it in #zope, I decided that maybe I will have to ask here
from another point of view.
As I was testing moving a big, old application to Zope
On Fri, Apr 15, 2011 at 12:05 PM, Sascha Welter zopel...@betabug.ch wrote:
Looking at http://pypi.python.org/pypi/zope.lifecycleevent I see some
examples about calling those notify() events, but nothing that would
tell me how to replace CatalogPathAware with this stuff. Googling for
On Friday 15 April 2011, Hanno Schlichting wrote:
I don't think there's any examples. Documentation for developing with
current Zope 2 is virtually non-existant.
How are people expected to upgrade to new code that replaces the old
functionality if there is no documentation for it? What is
14 matches
Mail list logo
