Re: [Zope-dev] Re: Let's fix the damned website
Previously Martin Aspeli wrote: Chris Withers wrote: Martijn Faassen wrote: Yeah, I know this is really a me too post, but I think we should err on the side of conventional for our website. We can't go from out-of-date boring to cutting edge hip in one giant leap; it won't be believable. Let's stick with what people know from other sites, and emphasize our serious rock-solid powerful flexibility experience thing. + sys.maxint A few frills here and there are permitted, of course. Actually, no frills please. They just come back to bite us every damned time. It looks like we're gonna get lumbered with Plone again but can we please please please make sure it's stable, conservative, maintainable release rather than some bleeding edge thing that becomes a total maintenance dead end? Yes. That's the point. It's vanilla Plone (well, one custom content type for the feature that fronts each section, but it's trivial) with a simple skin, not the FrankePlone that runs the old site. As a case in point, Wichert upgraded it from 3.0 to 3.1rc in about ten minutes. More like two minutes - the rest of the time was spent setting up supervisord for the installation. Also note that the entire deployment (except for the Data.fs of course) is available on svn.zope.org. Wichert. -- Wichert Akkerman [EMAIL PROTECTED]It is simple to make things. http://www.wiggy.net/ It is hard to make things simple. ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: Let's fix the damned website
Martin Aspeli wrote: Yes. That's the point. It's vanilla Plone (well, one custom content type for the feature that fronts each section, but it's trivial) with a simple skin, not the FrankePlone that runs the old site. As a case in point, Wichert upgraded it from 3.0 to 3.1rc in about ten minutes. Yes, because obviously 3.1rc is a stable, conservative, release... *sigh* Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: Let's fix the damned website
Previously Chris Withers wrote: Martin Aspeli wrote: Yes. That's the point. It's vanilla Plone (well, one custom content type for the feature that fronts each section, but it's trivial) with a simple skin, not the FrankePlone that runs the old site. As a case in point, Wichert upgraded it from 3.0 to 3.1rc in about ten minutes. Yes, because obviously 3.1rc is a stable, conservative, release... Chris, if you feel you can do better you're welcome to volunteer to help out. In the meantime I'ld like to have that I have a decent grasp of the stability of various Plone releases. Wichert. -- Wichert Akkerman [EMAIL PROTECTED]It is simple to make things. http://www.wiggy.net/ It is hard to make things simple. ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Let's fix the damned website
Chris Withers wrote: Martin Aspeli wrote: Yes. That's the point. It's vanilla Plone (well, one custom content type for the feature that fronts each section, but it's trivial) with a simple skin, not the FrankePlone that runs the old site. As a case in point, Wichert upgraded it from 3.0 to 3.1rc in about ten minutes. Yes, because obviously 3.1rc is a stable, conservative, release... *sigh* The site's not live yet. I have no interest in a further discussion about technology. We are where we are. I'm confident that we've made an appropriate platform choice, but that choice is only 10% of this effort. We need to focus on content, messages and structure. Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
AW: [Zope-dev] Status of zam packages
Hi David, Chris Betreff: Re: [Zope-dev] Status of zam packages zam (zope application manager) is reimplementation of sorts of the z3 zmi using a pagelet and form layers and with a plugin architecture and api. I have been working with it a bit but not sure how stable the api is so that I can build upon it which is what I am doing. Give me another two weeks and I hope to get ready for a initial release. Some tests break right now because I added a contets.html view which depends on z3c.table and z3c.contents. I think I will skip that dependency since probably not everybody will use zc.table or z3c.contents Darryl also did some improvments on a branch of z3c.contents which we need to merge back before we do a release. If this is done, ZAM should be stable enough for production. Regards Roger Ineichen Chris Withers wrote: David Pratt wrote: I am hoping I can get a bit of an update on zam packages on zope svn. Many thanks. What is zam? Chris ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Let's fix the damned website
Chris Withers wrote: Martijn Faassen wrote: [snip] A few frills here and there are permitted, of course. Actually, no frills please. They just come back to bite us every damned time. It looks like we're gonna get lumbered with Plone again but can we please please please make sure it's stable, conservative, maintainable release rather than some bleeding edge thing that becomes a total maintenance dead end? Ah, I didn't mean feature-frills, I meant design-frills. I agree we should be cautious about features. The grok.zope.org Plone site works quite well so far and takes a conservative approach. Regards, Martijn ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Zope Tests: 5 OK
Summary of messages to the zope-tests list. Period Mon Apr 7 11:00:00 2008 UTC to Tue Apr 8 11:00:00 2008 UTC. There were 5 messages: 5 from Zope Tests. Tests passed OK --- Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Tests Date: Mon Apr 7 21:03:12 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-April/009370.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Mon Apr 7 21:04:42 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-April/009371.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Mon Apr 7 21:06:12 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-April/009372.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Mon Apr 7 21:07:42 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-April/009373.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Mon Apr 7 21:09:12 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-April/009374.html ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: AW: [Zope-dev] Status of zam packages
Hi Roger. Thank you for this update. I will continue to work with these but will be aware that they are a bit volatile at the moment. Personally, I hope you don't remove the dependency upon the z3c.table and z3c.contents packages since these views add value. I think it would be better to include them but just allow folks to make that decision when they create a custom skin. Regards, David Roger Ineichen wrote: Hi David, Chris Betreff: Re: [Zope-dev] Status of zam packages zam (zope application manager) is reimplementation of sorts of the z3 zmi using a pagelet and form layers and with a plugin architecture and api. I have been working with it a bit but not sure how stable the api is so that I can build upon it which is what I am doing. Give me another two weeks and I hope to get ready for a initial release. Some tests break right now because I added a contets.html view which depends on z3c.table and z3c.contents. I think I will skip that dependency since probably not everybody will use zc.table or z3c.contents Darryl also did some improvments on a branch of z3c.contents which we need to merge back before we do a release. If this is done, ZAM should be stable enough for production. Regards Roger Ineichen Chris Withers wrote: David Pratt wrote: I am hoping I can get a bit of an update on zam packages on zope svn. Many thanks. What is zam? Chris ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: Jython, Zope and GSOC
On Mon, Apr 7, 2008 at 5:16 PM, Martijn Faassen [EMAIL PROTECTED] wrote: Frank Wierzbicki wrote: [snip] I'm looking for a Zope person who would be willing to put themselves down as a backup mentor for Georgy's proposal -- someone who is willing to be the point person for questions that I or Georgy might have on Zope details (or can direct us to the person to ask) -- Since I work on Jython full-time, the backup person would be pretty unlikely to become primary, but it would be important that this person be available for our questions. so -- anybody interested? So Sidnei da Silva has volunteered for this. Thanks for all of the offers of help that I received off-list! I will probably take you guys up on it :) -Frank ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Setting the size of a zope.formlib's schema html input
Could someone show me an example of defining a widget to set the size of
the rendered input?
Marcelo, here's what I did:
class PromosEditForm(EditForm):
An edit form to modify promo selection fields.
form_fields = form.FormFields(IContentPromoFields)
def setUpWidgets(self, ignore_request=False):
self.adapters = {
IContentPromoFields:ContentPromoFieldsAdapter(self.context)
}
self.widgets = form.setUpEditWidgets(
self.form_fields, self.prefix, self.context, self.request,
adapters=self.adapters, ignore_request=ignore_request
)
self.label = ...
self.description = \
...
self.widgets['global_promos'].size = 5
etc...
I too would like to see an example of a full custom widget. For example
I'd like to use an AT InOut-style dual list widget.
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] wiki front page updated
I have updated http://wiki.zope.org/zope3/Zope3Wiki , merging the aforementioned docs overview. http://wiki.zope.org/zope3/DocsCleanup talks more about this. I hope you agree, all feedback, improvements and help welcome. ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] What happened to the infrae.subversion and py eggs?
Hi,
Sorry, I don't know where best to ask this question, but it is about
buildout, so I guess it could be called on-topic on the zope dev list.
Since about one day I have problems with buildouts using the
infrae.subversion and py eggs. The problem can be seen with a
standard buildout. Well, a plone 3 buildout anyway:
paster create -t plone3_buildout
In the created buildout.cfg I added this section and included it in
the parts section:
===
[productcheckouts]
recipe = infrae.subversion
urls =
===
This does not do anything really, but it should be enough to
demonstrate the problem that surfaces when running bin/buildout -v:
===
...
Installing 'infrae.subversion'.
We have no distributions for infrae.subversion that satisfies
'infrae.subversion'.
Getting distribution for 'infrae.subversion'.
Got infrae.subversion 1.0dev-r28201.
Picked: infrae.subversion = 1.0dev-r28201
Getting required 'py==0.9.0'
required by infrae.subversion 1.0dev-r28201.
We have no distributions for py that satisfies 'py==0.9.0'.
Getting distribution for 'py==0.9.0'.
While:
Installing.
Getting section productcheckouts.
Initializing section productcheckouts.
Installing recipe infrae.subversion.
Getting distribution for 'py==0.9.0'.
Error: Couldn't find a distribution for 'py==0.9.0'.
===
At least, that happens when I do not yet have py-0.9.0-py2.4.egg in my
egg cache; no complaints when I already have that one. Has something
changed in the py egg? Other explanations for this error? Meanwhile
in a virtualenv I can do this without errors:
bin/easy_install py==0.9.0
Under the theory that the problem might be caused by the latest
version of the infrae.subversion recipe (released a few days ago I
think) having a wrong dependency or so, I pin this recipe to a
previous version that I know was on the cheeseshop last week as I got
it from there:
===
versions = versions
[versions]
infrae.subversion = 1.0dev-r27844
===
Then it can't find that version of the egg. Well, my buildout could
not find it this afternoon, but of course now the reverse
demonstration effect strikes back and it goes fine:
===
Installing 'infrae.subversion'.
We have no distributions for infrae.subversion that satisfies
'infrae.subversion==1.0dev-r27844'.
Getting distribution for 'infrae.subversion==1.0dev-r27844'.
Got infrae.subversion 1.0dev-r27844.
Getting required 'py'
required by infrae.subversion 1.0dev-r27844.
Picked: py = 0.9.1
===
But this page does not exist:
http://pypi.python.org/pypi/infrae.subversion/1.0dev-r27844
and it is not listed here:
http://pypi.python.org/simple/infrae.subversion
So where does buildout get that egg now? I emptied my egg cache.
Luckily for demonstration purposes this at least fails in a
virtualenv:
===
$ bin/easy_install infrae.subversion==1.0dev_r27844
Searching for infrae.subversion==1.0dev-r27844
Reading http://pypi.python.org/simple/infrae.subversion/
Reading https://svn.infrae.com/buildout/infrae.buildout/trunk/
No local packages or download links found for infrae.subversion==1.0dev-r27844
error: Could not find suitable distribution for
Requirement.parse('infrae.subversion==1.0dev-r27844')
===
So has that version of the egg been removed from the cheeseshop? And
can it be brought back? I have buildouts that are pinned to that
version for stability and I would like those to work half a year from
now (or in fact tomorrow) in case I have to rebuild those buildouts on
a new server. You never know when that meteor will hit your data
center. ;-)
Has anyone else seen this?
--
Maurits van Rees | http://maurits.vanrees.org/
Work | http://zestsoftware.nl/
This is your day, don't let them take it away. [Barlow Girl]
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: What happened to the infrae.subversion and py eggs?
Maurits van Rees wrote: [snip] Error: Couldn't find a distribution for 'py==0.9.0'. === At least, that happens when I do not yet have py-0.9.0-py2.4.egg in my egg cache; no complaints when I already have that one. Has something changed in the py egg? Other explanations for this error? Meanwhile in a virtualenv I can do this without errors: I know there was a py 0.9.1 release recently, but you'd think that wouldn't make the old py go away... Hm, there's still a py 0.9 download url available here: http://pypi.python.org/simple/py The one thing I notice is that py-0.9.1 is actually uploaded to the cheeseshop while the older versions were not (just download urls pointing back to the py website). Is it possible that this somehow confused things? If so, it might be worthwhile to contact the py list and ask them to upload py 0.9 as a tarball as well. Regards, Martijn ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: What happened to the infrae.subversion and py eggs?
Maurits van Rees [EMAIL PROTECTED] writes:
Luckily for demonstration purposes this at least fails in a
virtualenv:
===
$ bin/easy_install infrae.subversion==1.0dev_r27844
Searching for infrae.subversion==1.0dev-r27844
Reading http://pypi.python.org/simple/infrae.subversion/
Reading https://svn.infrae.com/buildout/infrae.buildout/trunk/
No local packages or download links found for infrae.subversion==1.0dev-r27844
error: Could not find suitable distribution for
Requirement.parse('infrae.subversion==1.0dev-r27844')
===
So has that version of the egg been removed from the cheeseshop? And
can it be brought back? I have buildouts that are pinned to that
version for stability and I would like those to work half a year from
now (or in fact tomorrow) in case I have to rebuild those buildouts on
a new server. You never know when that meteor will hit your data
center. ;-)
1.0dev-r27844 seems to be gone from PyPI. I'm CCing Sylvain who I
believe made the last release. Maybe we can even convince him to make a
proper release, not an SVN snapshot. :-)
Of course, we should also make sure that the latest version works
properly with its pinned py dependency.
Daniel
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Non-ASCII characters in URLs
On Mon, 07 Apr 2008 05:32:17 -0700, Jonathan [EMAIL PROTECTED] wrote: IDNA (http://www.ietf.org/rfc/rfc3490.txt) and Punycode (http://www.faqs.org/rfcs/rfc3492.html) may be of some use. I'm not looking for non-ASCII domain names, just object IDs. :) -- Alexander Limi · http://limi.net ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Non-ASCII characters in URLs
On Mon, 07 Apr 2008 12:45:00 -0700, Dieter Maurer [EMAIL PROTECTED] wrote: Wichert Akkerman wrote at 2008-4-7 20:45 +0200: This is becoming increasingly painful I will soon have a patch against Zope 2.11b1 which gets rid of this restriction. If there is consense, I can add it to the Zope repository. I would love to see support for non-ASCII object IDs, +1. (obviously not based on any technical understanding from my side :) -- Alexander Limi · http://limi.net ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: What happened to the infrae.subversion and py eggs?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Nouri wrote:
Maurits van Rees [EMAIL PROTECTED] writes:
Luckily for demonstration purposes this at least fails in a
virtualenv:
===
$ bin/easy_install infrae.subversion==1.0dev_r27844
Searching for infrae.subversion==1.0dev-r27844
Reading http://pypi.python.org/simple/infrae.subversion/
Reading https://svn.infrae.com/buildout/infrae.buildout/trunk/
No local packages or download links found for
infrae.subversion==1.0dev-r27844
error: Could not find suitable distribution for
Requirement.parse('infrae.subversion==1.0dev-r27844')
===
So has that version of the egg been removed from the cheeseshop? And
can it be brought back? I have buildouts that are pinned to that
version for stability and I would like those to work half a year from
now (or in fact tomorrow) in case I have to rebuild those buildouts on
a new server. You never know when that meteor will hit your data
center. ;-)
1.0dev-r27844 seems to be gone from PyPI.
Such a version should *never* have been released to PyPI (any egg /
source dist with an SVN revision number in its filename is *not*
suitable for sharing with the wider world). Pushing such distributions
out to PyPI, rather than sharing them in a more restricted / private
location, induces pain on the wrong parties (those who innocently rely
on PiPI, rather than those perpetrating the risky behavior).
I'm CCing Sylvain who I
believe made the last release. Maybe we can even convince him to make a
proper release, not an SVN snapshot. :-)
Of course, we should also make sure that the latest version works
properly with its pinned py dependency.
Amen!
Tres.
- --
===
Tres Seaver +1 540-429-0999 [EMAIL PROTECTED]
Palladion Software Excellence by Designhttp://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFH/B5C+gerLs4ltQ4RAtgwAJ464BsvjmvRqFuMLiuHdtpGIbGlAgCfZ/Pq
j56rwm9hVGP3gqp9kdY0LPY=
=+90j
-END PGP SIGNATURE-
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: What happened to the infrae.subversion and py eggs?
--On 8. April 2008 21:39:14 -0400 Tres Seaver [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 1.0dev-r27844 seems to be gone from PyPI. Such a version should *never* have been released to PyPI (any egg / source dist with an SVN revision number in its filename is *not* suitable for sharing with the wider world). Pushing such distributions out to PyPI, rather than sharing them in a more restricted / private location, induces pain on the wrong parties (those who innocently rely on PiPI, rather than those perpetrating the risky behavior). Amen. Lots of people are misusing PyPI right now for uploading their broken packages: lots of dev-packages in some weird state, packages without metadata, packages without URL, packages with descriptions..that's a pretty big pain in the *** right now. I currently working on the buildout infrastructure for three of our major Zope projects (which lots of externals dependencies) and I am sometimes really annoyed that stuffs works some day and not the other day because packages appearently come and go. I'm CCing Sylvain who I believe made the last release. Maybe we can even convince him to make a proper release, not an SVN snapshot. :-) Of course, we should also make sure that the latest version works properly with its pinned py dependency. Amen! Also Amen on this. Andreas pgpYknzKbfp9V.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] straighting out the SQLAlchemy integration mess
Hi, On Tue, Apr 08, 2008 at 11:54:33PM +0200, Martijn Faassen wrote: In the end, I hope we will end up with just *one* integration layer, that is released, that works with Zope 2 and Zope 3 and a recent release of SQLAlchemy, that is documented, and that people know about. We can then offer packages on top of this that offer extra features. I'm all for this and agree with you. The current situation is because everyone of us had slightly different use cases and the situation they found in the foreign packages wasn't satisfying. Consolidation is a really good idea. Christian PS: Martijn asked me to move a reply that went to zope3-users before he moved the thread to zope-dev, so here I'm repeating myself. ;) -- gocept gmbh co. kg - forsterstrasse 29 - 06112 halle (saale) - germany www.gocept.com - [EMAIL PROTECTED] - phone +49 345 122 9889 7 - fax +49 345 122 9889 1 - zope and plone consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
