[Zope-dev] buildbot failure in Zope trunk 2.4 Linux zc-buildbot
The Buildbot has detected a failed build of Zope trunk 2.4 Linux zc-buildbot. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 2134 Blamelist: andreasjung,gregweb,jens,oestermeier BUILD FAILED: failed test sincerely, -The Buildbot ___ 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: 7 OK, 1 Failed
Summary of messages to the zope-tests list. Period Sat Dec 10 12:01:01 2005 UTC to Sun Dec 11 12:01:01 2005 UTC. There were 8 messages: 8 from Zope Unit Tests. Test failures - Subject: FAILED : Zope-trunk Python-2.4.2 : Linux From: Zope Unit Tests Date: Sat Dec 10 22:07:55 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003769.html Tests passed OK --- Subject: OK : Zope-2_6-branch Python-2.1.3 : Linux From: Zope Unit Tests Date: Sat Dec 10 21:57:24 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003762.html Subject: OK : Zope-2_6-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Sat Dec 10 21:58:54 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003763.html Subject: OK : Zope-2_7-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Sat Dec 10 22:00:25 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003764.html Subject: OK : Zope-2_7-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Sat Dec 10 22:01:55 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003765.html Subject: OK : Zope-2_8-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Sat Dec 10 22:03:25 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003766.html Subject: OK : Zope-2_8-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Sat Dec 10 22:04:55 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003767.html Subject: OK : Zope-2_9-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Sat Dec 10 22:06:25 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003768.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 )
[Zope-dev] Zope.org Developer Home cleanup
(Sorry for X-post) Hi, I proposed to clean up the developer zone a bit. I'll do that without a lot of fuss as I have to goals: - get information up to date - reduce the amount of false / out-of-date information - structure it in small steps so important stuff is found easier I'll make an archive area that holds stuff that is out-of-date and will not delete stuff except it's obvious to me that it isn't needed anymore. I'll not make this a large-effort-project but want to move that what is there to a more usable form. I'll try to gather a couple of points that can then be tackled subsequently. Regards, Christian -- gocept gmbh co. kg - schalaunische str. 6 - 06366 koethen - germany www.gocept.com - [EMAIL PROTECTED] - phone +49 3496 30 99 112 - fax +49 3496 30 99 118 - zope and plone consulting and development signature.asc Description: This is a digitally signed message part ___ 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] [ZPT] Zope 3 ZPTs in Zope 2
Hi, I have a working implementation for Zope 3 ZPTs within Zope 2. It is currently implemented through a new class ZPT which implements the same functionality as Products.PageTemplates.ZopePageTemplate. I am currently thinking about the migration to the new implementation. Would it be possible to perform an in-place migration using setstate() when replacing the ZopePageTemplate implementation with the prototype code from my ZPT class? Andreas pgpUXH5QdyKEU.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] [ZPT] Zope 3 ZPTs in Zope 2
Am Sonntag, den 11.12.2005, 13:16 +0100 schrieb Andreas Jung: Hi, I have a working implementation for Zope 3 ZPTs within Zope 2. It is currently implemented through a new class ZPT which implements the same functionality as Products.PageTemplates.ZopePageTemplate. I am currently thinking about the migration to the new implementation. Would it be possible to perform an in-place migration using setstate() when replacing the ZopePageTemplate implementation with the prototype code from my ZPT class? Are there different object-attributes in both classes? If not, you could simple replace with the same old class name. If there are (you would have to know them anyway to do the __setstate__ approach) I'd like an approach with an upgrade script (similar to 'stale Python Scripts') better. Buts just me ;-) Regards Tino ___ 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] [ZPT] Zope 3 ZPTs in Zope 2
--On 11. Dezember 2005 13:42:58 +0100 Tino Wildenhain [EMAIL PROTECTED] wrote: Are there different object-attributes in both classes? If not, you could simple replace with the same old class name. The Z3 ZPT implementation seems to use the same attrs. So I could just replace the class implementation. Some first quick tests show that there is no further need for a migration..it just works :-) -aj pgpHUtnauZTqQ.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] [ZPT] Zope 3 ZPTs in Zope 2
Am Sonntag, den 11.12.2005, 15:03 +0100 schrieb Andreas Jung: ... The Z3 ZPT implementation seems to use the same attrs. So I could just replace the class implementation. Some first quick tests show that there is no further need for a migration..it just works :-) Lets praise the wonderful world of pickle ;)) ++Tino ___ 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] New ways of getting transactions?
Morten W. Petersen wrote: Hi, I'm having some code that bombs out trying to commit a transaction; I believe it's because of new ways of doing things in Zope 2.9.. how do you call the equivalents of get_transaction().commit() and abort() in Zope 2.9? Will those new ways work with Zope 2.7/2.8? import transaction ... transaction.commit() transaction.abort() Although I think the old way should still work. If it doesn't, please report a bug. Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ 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] New ways of getting transactions?
import transaction transaction.get() transaction.commit() transaction.abort() transaction.savepoint() This works since 2.8, but not in 2.7. Nearly every project has come up with its own backward compatibility module though. See for example CMFCore.utils.transaction or CMFPlone.transaction. Stefan On 11. Dez 2005, at 17:01, Morten W. Petersen wrote: Hi, I'm having some code that bombs out trying to commit a transaction; I believe it's because of new ways of doing things in Zope 2.9.. how do you call the equivalents of get_transaction().commit() and abort() in Zope 2.9? Will those new ways work with Zope 2.7/2.8? Thanks. -- Morten W. Petersen -- Anything that happens, happens. --Douglas Adams ___ 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] New ways of getting transactions?
Stefan H. Holek wrote: import transaction transaction.get() transaction.commit() transaction.abort() transaction.savepoint() This works since 2.8, but not in 2.7. Nearly every project has come up with its own backward compatibility module though. See for example CMFCore.utils.transaction or CMFPlone.transaction. I'm dispayed to hear this. :( The old use of __builtins__.get_transaction should be deprecated and supported for a period of time. If it isn't, then this is *definately* a bug. Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ 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] New ways of getting transactions?
This works since 2.8, but not in 2.7. Nearly every project has come up with its own backward compatibility module though. See for example CMFCore.utils.transaction or CMFPlone.transaction. I'm dispayed to hear this. :( The old use of __builtins__.get_transaction should be deprecated and supported for a period of time. If it isn't, then this is *definately* a bug. I agree. I've reported it as a bug: http://www.zope.org/Collectors/Zope/1965 -- Morten W. Petersen Email: [EMAIL PROTECTED] Phone: +47 45 44 00 69 Title: Project manager Nidelven IT (http://www.nidelven-it.no) We provide Zope/Plone hosting and consulting begin:vcard fn:Morten Petersen n:Petersen;Morten org:Nidelven IT adr:;;Postboks 923;Trondheim;;7409;Norway email;internet:[EMAIL PROTECTED] title:Project Manager tel;work:+47 45 44 00 69 tel;cell:+47 45 44 00 69 x-mozilla-html:FALSE url:http://www.nidelven-it.no version:2.1 end:vcard ___ 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] New ways of getting transactions?
--On 11. Dezember 2005 17:01:56 +0100 Morten W. Petersen [EMAIL PROTECTED] wrote: Hi, I'm having some code that bombs out trying to commit a transaction; I believe it's because of new ways of doing things in Zope 2.9.. how do you call the equivalents of get_transaction().commit() and abort() in Zope 2.9? Will those new ways work with Zope 2.7/2.8? See doc/ZODB.txt. Of course the new API will not work in Zope 2.7/2.8. -aj pgpbsHnd6aIix.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 )
[Zope-dev] Re: New ways of getting transactions?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andreas Jung wrote: --On 11. Dezember 2005 17:01:56 +0100 Morten W. Petersen [EMAIL PROTECTED] wrote: Hi, I'm having some code that bombs out trying to commit a transaction; I believe it's because of new ways of doing things in Zope 2.9.. how do you call the equivalents of get_transaction().commit() and abort() in Zope 2.9? Will those new ways work with Zope 2.7/2.8? See doc/ZODB.txt. Of course the new API will not work in Zope 2.7/2.8. The 'transaction' module is present in Zope 2.8.x / ZODB 3.4.x. Forward compatibility for third-party produccts which need to work on both 2.7.x and 2.8.x+ usually looks like this: try: import transaction except ImportError: class transaction: Forward-compatibility for Zope 2.7.x def begin(self): get_transaction().begin() def commit(self, sub=False): get_transaction().commit(sub) def abort(self, sub=False): get_transaction().abort(sub) def savepoint(self, optimistic=None): get_transaction().commit(optimistic and 1 or 0) def get(self): return get_transaction() transaction = transaction() I'll agree with Jim and Morten that the deprecated 'get_transaction()' pattern should *not* have been ripped out in Zope 2.9b1 (2.10 is the earliest feasible point, I think). Tres. - -- === Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDnG5W+gerLs4ltQ4RAlDCAJ9n1owUWja8VUoYfOA3qXQEwKK/AwCffWDG YbnO+f8tnKilCYQHVnPeYNk= =7HJy -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] New ways of getting transactions?
--On 11. Dezember 2005 12:28:04 -0500 Jim Fulton [EMAIL PROTECTED] wrote: Stefan H. Holek wrote: import transaction transaction.get() transaction.commit() transaction.abort() transaction.savepoint() This works since 2.8, but not in 2.7. Nearly every project has come up with its own backward compatibility module though. See for example CMFCore.utils.transaction or CMFPlone.transaction. I'm dispayed to hear this. :( The old use of __builtins__.get_transaction should be deprecated and supported for a period of time. If it isn't, then this The deprecation warning in Zope 2.8 says: -c:1: DeprecationWarning: This will be removed in ZODB 3.6: use transaction.get() instead of get_transaction(). transaction.commit() is a shortcut spelling of transaction.get().commit(), and transaction.abort() of transaction.get().abort(). Zope 2.9 comes with ZODB 3.6. So the behaviour is correct in some way but I agree that the deprecation should continue longer. It would be save to remove it in Zope 2.10. -aj pgpUKqZDyxiF7.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] New ways of getting transactions?
A number of ZODB gimmicks were officially deprecated in ZODB 3.4, and removed in ZODB 3.6. Zope 2.9 uses the latter. From the ZODB NEWS file for 3.6: Removal of Features Deprecated in ZODB 3.4 -- (3.6b2) ZODB 3.6 no longer contains features officially deprecated in the ZODB 3.4 release. These include: - ``get_transaction()``. Use ``transaction.get()`` instead. ``transaction.commit()`` is a shortcut spelling of ``transaction.get().commit()``, and ``transaction.abort()`` of ``transaction.get().abort()``. Note that importing ZODB no longer installs ``get_transaction`` as a name in Python's ``__builtin__`` module either. - The ``begin()`` method of ``Transaction`` objects. Use the ``begin()`` method of a transaction manager instead. ``transaction.begin()`` is a shortcut spelling to call the default transaction manager's ``begin()`` method. - The ``dt`` argument to ``Connection.cacheMinimize()``. - The ``Connection.cacheFullSweep()`` method. Use ``cacheMinimize()`` instead. - The ``Connection.getTransaction()`` method. Pass a transaction manager to ``DB.open()`` instead. - The ``Connection.getLocalTransaction()`` method. Pass a transaction manager to ``DB.open()`` instead. - The ``cache_deactivate_after`` and ``version_cache_deactivate_after`` arguments to the ``DB`` constructor. - The ``temporary``, ``force``, and ``waitflag`` arguments to ``DB.open()``. ``DB.open()`` no longer blocks (there's no longer a fixed limit on the number of open connections). - The ``transaction`` and ``txn_mgr``arguments to ``DB.open()``. Use the ``transaction_manager`` argument instead. - The ``getCacheDeactivateAfter``, ``setCacheDeactivateAfter``, ``getVersionCacheDeactivateAfter`` and ``setVersionCacheDeactivateAfter`` methods of ``DB``. ___ 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] buildbot failure in Zope branches 2.9 2.4 Linux zc-buildbot
The Buildbot has detected a failed build of Zope branches 2.9 2.4 Linux zc-buildbot. Buildbot URL: http://buildbot.zope.org/ Build Reason: The web-page 'force build' button was pressed by '': Build Source Stamp: None Blamelist: BUILD FAILED: failed test sincerely, -The Buildbot ___ 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] New ways of getting transactions?
Andreas Jung wrote: --On 11. Dezember 2005 12:28:04 -0500 Jim Fulton [EMAIL PROTECTED] wrote: Stefan H. Holek wrote: import transaction transaction.get() transaction.commit() transaction.abort() transaction.savepoint() This works since 2.8, but not in 2.7. Nearly every project has come up with its own backward compatibility module though. See for example CMFCore.utils.transaction or CMFPlone.transaction. I'm dispayed to hear this. :( The old use of __builtins__.get_transaction should be deprecated and supported for a period of time. If it isn't, then this The deprecation warning in Zope 2.8 says: -c:1: DeprecationWarning: This will be removed in ZODB 3.6: use transaction.get() instead of get_transaction(). transaction.commit() is a shortcut spelling of transaction.get().commit(), and transaction.abort() of transaction.get().abort(). Zope 2.9 comes with ZODB 3.6. So the behaviour is correct in some way but I agree that the deprecation should continue longer. It would be save to remove it in Zope 2.10. Yup. BTW, This is a good example for why I want to start using time-based deprecation. Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ 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] New ways of getting transactions?
[Jim Fulton] ... BTW, This is a good example for why I want to start using time-based deprecation. In a world with time-based releases, is there a difference? ___ 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] New ways of getting transactions?
Tim Peters wrote: [Jim Fulton] ... BTW, This is a good example for why I want to start using time-based deprecation. In a world with time-based releases, is there a difference? Yes, because release numbers aren't very helpful when software is used by many applications. For example, I could imagine bumping ZODB (or some other packages) release numbers more often than is needed by Zope. For example, zope.interface has separate releases. We might someday decide to make a release to meet Twisted's needs. We wouldn't want such an incedental event to cause a feature to be deprecated more quickly. Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ 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] make test fails on 2.9.0-b1?
Sorry for redundancy if this is a known problem, but I just now grabbed the 2.9.0-b1 tarball and noticed this: [EMAIL PROTECTED] Zope-2.9.0b1 $ ./configure --prefix=/home/pw/Zope-2.9.0b1-SoftwareHome Configuring Zope installation Testing for an acceptable Python interpreter... Python version 2.4.2 found at /usr/bin/python The optimum Python version (2.4.2) was found at /usr/bin/python. [EMAIL PROTECTED] Zope-2.9.0b1 $ less Makefile [EMAIL PROTECTED] Zope-2.9.0b1 $ make make test make install /usr/bin/python install.py -q build /usr/bin/python install.py -q build /usr/bin/python test.py -v Traceback (most recent call last): File test.py, line 32, in ? import zope.app.testing.test ImportError: No module named test make: *** [test] Error 1 Is make test expected to work currently? -- Paul Winkler http://www.slinkp.com ___ 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] Imports broken on 2.9.0-b1?
Am Sonntag, den 11.12.2005, 23:19 -0500 schrieb Paul Winkler: Another quickie problem report - no time to investigate further right now, but can anybody else reproduce? If so, I'll try to fix tomorrow... In a fresh 2.9.0-b1 instance, made via bin/mkzopeinstance, I get this when I click the Import/Export button in the ZMI: Site Error An error was encountered while publishing this resource. Error Type: OSError Error Value: [Errno 2] No such file or directory: '/home/pw/Zope-2.9.0b1-SoftwareHome/import' And the traceback is: ... OSError: [Errno 2] No such file or directory: '/home/pw/Zope-2.9.0b1-SoftwareHome/import' Well, err, why are you looking there? That's not my instance home :-\ I suspect its the feature which got introduced in 2.8? or so which has a browser for packets to import so you dont have to guess and type the name correctly. And to not have to copy the exaples to every instance home, it looks in Software-home too. 2 questions araise, though: 1) why is Softwarehome/import not there? 2) why is the test not skipping the non existant directory. Either case a bug report :) ++Tino ___ 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 )
