[Zope-dev] zope-tests - FAILED: 16, OK: 69, UNKNOWN: 2
This is the summary for test reports received on the zope-tests list between 2011-07-06 00:00:00 UTC and 2011-07-07 00:00:00 UTC: See the footnotes for test reports of unsuccessful builds. An up-to date view of the builders is also available in our buildbot documentation: http://docs.zope.org/zopetoolkit/process/buildbots.html#the-nightly-builds Reports received Bluebream / Python2.4.6 64bit linux Bluebream / Python2.5.5 64bit linux Bluebream / Python2.6.5 64bit linux [1]UNKNOWN : Zope-trunk Python-2.6.6 : Linux [2]UNKNOWN : Zope-trunk-alltests Python-2.6.6 : Linux ZTK 1.0 / Python2.4.6 Linux 64bit ZTK 1.0 / Python2.5.5 Linux 64bit ZTK 1.0 / Python2.6.5 Linux 64bit [3]ZTK 1.0dev / Python2.4.6 Linux 64bit [4]ZTK 1.0dev / Python2.5.5 Linux 64bit [5]ZTK 1.0dev / Python2.6.5 Linux 64bit Zope 3.4 KGS / Python2.4.6 64bit linux Zope 3.4 KGS / Python2.5.5 64bit linux Zope 3.4 Known Good Set / py2.4-32bit-linux Zope 3.4 Known Good Set / py2.4-64bit-linux Zope 3.4 Known Good Set / py2.5-32bit-linux Zope 3.4 Known Good Set / py2.5-64bit-linux Zope Buildbot / zope2.12-py2.6 slave-osx Zope Buildbot / zope2.12-py2.6 slave-ubuntu32 Zope Buildbot / zope2.12-py2.6 slave-ubuntu64 Zope Buildbot / zope2.13-py2.6 slave-osx Zope Buildbot / zope2.13-py2.6 slave-ubuntu32 Zope Buildbot / zope2.13-py2.6 slave-ubuntu64 Zope Buildbot / zope2.13-py2.7 slave-osx Zope Buildbot / zope2.13-py2.7 slave-ubuntu32 Zope Buildbot / zope2.13-py2.7 slave-ubuntu64 [6]Zope Buildbot / zope2.13_win-py2.6 slave-win [7]Zope Buildbot / zope2.13_win-py2.7 slave-win [8]Zope Buildbot / zope2.14-py2.6 slave-osx [9]Zope Buildbot / zope2.14-py2.6 slave-ubuntu32 [10] Zope Buildbot / zope2.14-py2.6 slave-ubuntu64 [11] Zope Buildbot / zope2.14-py2.7 slave-osx [12] Zope Buildbot / zope2.14-py2.7 slave-ubuntu32 [13] Zope Buildbot / zope2.14-py2.7 slave-ubuntu64 Zope Buildbot / zopetoolkit-1.0-py2.4 slave-osx Zope Buildbot / zopetoolkit-1.0-py2.4 slave-ubuntu32 Zope Buildbot / zopetoolkit-1.0-py2.4 slave-ubuntu64 Zope Buildbot / zopetoolkit-1.0-py2.5 slave-osx Zope Buildbot / zopetoolkit-1.0-py2.5 slave-ubuntu32 Zope Buildbot / zopetoolkit-1.0-py2.5 slave-ubuntu64 Zope Buildbot / zopetoolkit-1.0-py2.6 slave-osx Zope Buildbot / zopetoolkit-1.0-py2.6 slave-ubuntu32 Zope Buildbot / zopetoolkit-1.0-py2.6 slave-ubuntu64 Zope Buildbot / zopetoolkit-1.0_win-py2.4 slave-win Zope Buildbot / zopetoolkit-1.0_win-py2.5 slave-win Zope Buildbot / zopetoolkit-1.0_win-py2.6 slave-win Zope Buildbot / zopetoolkit-1.1-py2.5 slave-osx Zope Buildbot / zopetoolkit-1.1-py2.5 slave-ubuntu32 Zope Buildbot / zopetoolkit-1.1-py2.5 slave-ubuntu64 Zope Buildbot / zopetoolkit-1.1-py2.6 slave-osx Zope Buildbot / zopetoolkit-1.1-py2.6 slave-ubuntu32 Zope Buildbot / zopetoolkit-1.1-py2.6 slave-ubuntu64 [14] Zope Buildbot / zopetoolkit-1.1_win-py2.5 slave-win [15] Zope Buildbot / zopetoolkit-1.1_win-py2.6 slave-win Zope Buildbot / zopetoolkit-py2.5 slave-osx Zope Buildbot / zopetoolkit-py2.5 slave-ubuntu32 Zope Buildbot / zopetoolkit-py2.5 slave-ubuntu64 Zope Buildbot / zopetoolkit-py2.6 slave-osx Zope Buildbot / zopetoolkit-py2.6 slave-ubuntu32 Zope Buildbot / zopetoolkit-py2.6 slave-ubuntu64 [16] Zope Buildbot / zopetoolkit_win-py2.5 slave-win [17] Zope Buildbot / zopetoolkit_win-py2.6 slave-win Zope-2.10 Python-2.4.6 : Linux Zope-2.11 Python-2.4.6 : Linux Zope-2.12 Python-2.6.6 : Linux Zope-2.12-alltests Python-2.6.6 : Linux Zope-2.13 Python-2.6.6 : Linux Zope-2.13-alltests Python-2.6.6 : Linux winbot / ZODB_dev py_254_win32 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [18] winbot / zope.app.interface_py_265_32 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 winbot / ztk_11 py_270_win64 winbot / ztk_dev py_254_win32 winbot / ztk_dev py_265_win32 winbot / ztk_dev py_265_win64 winbot / ztk_dev py_270_win32 winbot / ztk_dev py_270_win64 Non-OK results -- [1]UNKNOWN UNKNOWN : Zope-trunk Python-2.6.6 : Linux https://mail.zope.org/pipermail/zope-tests/2011-July/045259.html [2]UNKNOWN UNKNOWN : Zope-trunk-alltests Python-2.6.6 : Linux https://mail.zope.org/pipermail/zope-tests/2011-July/045260.html [3]FAILED ZTK 1.0dev / Python2.4.6 Linux 64bit https://mail.zope.org/piper
Re: [Zope-dev] direction
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/07/2011 03:24 AM, Shane Hathaway wrote: > On 07/06/2011 10:59 AM, Hanno Schlichting wrote: >> The ZMI is a highly insecure, completely outdated and >> user-unfriendly interface. > > As I read this, I got an idea for a possible way forward. I haven't > been reading zope-dev much lately, so forgive me if something like > this has been mentioned already. > > What if we had decorators that let us disable old code by default, > yet allowed users to enable the old code with configuration? > Something like this: > > > import zope.oldcode > > class SomeClass(SimpleObject): > > @zope.oldcode.zmi def manage_edit(self, REQUEST): # ... > > > The idea here is we'll create a zope.oldcode egg and fill it with > decorators for pervasive features of Zope that need to be removed > over time, such as the current ZMI. We'll also create a > configuration switch for each of those old features so that people > can keep using them for a reasonable period of time. When the "zmi" > feature is disabled, the code above will replace the manage_edit > method with a "zope.oldcode.Disabled" object that raises a helpful > exception if anyone tries to call it. > > It would also be good to make these decorators implement __nonzero__ > to allow conditional attribute definition: > > if zope.oldcode.zmi: manage_properties = (...) > > I would want to make sure conditional tests are possible as well: > > @zope.oldcode.zmi def test_manage_edit(self): # ... > > (The zope.oldcode package probably ought to enable all old features > by default when running tests.) > > What do you think? Neat -- sounds like an interesting thing to try a "spike" on, anyway. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software "Excellence by Design"http://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk4WLuwACgkQ+gerLs4ltQ46IgCgivBo8ucn91ix8YlsYknNG7HB +fcAn2wyEQoKNNpZ+yv5OXHi9vKmtiHh =Dm5a -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Publisher, WSGI and possibility for simplification
On Thu, 7 Jul 2011 16:15:38 +0100 Laurence Rowe wrote: Hello, > I was interested to see that Pyramid seems to be experimenting with a > non-wsgi approach now too for transaction integration > (http://groups.google.com/group/pylons-devel/browse_thread/thread/f05c56072e43f214/3006cbaf0258c568.) > I really don't have enough experience with WSGI to know which is the > best way to do it. > > I took a brief look at the documentation at > http://www.infrae.com/download/tools/infrae.wsgi where some of the > motivations behind it are mentioned. The builtin Zope2 WSGI publisher > is still very new, and seems to have some rough edges still when > running in mod_wsgi (possibly due to conflicts with Zope registered > signal handlers.) Is it only that you think that the Zope2 WSGI > publisher is not ready yet, or are there other problems? > The main reason I made this project (infrae.wsgi) is that I had a customer that wanted to have Zope running in a WSGI stack with some repoze.bfg application, one year ago. It was for Zope 2.12 (or even 2.11, I don't remember well). I tested the WSGIPublisher in that Zope version, and I got errors as soon as I tried something more complicated than a simple hello world. (Opening the ZMI didn't work). I didn't even test with mod_wsgi at that time. Repoze.zope2 was for much older versions of Zope 2 and didn't work either. So it was not definitely ready yet. I saw since that lot of efforts have been made, and the default WSGI publisher works probably better now in 2.13, or the trunk. What infrae.wsgi does, is providing: - a (simple) alternate boot code for Zope : not all the parameters of the zope.conf are applied ; mainly only DB configuration, products and ZCML loading are done. No signal handling, no logging configuration (just using Python logging facilities and Paster configuration for it works), nor any other parameters that would be related to the server part are done for example, - an equivalent of the WSGIPublisher code (written in completely different fashion that the default WSGIPublisher code, since I could not get my head around that code to fix the errors I encountered), - support to get zope.testbrowser working with this (that I don't use anymore actually). Testing code that do streaming with Products.File.testbrowser doesn't work (the magic is in ZServer, and the TestBrowser is hooked before), this fix this issue. After I changed it to have a better and more useful error reporting by default (which is nice when customer sends you only the error, and don't tell you what they did), and a different way to render errors (I find the code completely crazy in Zope 2 for that). Because of that last point, it is not really compatible Zope 2 100%. I use it on production for one year now, on big sites, and didn't had any problem. > I'd certainly support simplifying the publisher, it has grown very > complex as more and more functionality has been grafted on over the > years. In the long run I'd much rather see something that only used > __getitem__ for traversal and never getattr. > I would love to have something more easy to understand and use, with less magic, and not included in the REQUEST like that. Regards, Sylvain, -- Sylvain Viollon -- Infrae t +31 10 243 7051 -- http://infrae.com Hoevestraat 10 3033GC Rotterdam -- The Netherlands ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] zope 3 wiki update
I've made the zope 3 wiki's skin consistent with the other wikis, leaving the pond design for sole use of the foundation site. I also did a little front page cleanup and updated the intro - corrections welcome. Until some cache expires or can be flushed/restarted by Jens, you might see a messed up display caused by the old stylesheet (http://wiki.zope.org/Zope3Wiki/stylesheet). If so, just shift-reload. ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Publisher, WSGI and possibility for simplification
Breaking this out as the thread has got overlong. On 4 July 2011 09:49, Sylvain Viollon wrote: > On Sun, 03 Jul 2011 01:09:17 -0400 > Chris McDonough wrote: > >> On Sun, 2011-07-03 at 03:41 +0200, Hanno Schlichting wrote: >> > > Hello, > >> > - Continue to remove functionality tailored for TTW development, >> > like SiteRoot, AccessRules, HelpSys and step-by-step most of the ZMI >> > - Document and use the WSGI publisher and remove obsoleted >> > functionality like the virtual host monster, error_log, >> > ZServer/medusa, zopectl/zdaemon >> >> Zope still needs to the virtual host monster (or something like it) >> even with the WSGI publisher; there's nothing equivalent in the WSGI >> world (unless you could repoze.vhm, which is essentially just the >> virtual host monster, and probably doesn't need to live in >> middleware; no one uses it except people who use repoze.zope2). >> > > I have my own WSGI implementation, since a while, that works > perfectly (infrae.wsgi), and I still do use the VirtualHostMonster > (you can trash all the other things). > > I agree that its code might not been the best in the world, but it > works for the moment and does what it says (I would love to see > shiftNameToApplication implemented with more than one pass). > > I will sad to learn that this goes away, if nothing replace it. I > kind of don't like the WSGI approach of cutting the database, > traversing, authorization, rewriting Zope 2 concepts into middleware > as I think they don't really fit the design of pipes provided by the > WSGI middleware concept (but I do use middlewares for other things > with Zope 2). I was interested to see that Pyramid seems to be experimenting with a non-wsgi approach now too for transaction integration (http://groups.google.com/group/pylons-devel/browse_thread/thread/f05c56072e43f214/3006cbaf0258c568.) I really don't have enough experience with WSGI to know which is the best way to do it. I took a brief look at the documentation at http://www.infrae.com/download/tools/infrae.wsgi where some of the motivations behind it are mentioned. The builtin Zope2 WSGI publisher is still very new, and seems to have some rough edges still when running in mod_wsgi (possibly due to conflicts with Zope registered signal handlers.) Is it only that you think that the Zope2 WSGI publisher is not ready yet, or are there other problems? I'd certainly support simplifying the publisher, it has grown very complex as more and more functionality has been grafted on over the years. In the long run I'd much rather see something that only used __getitem__ for traversal and never getattr. Laurence ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] www.zope.org relaunched
Sylvain Viollon wrote: Great ! However if I click on any links on the site, my URL changes to http://beta.zope.org/. Just fixed. Andreas <>___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] direction
On Tue, 5 Jul 2011 12:11:40 +0100 Martin Aspeli wrote: > Hi, > Hello, > > I think it would be very sad if that happened, especially since there > evidently demand from other projects. > > What I think is clear is that to evolve Zope 2, we need to shed some > baggage and make some deeper changes to allow us to achieve some of > our goals (e.g. WSGI, simplified stack, simpler and more easily > controllable security, less magical traversal, more comprehensible > publisher). > > Plone is obviously a big consumer of Zope 2 and I would expect Plone > to have a major influence on Zope 2's evolution. But ERP5 is another > big consumer, and we shouldn't ignore that. > > And Silva. And maybe other companies that have a product and are not big enough to develop their product AND the framework they use. Regards, Sylvain -- Sylvain Viollon -- Infrae t +31 10 243 7051 -- http://infrae.com Hoevestraat 10 3033GC Rotterdam -- The Netherlands ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] www.zope.org relaunched
On 7 July 2011 12:58, Andreas Jung wrote: > Dear Zope Community, > > on behalf of the Zope Foundation I please to announce > the relaunch of the new www.zope.org web site. > > http://www.zope.org > > The "old" zope.org site will available for the time being > in (reduced form) under > > http://old.zope.org > > Many thanks to my team: > > - Kai Mertens > - Michael Haubenwaller > - Jens Vagelpohl > - Johannes Raggam > > Andreas Jung > Zope Foundation Fantastic work - thanks so much for succeeding where so many (myself included) have previously failed. :) Martin ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] www.zope.org relaunched
On Thu, Jul 7, 2011 at 3:39 PM, Sylvain Viollon wrote: > On Thu, 07 Jul 2011 13:58:27 +0200 > Andreas Jung wrote: >> on behalf of the Zope Foundation I please to announce >> the relaunch of the new www.zope.org web site. >> >> http://www.zope.org > > Great ! +10 :) Hanno ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] www.zope.org relaunched
On Thu, 07 Jul 2011 13:58:27 +0200 Andreas Jung wrote: > Dear Zope Community, > Hello, > on behalf of the Zope Foundation I please to announce > the relaunch of the new www.zope.org web site. > > http://www.zope.org > Great ! However if I click on any links on the site, my URL changes to http://beta.zope.org/. Is it because all web-products have now a beta tag on it :) ? > > Many thanks to my team: > > - Kai Mertens > - Michael Haubenwaller > - Jens Vagelpohl > - Johannes Raggam > Thanks for your work. Regards, Sylvain, -- Sylvain Viollon -- Infrae t +31 10 243 7051 -- http://infrae.com Hoevestraat 10 3033GC Rotterdam -- The Netherlands ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] www.zope.org relaunched
Both content and Skins are on Githubdo something...otherwise it will remain that way. Sorry not time for UI discussions right now. -aj Cykooz wrote: This is image not placed in skin. It is content of site and patch for skin will change nothing. 2011/7/7 Andreas Jung: Sorry, it will remain that way...we're happy accepting patches for the theme...it's on Github. -- ZOPYX Limited | zopyx group Charlottenstr. 37/1 | The full-service network for Zope & Plone D-72070 Tübingen| Produce & Publish www.zopyx.com | www.produce-and-publish.com E-Publishing, Python, Zope & Plone development, Consulting <>___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] www.zope.org relaunched
This is image not placed in skin. It is content of site and patch for skin will change nothing. 2011/7/7 Andreas Jung : > Sorry, it will remain that way...we're happy accepting patches for the > theme...it's on Github. > ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] www.zope.org relaunched
Sorry, it will remain that way...we're happy accepting patches for the theme...it's on Github. -aj Cykooz wrote: Ohhh, my eyes!!! Please, replace image in the teaser ( http://www.zope.org/teasers/the-world-of-zope/image_0_overfull ), on normal HTML code with text as text. Sorry, but otherwise it's a full shit. PS: Thanks to all who did this work. 2011/7/7 Andreas Jung: Dear Zope Community, on behalf of the Zope Foundation I please to announce the relaunch of the new www.zope.org web site. http://www.zope.org The "old" zope.org site will available for the time being in (reduced form) under http://old.zope.org Many thanks to my team: - Kai Mertens - Michael Haubenwaller - Jens Vagelpohl - Johannes Raggam Andreas Jung Zope Foundation ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope ) -- ZOPYX Limited | zopyx group Charlottenstr. 37/1 | The full-service network for Zope & Plone D-72070 Tübingen| Produce & Publish www.zopyx.com | www.produce-and-publish.com E-Publishing, Python, Zope & Plone development, Consulting <>___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] www.zope.org relaunched
Ohhh, my eyes!!! Please, replace image in the teaser ( http://www.zope.org/teasers/the-world-of-zope/image_0_overfull ), on normal HTML code with text as text. Sorry, but otherwise it's a full shit. PS: Thanks to all who did this work. 2011/7/7 Andreas Jung : > Dear Zope Community, > > on behalf of the Zope Foundation I please to announce > the relaunch of the new www.zope.org web site. > > http://www.zope.org > > The "old" zope.org site will available for the time being > in (reduced form) under > > http://old.zope.org > > Many thanks to my team: > > - Kai Mertens > - Michael Haubenwaller > - Jens Vagelpohl > - Johannes Raggam > > Andreas Jung > Zope Foundation > > ___ > Zope-Dev maillist - Zope-Dev@zope.org > https://mail.zope.org/mailman/listinfo/zope-dev > ** No cross posts or HTML encoding! ** > (Related lists - > https://mail.zope.org/mailman/listinfo/zope-announce > https://mail.zope.org/mailman/listinfo/zope ) > > ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] www.zope.org relaunched
Dear Zope Community, on behalf of the Zope Foundation I please to announce the relaunch of the new www.zope.org web site. http://www.zope.org The "old" zope.org site will available for the time being in (reduced form) under http://old.zope.org Many thanks to my team: - Kai Mertens - Michael Haubenwaller - Jens Vagelpohl - Johannes Raggam Andreas Jung Zope Foundation <>___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] direction
On Wed, 06 Jul 2011 15:07:35 +0200 Jens Vagelpohl wrote: Hello, > > I totally agree. Now would be a good moment to make it all a little > better by dropping the name "Zope 2" in favor of "Zope". And I > sincerely hope that "zope2.zope.org" will go away and its content end > up on the new www.zope.org site. > I would be very happy if this happens too. Regards, Sylvain, -- Sylvain Viollon -- Infrae t +31 10 243 7051 -- http://infrae.com Hoevestraat 10 3033GC Rotterdam -- The Netherlands ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] direction
On Tue, 5 Jul 2011 12:10:35 +0100 Laurence Rowe wrote: Hello, > > I agree with Jonas that any idea of giving a package named Zope2 a > version number that is not 2.x is only going to lead to more > confusion. For Zope2 we're used the x in 2.x.y being the major version > now anyway, the next release should be 2.14. Lets stick with our > convention until we have something that we really do want to promote > to users outside the existing development community, I expect that > will be a few years away yet. > I fully agree with that. A major version of Zope 2 is actually a minor at the version meaning, but everybody knows that for instance to switch from 2.10 to 2.11 you have to review and update your code like if it was a real major version change at the version meaning. That would be really confusing to do otherwise, since it was like that for years. I am also in favor of dropping the 2, but picking a new name would be nice, like to have 'framework x' 10 that map to Zope 2 2.10, 'framework x' to 2.11. Other products did that, Solaris, Mac OS X ... it is not strange to do so I think. Regards, Sylvain, -- Sylvain Viollon -- Infrae t +31 10 243 7051 -- http://infrae.com Hoevestraat 10 3033GC Rotterdam -- The Netherlands ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] direction
On 07/06/2011 10:59 AM, Hanno Schlichting wrote: > The ZMI is a highly insecure, completely outdated and user-unfriendly > interface. As I read this, I got an idea for a possible way forward. I haven't been reading zope-dev much lately, so forgive me if something like this has been mentioned already. What if we had decorators that let us disable old code by default, yet allowed users to enable the old code with configuration? Something like this: import zope.oldcode class SomeClass(SimpleObject): @zope.oldcode.zmi def manage_edit(self, REQUEST): # ... The idea here is we'll create a zope.oldcode egg and fill it with decorators for pervasive features of Zope that need to be removed over time, such as the current ZMI. We'll also create a configuration switch for each of those old features so that people can keep using them for a reasonable period of time. When the "zmi" feature is disabled, the code above will replace the manage_edit method with a "zope.oldcode.Disabled" object that raises a helpful exception if anyone tries to call it. It would also be good to make these decorators implement __nonzero__ to allow conditional attribute definition: if zope.oldcode.zmi: manage_properties = (...) I would want to make sure conditional tests are possible as well: @zope.oldcode.zmi def test_manage_edit(self): # ... (The zope.oldcode package probably ought to enable all old features by default when running tests.) What do you think? Shane ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
