-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05.01.10 08:36, Martin Aspeli wrote:
+1. It puts the final nail in the Zope 3 coffin and allows a reborn
vampire to emerge from slumber.
Ok, we all hate the damage that Zope 3 did and I have no problem to call
one of the x Zope Webframeworks
Hi there,
On 01/04/2010 07:23 PM, Baiju M wrote:
Hi All,
I am proposing to call Zope 3 - the web frame work
as BlueBream. The main use for name is documentation.
But the package named bluebream will not provide
any part of framework code by itself. All the framework
code will be
Jan Ulrich Hasecke wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05.01.10 08:36, Martin Aspeli wrote:
+1. It puts the final nail in the Zope 3 coffin and allows a reborn
vampire to emerge from slumber.
Ok, we all hate the damage that Zope 3 did and I have no problem to call
one
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Aspeli wrote:
Jan Ulrich Hasecke wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05.01.10 08:36, Martin Aspeli wrote:
+1. It puts the final nail in the Zope 3 coffin and allows a reborn
vampire to emerge from slumber.
Ok, we all
Andreas Jung wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Baiju M wrote:
Hi All, I am proposing to call Zope 3 - the web frame work as
BlueBream. The main use for name is documentation. But the
package named bluebream will not provide any part of framework
code by itself. All the
it took me hours to find out that i had the same issue in a plone-4.0a3
buildout until i found this thread
in the meantime 2.12.2 is released so all one needs to do is to modify
http://dist.plone.org/release/4.0a3/versions.cfg to use zope-2.12.2:
[buildout]
extends =
robert rottermann wrote:
[snip]
all the other items bear so little market value that even an insider can not
place them.
Therefore I think either of the two should be part of any new packages name
meant to be recognized by non Zope affectionados.
Bluebream for Zope
I've sometimes called
Hermann Himmelbauer wrote:
But I have to further state that I'm locked into Zope 3.4.0 as the support
for
Python 2.4 was dropped, so I can't upgrade to the current ZTK.
This is a surprise to me. I thought we still supported Python 2.4
Regards,
Martijn
Hi Tres,
You don't seem to get what I kept telling you over and over. I'm
therefore going to be more blunt.
I don't want to use zope.app packages in Grok. Grok wants to get rid of
zope.app packages. That's the very idea. We pushed this from the start.
I spent a huge amount of time to make
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martijn Faassen wrote:
Hey Tres,
Tres Seaver wrote:
You're kidding, right?
[snip]
My self-interest? Not really: you are appealing to my altruism, in the
fact that I care about the *broader* Zope community (broader than Zope2,
Grok,
On Tue, Jan 5, 2010 at 11:28, Andreas Jung li...@zopyx.com wrote:
I associate blueberry bagels with cream cheese when reading the name
Bluebream.
Yummy!
--
Lennart Regebro: Python, Zope, Plone, Grok
http://regebro.wordpress.com/
+33 661 58 14 64
___
Summary of messages to the zope-tests list.
Period Mon Jan 4 12:00:00 2010 UTC to Tue Jan 5 12:00:00 2010 UTC.
There were 6 messages: 6 from Zope Tests.
Unknown
---
Subject: UNKNOWN : Zope-2.12 Python-2.6.4 : Linux
From: Zope Tests
Date: Mon Jan 4 20:45:19 EST 2010
URL:
Am Dienstag 05 Januar 2010 11:58:38 schrieb Martijn Faassen:
Hermann Himmelbauer wrote:
But I have to further state that I'm locked into Zope 3.4.0 as the
support for Python 2.4 was dropped, so I can't upgrade to the current
ZTK.
This is a surprise to me. I thought we still supported
Hermann Himmelbauer wrote:
Am Dienstag 05 Januar 2010 11:58:38 schrieb Martijn Faassen:
Hermann Himmelbauer wrote:
But I have to further state that I'm locked into Zope 3.4.0 as the
support for Python 2.4 was dropped, so I can't upgrade to the current
ZTK.
This is a surprise to me. I thought
Jens Vagelpohl wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hermann Himmelbauer wrote:
Am Montag 04 Januar 2010 23:10:05 schrieb Tres Seaver:
Martijn Faassen wrote:
Obviously I cannot *force* ZTK
maintainers to worry about this. Instead I'm appealing to your
self-interest. And of
Jens Vagelpohl wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martijn Faassen wrote:
Hey Tres,
Tres Seaver wrote:
You're kidding, right?
[snip]
My self-interest? Not really: you are appealing to my altruism, in the
fact that I care about the *broader* Zope community (broader
Martijn Faassen wrote:
[snip]
But I do see that Python 2.4 has a failed test, so we do need to fix that.
Some of those failure appears to be because some code was switched over
to the Python standard library pprint from the version in zope.testing,
and in Python 2.4 that doesn't sort
Martijn Faassen wrote:
Hey Tres,
Tres Seaver wrote:
You're kidding, right?
[snip]
My self-interest? Not really: you are appealing to my altruism, in the
fact that I care about the *broader* Zope community (broader than Zope2,
Grok, Plone, or whatever. Neither of my chosen platforms
On Monday 04 January 2010, Baiju M wrote:
I am proposing to call Zope 3 - the web frame work
as BlueBream. The main use for name is documentation.
But the package named bluebream will not provide
any part of framework code by itself. All the framework
code will be in zope and
Jens Vagelpohl wrote:
How is that any different from people who won't use the ZTK because they
don't want to deal with any zope.app* baggage?
We have a proposal for dealing with that now: To maintain two KGS', one
for ZTK and one for ZopeApp.
We can and should run tests for both, and ensure
On Sunday 03 January 2010, Martijn Faassen wrote:
So here's my proposed solution for the ZTK shrinking issue:
I really like the proposed solution of the small ZTK and an addon zope.app
superset. It provides me with an example how to create other supersets. And I
do agree that a migration path
Am Dienstag 05 Januar 2010 14:37:51 schrieb Martijn Faassen:
Hermann Himmelbauer wrote:
Am Dienstag 05 Januar 2010 11:58:38 schrieb Martijn Faassen:
Hermann Himmelbauer wrote:
But I have to further state that I'm locked into Zope 3.4.0 as the
support for Python 2.4 was dropped, so I can't
2010/1/5 Hermann Himmelbauer du...@qwer.tk:
Am Dienstag 05 Januar 2010 14:37:51 schrieb Martijn Faassen:
Hermann Himmelbauer wrote:
Am Dienstag 05 Januar 2010 11:58:38 schrieb Martijn Faassen:
Hermann Himmelbauer wrote:
But I have to further state that I'm locked into Zope 3.4.0 as the
Am Dienstag 05 Januar 2010 16:12:02 schrieb Lennart Regebro:
On Tue, Jan 5, 2010 at 16:10, Hermann Himmelbauer du...@qwer.tk wrote:
Hmmm. Bad luck for me.
It would be interesting to know why you have to use Python 2.4.
My application relies on the MaxDB database (former SAP-DB). They offer a
Am Dienstag 05 Januar 2010 16:18:17 schrieb Andreas Jung:
Lennart Regebro wrote:
On Tue, Jan 5, 2010 at 16:10, Hermann Himmelbauer du...@qwer.tk
wrote:
Hmmm. Bad luck for me.
It would be interesting to know why you have to use Python 2.4.
Dropping Python 2.4 support asap for any
On Tue, Jan 5, 2010 at 9:29 AM, Stephan Richter
srich...@cosmos.phy.tufts.edu wrote:
On Monday 04 January 2010, Baiju M wrote:
I am proposing to call Zope 3 - the web frame work
as BlueBream. The main use for name is documentation.
But the package named bluebream will not
On Sun, Jan 3, 2010 at 3:51 PM, Martijn Faassen faas...@startifact.com wrote:
Hi there,
So here's my proposed solution for the ZTK shrinking issue:
The ZTK branch 'faassen-smaller' contains Hanno's smaller ZTK. Since
Zope 2 forked the ZTK in response and continued to make changes to their
2010/1/5 Martin Aspeli optilude+li...@gmail.com:
Andreas Jung wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Baiju M wrote:
Hi All, I am proposing to call Zope 3 - the web frame work as
BlueBream. The main use for name is documentation. But the
package named bluebream will not
Jim Fulton wrote:
- When we refactor zope.app.foo to be zope.foo (or something else),
rather than changing
zope.app.foo to use zope.foo, just leave zope.app.foo alone, if possible.
One problem with this is that if you have interfaces for which there are
components registered, this can
On Tue, Jan 5, 2010 at 16:55, Gediminas Paulauskas mene...@pov.lt wrote:
If we released Zope 3 the web framework as version 3.5, little would
change for existing Zope 3 users since it still includes all zope.app
packages with backward compatibility imports. Wasn't this the plan
last year? I
I like Bream. BlueBream or Blue Bream.
Just change the name Zope3 so we get over it eventually.
I'm a zope3 user btw !
2010/1/5 Lennart Regebro rege...@gmail.com:
On Tue, Jan 5, 2010 at 16:55, Gediminas Paulauskas mene...@pov.lt wrote:
If we released Zope 3 the web framework as version 3.5,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martijn Faassen wrote:
Hermann Himmelbauer wrote:
Am Dienstag 05 Januar 2010 11:58:38 schrieb Martijn Faassen:
Hermann Himmelbauer wrote:
But I have to further state that I'm locked into Zope 3.4.0 as the
support for Python 2.4 was dropped, so I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martijn Faassen wrote:
Hey Tres,
Tres Seaver wrote:
You're kidding, right?
[snip]
My self-interest? Not really: you are appealing to my altruism, in the
fact that I care about the *broader* Zope community (broader than Zope2,
Grok,
Baiju M wrote:
On Mon, Jan 4, 2010 at 11:53 PM, Baiju Mmba...@zeomega.com wrote:
Hi All,
I am proposing to call Zope 3 - the web frame work
as BlueBream.
I am unable to make a conclusion out of this discussion as many
real users of Zope 3 - the web frame work is not given +1
But
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martijn Faassen wrote:
You don't seem to get what I kept telling you over and over. I'm
therefore going to be more blunt.
I don't want to use zope.app packages in Grok. Grok wants to get rid of
zope.app packages. That's the very idea. We
Martin Aspeli wrote:
Baiju M wrote:
On Mon, Jan 4, 2010 at 11:53 PM, Baiju Mmba...@zeomega.com wrote:
Hi All,
I am proposing to call Zope 3 - the web frame work
as BlueBream.
I am unable to make a conclusion out of this discussion as many
real users of Zope 3 - the web frame
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martijn Faassen wrote:
Hi there,
25 zope.app packages are broken due to changes in zope.publisher 3.12.
zope.publisher had some components factored out of it into zope.login.
I fixed zope.app.exception: it could be fixed by adding the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Maurits van Rees wrote:
Log message for revision 107689:
Fixed possible TypeError while sending multipart emails.
Changed:
U Zope/branches/2.12/doc/CHANGES.rst
U Zope/branches/2.12/src/Products/MailHost/MailHost.py
U
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tres Seaver wrote:
Maurits van Rees wrote:
Log message for revision 107689:
Fixed possible TypeError while sending multipart emails.
Changed:
U Zope/branches/2.12/doc/CHANGES.rst
U Zope/branches/2.12/src/Products/MailHost/MailHost.py
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Malthe Borch wrote:
Log message for revision 107710:
Fixed a calling convention oddity.
Changed:
U five.pt/trunk/CHANGES.txt
U five.pt/trunk/src/five/pt/patches.py
-=-
snip
Modified: five.pt/trunk/src/five/pt/patches.py
2009/12/31 Martin Aspeli optilude+li...@gmail.com:
Hi,
A few of us are playing with some caching tools, trying to get to a more
sane and less monkey patch-laden approach than CacheFu
(Products.CacheSetup), for use with Zope 2.12.
It is relatively easy to set response headers, e.g. in an
Hi All,
Thanks to all those who participated in this discussion so far.
I will try to make baby steps for the project. So, for time being
I will focus on the getting started story (which is somewhat ready)
then documentation, a small website ( http://bluebream.zope.org )
and before 1.0
FYI, I just made two new releases:
zope.schema 3.6.1
zope.configuration 3.7.1
These releases provide basic compatibility with Jython.
- C
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or
Laurence Rowe wrote:
2009/12/31 Martin Aspelioptilude+li...@gmail.com:
Hi,
A few of us are playing with some caching tools, trying to get to a more
sane and less monkey patch-laden approach than CacheFu
(Products.CacheSetup), for use with Zope 2.12.
It is relatively easy to set response
On Wed, Jan 6, 2010 at 8:39 AM, Chris McDonough chr...@plope.com wrote:
FYI, I just made two new releases:
zope.schema 3.6.1
zope.configuration 3.7.1
These releases provide basic compatibility with Jython.
Congrats! this is great step towards supporting other Python implementations.
I
45 matches
Mail list logo
