Hi,
Now when zope refactoring is in progress, would it be possible to refactor
zope.app.generations package so there would be for example package
zope.generations that would depend only on ZODB3 package ?
I'm using zope.app.generations to upgrade the DB schema in my web project, and
in future
Previously Martin Aspeli wrote:
Wichert Akkerman wrote:
To stir things up: I would like to suggest renumbering the next Zope 2
release to Zope 4. That reflects the large refactoring that is being
done to clean up the codebase and fully eggify Zope. There are enough
changes to warrant a
Previously Shane Hathaway wrote:
discussion type=bikeshed
Tres Seaver wrote:
WRT the Framework name: framework is a misleading name for the
collection of packages salvaged from the new Coke effort: it is
actually a *bunch* of frameworks, in the classic software engineering
sense,
Wichert Akkerman wrote:
Previously Shane Hathaway wrote:
discussion type=bikeshed
Tres Seaver wrote:
WRT the Framework name: framework is a misleading name for the
collection of packages salvaged from the new Coke effort: it is
actually a *bunch* of frameworks, in the classic software
Wichert Akkerman wrote:
Previously Martin Aspeli wrote:
Wichert Akkerman wrote:
To stir things up: I would like to suggest renumbering the next Zope 2
release to Zope 4. That reflects the large refactoring that is being
done to clean up the codebase and fully eggify Zope. There are enough
When i speak about zope with my friends or tell about zope to my boss i allways
use Zope Framework name.
Zope Framework was from beginning the natural name for zope3 for me.
When i thing about Zope3, i think about Zope Framework
When i thing about Zope2, i think about Zope2
Just my 0.02 cents
Zope Toolkit is a good name. But so is Zope Framework. And honestly,
it's more a framework than a toolkit. A toolkit is a collection of
reasonably independent tools. OK, so Zope Framework is actually loads
of frameworks, one for components, one for security one for web forms,
and this and that.
Summary of messages to the zope-tests list.
Period Wed Apr 8 12:00:00 2009 UTC to Thu Apr 9 12:00:00 2009 UTC.
There were 8 messages: 8 from Zope Tests.
Test failures
-
Subject: FAILED (errors=1) : Zope-trunk-alltests Python-2.6.1 : Linux
From: Zope Tests
Date: Wed Apr 8 21:02:08
Tres Seaver wrote:
Hanno Schlichting wrote:
Lennart Regebro wrote:
So it's highly likely that Zope 2.12 is the last release of Zope2 that
Plone is going to use. Maybe a Zope 2.13 once Python 2.7 is released
might be of interest to Plone. But otherwise I don't see any reason for
a new Zope
Hey All,
Is this buildout sufficient to run all the Zope 2 tests on trunk:
[buildout]
parts = test
extends =
http://svn.zope.org/*checkout*/Zope/tags/2.12.0a1/versions-zope2.cfg
develop = Zope
# Zope is a checkout of:
# svn+ssh://chr...@svn.zope.org/repos/main/Zope/trunk
[test]
recipe =
On Apr 8, 2009, at 11:34 PM, Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hanno Schlichting wrote:
Lennart Regebro wrote:
This is only mildly confusing. It can also only get better with
time,
as Plone seems to continue away from Zope 2 and onto the framework,
Hi,
Shane Hathaway wrote:
Hanno Schlichting wrote:
Wichert Akkerman wrote:
I'ld rather not see a whole slew of extra packagse appear. I also
wonder
how the extra number of packages and increasing size of sys.path
influence performance and restrictions on environments like GAE.
For
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lennart Regebro wrote:
On Thu, Apr 9, 2009 at 05:34, Tres Seaver tsea...@palladion.com wrote:
Hanno Schlichting wrote:
The current line of thinking for Plone is about this: Plone 4 will still
run on Zope2. Plone 5 will run on Python 3.x and not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Fulton wrote:
On Apr 8, 2009, at 11:29 PM, Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Aspeli wrote:
Wichert Akkerman wrote:
To stir things up: I would like to suggest renumbering the next
Zope 2
release
Hi
Just on the zope in gae.
I have been hacking away at getting a core of zope running under gae.
(one example is http://baon.appspot.com/ which was a port of an old
portal_toolkit/cmf 1.0 site I used as an excercise)
I am currently using the following packages
app (completely gutted)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Fulton wrote:
On Apr 8, 2009, at 11:34 PM, Tres Seaver wrote:
Plone could run on something like the Zope Framework without running
on Zope 2.
That would be feasible, except that a ton of Plone's features depend on
Zope2-specific machinery.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Zope Tests Summarizer wrote:
Summary of messages to the zope-tests list.
Period Wed Apr 8 12:00:00 2009 UTC to Thu Apr 9 12:00:00 2009 UTC.
There were 8 messages: 8 from Zope Tests.
Test failures
-
Subject: FAILED (errors=1)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lacko Roman wrote:
Now when zope refactoring is in progress, would it be possible to
refactor zope.app.generations package so there would be for example
package zope.generations that would depend only on ZODB3 package ?
+1.
I'm using
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tobias Rodäbel wrote:
Hi,
Shane Hathaway wrote:
Hanno Schlichting wrote:
Wichert Akkerman wrote:
I'ld rather not see a whole slew of extra packagse appear. I also
wonder
how the extra number of packages and increasing size of
Hi,
I just tried to check out the new 1.9.x branch of z3c.form (thanks
Stephan!), but it won't build with Python 2.4 (I need this to work with
Plone, so 2.4 is a must):
$ ./bin/buildout
Develop: '/users/optilude/Development/Plone/Code/Products/z3c.form/.'
Unused options for buildout:
Tres Seaver wrote:
I don't know how the 'alltests' script is being built, or I would have
run the tests myself and found the failure.
You run bin/buildout -c alltests.cfg and then bin/alltests
Hanno
___
Zope-Dev maillist - Zope-Dev@zope.org
On Thursday 09 April 2009, Martin Aspeli wrote:
Clearly, I'm getting too new a version of RestrictedPython, but this is
running against the 3.4 KGS, so I don't see how that could really happen.
This is not a problem. Ignore those errors as they happen in the Python 2.6
support code.Everything
Hi All,
Apologies for the current test failure on trunk, why doesn't the
following testrunner run the zdaemon tests?
[buildout]
parts = test
extends =
http://svn.zope.org/*checkout*/Zope/tags/2.12.0a1/versions-zope2.cfg
versions = versions
develop = Zope zdaemon
[versions]
setuptools = 0.6c9
Jim Fulton wrote:
If not, I'll change it on trunk...
Please just remove that trove classifier.
Done.
Chris
--
Simplistix - Content Management, Zope Python Consulting
- http://www.simplistix.co.uk
___
Zope-Dev maillist -
Chris Withers wrote:
Apologies for the current test failure on trunk, why doesn't the
following testrunner run the zdaemon tests?
The testrunner recipe only puts the things in its own eggs section onto
the test path, so you need to do:
[test]
recipe = zc.recipe.testrunner
eggs =
Zope2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Withers wrote:
Hi All,
Apologies for the current test failure on trunk, why doesn't the
following testrunner run the zdaemon tests?
[buildout]
parts = test
extends =
Hanno Schlichting wrote:
Chris Withers wrote:
Apologies for the current test failure on trunk, why doesn't the
following testrunner run the zdaemon tests?
The testrunner recipe only puts the things in its own eggs section onto
the test path,
Ah, I only just got that :-)
Okay, so 'eggs'
Tres Seaver wrote:
$ bin/buildout -c alltests.cfg
$ bin/alltests
Any reason alltests.cfg isn't in the root buildout.cfg?
(not that I'm using the root buildout.cfg either...)
Chris
--
Simplistix - Content Management, Zope Python Consulting
- http://www.simplistix.co.uk
Hey,
Joy, another naming discussion. Oh well, I started it. :)
Zope Toolkit is better name than Zope Framework. I'm fine with renaming
Zope Framework to Zope Toolkit if:
* someone goes and changes the name in:
* the Zope Framework sphinx documentation in SVN
* renames the SVN directory
Hey there,
Tim Hoffman wrote:
[snip]
One question before I go. I had to replace about 90% of
zope.security (well get rid of it)
what would be the best way of specifying a replacement for a core
package like zope.security rather than just replacing it.
If I wanted to share this work it
Martijn Faassen wrote:
If nobody volunteers to do this (feel free to organize more volunteers),
we'll stick with Zope Framework.
Let me know if you're going to do this and when you're done.
FWIW, I think this particular pile of libraries is in fact best
described by the name framework,
I can't believe no one's suggested Zope Mega, yet.
Chris
On Thu, Apr 9, 2009 at 4:25 PM, Martijn Faassen faas...@startifact.comwrote:
Hey,
Joy, another naming discussion. Oh well, I started it. :)
Zope Toolkit is better name than Zope Framework. I'm fine with renaming
Zope Framework to
On Thu, Apr 9, 2009 at 23:07, Chris Rossi ch...@archimedeanco.com wrote:
I can't believe no one's suggested Zope Mega, yet.
It sounds stupid.
The Zope Ultra Component Framework Toolkit, though, THAT's a name with panache!
--
Lennart Regebro: Python, Zope, Plone, Grok
On 4/9/09 4:25 PM, Martijn Faassen wrote:
Hey,
Joy, another naming discussion. Oh well, I started it. :)
Zope Toolkit is better name than Zope Framework. I'm fine with renaming
Zope Framework to Zope Toolkit if:
* someone goes and changes the name in:
* the Zope Framework sphinx
34 matches
Mail list logo
