[Zope-Annce] Issue Dealer 0.9.75 released
Issue Dealer (http://www.nidelven-it.no/products/issue_dealer) is a issue management tool featuring a weblog publisher (client), weblog (server), WebDAV client, WYSIWYG editing of HTML and Images and more. This announcement covers the last 3 releases, which were mostly minor tweaks and two major new features, the ability to add files, and the ability to customize weblog templates. Changes since the last announcement: 0.9.75: - Fixed bug where TypeError would be raised in local weblog publisher on direct issue publishing - Added ability to upload files 0.9.74: - Added option to delete catalog - Cleaned up text files - Added info on how to handle problems 0.9.73: - Cleaned up weblog code - Refactored weblog templates for easier customization, enabled easy access to all weblog templates through the browser If you're interested in trying a demo, sign up at the demo site (http://demos.issue-dealer.net). To see the Issue Dealer Weblog Server in action, have a look at The Blogologue (http://www.blogologue.com). :) Nidelven IT (http://www.nidelven-it.no) and others use the product to manage their knowledge and action items, it's a great tool to keep track issues in different departments for example. Try it! ;) 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-Announce maillist - Zope-Announce@zope.org http://mail.zope.org/mailman/listinfo/zope-announce Zope-Announce for Announcements only - no discussions (Related lists - Users: http://mail.zope.org/mailman/listinfo/zope Developers: http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope-Annce] ZODB 3.4 final released
I'm pleased to announce the release of ZODB 3.4 final. This corresponds to the ZODB that will ship in Zope 2.8. You can download a source tarball or Windows installer from: http://zope.org/Products/ZODB3.4 Note that there are two Windows installers, for Python 2.3 (2.3.5 is recommended) and Python 2.4 (2.4.1 is recommended). Only minor changes were made since ZODB 3.4b1. See the news file for details: http://zope.org/Products/ZODB3.4/NEWS.html Note that ZODB 3.4 does not support any version of Zope 2.6 or 2.7. Current Zope 2.8 and Zope 3 development use ZODB 3.4. The ZODB 3.3 line is officially retired (3.3.1 final was the last release in the 3.3 line). ___ Zope-Announce maillist - Zope-Announce@zope.org http://mail.zope.org/mailman/listinfo/zope-announce Zope-Announce for Announcements only - no discussions (Related lists - Users: http://mail.zope.org/mailman/listinfo/zope Developers: http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope-Checkins] SVN: Zope/branches/Zope-2_8-branch/ Collector #1798, issue 1: ZopeTestCase no longer tries to
Log message for revision 30728:
Collector #1798, issue 1: ZopeTestCase no longer tries to
install products that were installed by Zope during startup.
Interestingly, I never saw a checkin message for the merge of
Lennart's branch...
Changed:
U Zope/branches/Zope-2_8-branch/doc/CHANGES.txt
U Zope/branches/Zope-2_8-branch/lib/python/OFS/Application.py
U Zope/branches/Zope-2_8-branch/lib/python/Testing/ZopeTestCase/ZopeLite.py
U
Zope/branches/Zope-2_8-branch/lib/python/Testing/ZopeTestCase/doc/CHANGES.txt
U Zope/branches/Zope-2_8-branch/lib/python/Testing/ZopeTestCase/utils.py
U
Zope/branches/Zope-2_8-branch/lib/python/Testing/ZopeTestCase/zopedoctest/FunctionalDocTest.txt
-=-
Modified: Zope/branches/Zope-2_8-branch/doc/CHANGES.txt
===
--- Zope/branches/Zope-2_8-branch/doc/CHANGES.txt 2005-06-10 08:54:29 UTC
(rev 30727)
+++ Zope/branches/Zope-2_8-branch/doc/CHANGES.txt 2005-06-10 10:05:01 UTC
(rev 30728)
@@ -31,7 +31,7 @@
- Collector #1803: Fixed InitializeClass for some corner case.
- Collector #1798, issue 1: ZopeTestCase no longer tries to
-install products that was installed by Zope during startup.
+install products that were installed by Zope during startup.
- Collector #1799: Avoid lying about parent's refcount when
calling back into Python code.
Modified: Zope/branches/Zope-2_8-branch/lib/python/OFS/Application.py
===
--- Zope/branches/Zope-2_8-branch/lib/python/OFS/Application.py 2005-06-10
08:54:29 UTC (rev 30727)
+++ Zope/branches/Zope-2_8-branch/lib/python/OFS/Application.py 2005-06-10
10:05:01 UTC (rev 30728)
@@ -38,9 +38,6 @@
import ZDOM
from FindSupport import FindSupport
-# Dictionary of installed products, mainly used by ZopeTestCase.
-_installedProducts = {}
-
class Application(Globals.ApplicationDefaultPermissions,
ZDOM.Root, Folder.Folder,
App.ProductRegistry.ProductRegistry, FindSupport):
@@ -624,13 +621,7 @@
# together and do a default initialization.
if done.has_key(product_name):
continue
-# We need to separately track what has been installed now, and
-# what has been installed at a whole. This is because install_products
-# should always install everything, but only once every time it's
-# called. The _installedProducts dictionary is later used by
-# ZopeTestCase to not install products twice.
done[product_name]=1
-_installedProducts[product_name]=1
install_product(app, product_dir, product_name, meta_types,
folder_permissions, raise_exc=debug_mode)
Modified:
Zope/branches/Zope-2_8-branch/lib/python/Testing/ZopeTestCase/ZopeLite.py
===
--- Zope/branches/Zope-2_8-branch/lib/python/Testing/ZopeTestCase/ZopeLite.py
2005-06-10 08:54:29 UTC (rev 30727)
+++ Zope/branches/Zope-2_8-branch/lib/python/Testing/ZopeTestCase/ZopeLite.py
2005-06-10 10:05:01 UTC (rev 30728)
@@ -99,6 +99,8 @@
import App.ProductContext
_write('.')
+_patched = False
+
def _apply_patches():
# Avoid expensive product import
def null_import_products(): pass
@@ -116,18 +118,22 @@
def null_register_help(self,directory='',clear=1,title_re=None): pass
App.ProductContext.ProductContext.registerHelp = null_register_help
+# Note that we applied the monkey patches
+global _patched
+_patched = True
+
# Do not patch a running Zope
if not Zope2._began_startup:
_apply_patches()
# Allow test authors to install Zope products into the test environment. Note
# that installProduct() must be called at module level -- never from tests.
-from OFS.Application import get_folder_permissions, get_products, \
- install_product, _installedProducts
+from OFS.Application import get_folder_permissions, get_products,
install_product
from OFS.Folder import Folder
import Products
_theApp = Zope2.app()
+_installedProducts = {}
def hasProduct(name):
'''Checks if a product can be found along Products.__path__'''
@@ -137,7 +143,7 @@
'''Installs a Zope product.'''
start = time.time()
meta_types = []
-if not _installedProducts.has_key(name):
+if _patched and not _installedProducts.has_key(name):
for priority, product_name, index, product_dir in get_products():
if product_name == name:
if not quiet: _print('Installing %s ... ' % product_name)
Modified:
Zope/branches/Zope-2_8-branch/lib/python/Testing/ZopeTestCase/doc/CHANGES.txt
===
---
Zope/branches/Zope-2_8-branch/lib/python/Testing/ZopeTestCase/doc/CHANGES.txt
2005-06-10 08:54:29 UTC (rev 30727)
+++
[Zope-Checkins] SVN: Zope/trunk/lib/python/ Collector #1798, issue 1: ZopeTestCase no longer tries to
Log message for revision 30729:
Collector #1798, issue 1: ZopeTestCase no longer tries to
install products that were installed by Zope during startup.
Changed:
U Zope/trunk/lib/python/OFS/Application.py
U Zope/trunk/lib/python/Testing/ZopeTestCase/ZopeLite.py
U Zope/trunk/lib/python/Testing/ZopeTestCase/doc/CHANGES.txt
U Zope/trunk/lib/python/Testing/ZopeTestCase/utils.py
U
Zope/trunk/lib/python/Testing/ZopeTestCase/zopedoctest/FunctionalDocTest.txt
-=-
Modified: Zope/trunk/lib/python/OFS/Application.py
===
--- Zope/trunk/lib/python/OFS/Application.py2005-06-10 10:05:01 UTC (rev
30728)
+++ Zope/trunk/lib/python/OFS/Application.py2005-06-10 10:36:30 UTC (rev
30729)
@@ -38,9 +38,6 @@
import ZDOM
from FindSupport import FindSupport
-# Dictionary of installed products, mainly used by ZopeTestCase.
-_installedProducts = {}
-
class Application(Globals.ApplicationDefaultPermissions,
ZDOM.Root, Folder.Folder,
App.ProductRegistry.ProductRegistry, FindSupport):
@@ -624,13 +621,7 @@
# together and do a default initialization.
if done.has_key(product_name):
continue
-# We need to separately track what has been installed now, and
-# what has been installed at a whole. This is because install_products
-# should always install everything, but only once every time it's
-# called. The _installedProducts dictionary is later used by
-# ZopeTestCase to not install products twice.
done[product_name]=1
-_installedProducts[product_name]=1
install_product(app, product_dir, product_name, meta_types,
folder_permissions, raise_exc=debug_mode)
Modified: Zope/trunk/lib/python/Testing/ZopeTestCase/ZopeLite.py
===
--- Zope/trunk/lib/python/Testing/ZopeTestCase/ZopeLite.py 2005-06-10
10:05:01 UTC (rev 30728)
+++ Zope/trunk/lib/python/Testing/ZopeTestCase/ZopeLite.py 2005-06-10
10:36:30 UTC (rev 30729)
@@ -99,6 +99,8 @@
import App.ProductContext
_write('.')
+_patched = False
+
def _apply_patches():
# Avoid expensive product import
def null_import_products(): pass
@@ -116,18 +118,22 @@
def null_register_help(self,directory='',clear=1,title_re=None): pass
App.ProductContext.ProductContext.registerHelp = null_register_help
+# Note that we applied the monkey patches
+global _patched
+_patched = True
+
# Do not patch a running Zope
if not Zope2._began_startup:
_apply_patches()
# Allow test authors to install Zope products into the test environment. Note
# that installProduct() must be called at module level -- never from tests.
-from OFS.Application import get_folder_permissions, get_products, \
- install_product, _installedProducts
+from OFS.Application import get_folder_permissions, get_products,
install_product
from OFS.Folder import Folder
import Products
_theApp = Zope2.app()
+_installedProducts = {}
def hasProduct(name):
'''Checks if a product can be found along Products.__path__'''
@@ -137,7 +143,7 @@
'''Installs a Zope product.'''
start = time.time()
meta_types = []
-if not _installedProducts.has_key(name):
+if _patched and not _installedProducts.has_key(name):
for priority, product_name, index, product_dir in get_products():
if product_name == name:
if not quiet: _print('Installing %s ... ' % product_name)
Modified: Zope/trunk/lib/python/Testing/ZopeTestCase/doc/CHANGES.txt
===
--- Zope/trunk/lib/python/Testing/ZopeTestCase/doc/CHANGES.txt 2005-06-10
10:05:01 UTC (rev 30728)
+++ Zope/trunk/lib/python/Testing/ZopeTestCase/doc/CHANGES.txt 2005-06-10
10:36:30 UTC (rev 30729)
@@ -1,6 +1,8 @@
Unreleased
- Functional.publish() would hang if it got a request_method argument other
than GET or HEAD while omitting the stdin argument.
+- installProduct() now becomes a noop if ZopeTestCase did not apply its
+ patches.
0.9.8 (Zope 2.8 edition)
- Renamed 'doctest' package to 'zopedoctest' because of name-shadowing
Modified: Zope/trunk/lib/python/Testing/ZopeTestCase/utils.py
===
--- Zope/trunk/lib/python/Testing/ZopeTestCase/utils.py 2005-06-10 10:05:01 UTC
(rev 30728)
+++ Zope/trunk/lib/python/Testing/ZopeTestCase/utils.py 2005-06-10 10:36:30 UTC
(rev 30729)
@@ -97,7 +97,8 @@
def importObjectFromFile(container, filename, quiet=0):
'''Imports an object from a (.zexp) file into the given container.'''
-from ZopeLite import _print
+from ZopeLite import _print, _patched
+quiet = quiet or not _patched
start = time.time()
if not quiet: _print(Importing %s ... % os.path.basename(filename))
Re: [Zope-Coders] Zope 2.8 coming this weekend
On Thu, Jun 09, 2005 at 05:24:08PM +0200, Andreas Jung wrote: Heads up for the 2.8.0 final release. My plans are to make the final release on Saturday morning. So any further changes should be done by tomorrow at the latest. Cheers, -aj Mind if I check in text-only changes to the 2_8 branch? I'm playing with a checkout of the Zope-2_8-branch right now, and while I was looking at doc/*txt to see what if anything is said about migrating to 2.8, I noticed some really trivial typos which I'd gladly check in (and merge to the trunk too). 5710 unit tests... holy cow. -- Paul Winkler http://www.slinkp.com ___ Zope-Coders mailing list Zope-Coders@zope.org http://mail.zope.org/mailman/listinfo/zope-coders
Re: [Zope-Coders] Zope 2.8 coming this weekend
On 6/10/05, Paul Winkler [EMAIL PROTECTED] wrote: Mind if I check in text-only changes to the 2_8 branch? It's still Friday for Andreas, so this is a good time! -Fred -- Fred L. Drake, Jr.fdrake at gmail.com Zope Corporation ___ Zope-Coders mailing list Zope-Coders@zope.org http://mail.zope.org/mailman/listinfo/zope-coders
[Zope-dev] Re: Logging after ConflictError Retries
On Thu, 09 Jun 2005 20:50:22 +0200, Dieter Maurer wrote: The fix is (almost surely) to replace in .../Zope/App/startup.py: if t is ZPublisher.Retry: v.reraise() by if t is ZPublisher.Retry: t, v, traceback = v._args Yes, that's better than my fix. 2. If there is at least one ConflictError and then the request finishes with an error (either more ConflictErrors or something else), the Z2 log shows the request as having been answered with status 200, although actually a status 500 error response has been served. I've managed to work out what's causing this, but fixing may be more fiddly. What happens is, once the request is abandoned because of the error, when control comes back to publish_module_standard in Publish.py, response.exception() is called on the original response, not on the latest retry. Then, when HTTPResponse _finish() is called, it traces down to the latest retry to find the status code for the logging, which is now the wrong one. This should only happen when publish itself raises an exception. Usually, publish should *NOT* raise an exception, when the request fails (although exceeding the maximal number of retries may cause this). My debugger indicates that publish in fact does raise an exception, whether or not retries are in play. zpublisher_exception_hook calls raise_standardErrorMessage, which raises, and this exception propagates all the way to the catch in publish_module_standard. Nevertheless, the mixed use of response and request.response in publish_module_standard looks wrong. Almost surely, request.response should get the value of response when publish succeeds and both are different. Thus I expect, we should have: response = publish(...) request.response = response except ... I don't know if this is right or not, but due to the way exceptions are propagating here it won't have any impact on this specific problem; the extra code won't be executed in this case. Please file two bug reports for the problems you discovered... I've filed one bug report; I'll scope it down to the first bug and add your better fix, and file another for the second bug. Thanks, Malcolm. -- [] j a m k i t web solutions for charities malcolm cleaton T: 020 7549 0520 F: 020 7490 1152 M: 07986 563852 W: www.jamkit.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 )
[Zope-dev] Re: [Zope-Coders] Zope 2.8 coming this weekend
On Thu, Jun 09, 2005 at 05:24:08PM +0200, Andreas Jung wrote: Heads up for the 2.8.0 final release. My plans are to make the final release on Saturday morning. So any further changes should be done by tomorrow at the latest. Cheers, -aj Mind if I check in text-only changes to the 2_8 branch? I'm playing with a checkout of the Zope-2_8-branch right now, and while I was looking at doc/*txt to see what if anything is said about migrating to 2.8, I noticed some really trivial typos which I'd gladly check in (and merge to the trunk too). 5710 unit tests... holy cow. -- 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 )
[Zope-dev] Re: [Zope-Coders] Zope 2.8 coming this weekend
On 6/10/05, Paul Winkler [EMAIL PROTECTED] wrote: Mind if I check in text-only changes to the 2_8 branch? It's still Friday for Andreas, so this is a good time! -Fred -- Fred L. Drake, Jr.fdrake at gmail.com Zope Corporation ___ 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] ZEO-based migration script [was Drop Mount.py from ZODB 3.5]
For a migration situation like yours I would highly suggest you use a simple script that acts as a ZEO client to two ZEO servers Inspired by this post, I wrote just such a migration script and have posted it on Zope Labs: http://www.zopelabs.com/cookbook/1118424287 Thanks for the tip Jens. chad ___ 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: [Zope-Coders] Zope 2.8 coming this weekend
On Fri, Jun 10, 2005 at 07:27:15PM +0200, Andreas Jung wrote: --On 10. Juni 2005 12:39:50 -0400 Fred Drake [EMAIL PROTECTED] wrote: On 6/10/05, Paul Winkler [EMAIL PROTECTED] wrote: Mind if I check in text-only changes to the 2_8 branch? It's still Friday for Andreas, so this is a good time! yeah...countdown is running :-) -aj Done. Like I said, just trivial docs typos. -- 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 )
[Zope-dev] Re: [Zope-Coders] Zope 2.8 coming this weekend
On Fri, Jun 10, 2005 at 02:21:32PM -0400, Paul Winkler wrote: Done. Like I said, just trivial docs typos. While I'm at it, anybody object to the attached patch to doc/FAQ.txt ? -- Paul Winkler http://www.slinkp.com Index: FAQ.txt === --- FAQ.txt (revision 30745) +++ FAQ.txt (working copy) @@ -194,7 +194,35 @@ (yay) it's var/z2.pid, for pcgi (not so yay), it's var/pcgi.pid. -4. After moving my old Data.fs to Zope 2.8 I get an + Upgrading from Earlier Versions of Zope + +1. How can I upgrade to Zope 2.8? + + The usual procedure when installing a new version of Zope is: + + - Create a new instance (see doc/INSTALL.txt). + + - Copy the var/Data.fs file from your old instance into your + new instance's var/ directory. (It is best to do this while + the old instance is not running; alternatively, you can + use repozo.py as described at + http://www.zope.org/Wikis/ZODB/FileStorageBackup + to make a live backup, then create a new Data.fs from that + backup in your new instance.) + + Keep your old Data.fs in the old instance as a backup. + + - Copy the Products and Extensions directories from your old + instance into the new instance. + + - Update etc/zope.conf with any changes you made in your + old instance. (Likewise for zeo.conf if you are using zeo.) + + - Start the new instance. (Be sure the old instance is not running.) + + - Update any ZCatalogs as described below. + +2. After moving my old Data.fs to Zope 2.8 I get an AttributeError, _length when trying to use the ZCatalog? In Zope 2.8 we cleaned up the index implementations and therefore @@ -224,6 +252,25 @@ converted and reindexed +3. CMF doesn't work! + +Check that you have a recent stable version of CMF. +You need at least CMF-1.4.8. CMF is available at +http://www.zope.org/Products/CMF/ + + +4. Plone doesn't work! + +As of the release of Zope 2.8.0, Plone does not support +Zope 2.8 yet. Check http://www.plone.org for updates. + + +5. I'm using Python 2.4 and I'm having a problem... + + Zope 2.8 has not been tested with Python 2.4. + Please use Python 2.3. + + General ___ 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: [Zope-Coders] Zope 2.8 coming this weekend
On Fri, Jun 10, 2005 at 03:07:51PM -0400, Paul Winkler wrote: On Fri, Jun 10, 2005 at 02:21:32PM -0400, Paul Winkler wrote: Done. Like I said, just trivial docs typos. While I'm at it, anybody object to the attached patch to doc/FAQ.txt ? (snip) Holy crap, FAQ.txt is rally crufty. It's loaded with pcgi information and other useless crap. Gimme a minute to come up with a better patch. I should make a branch for this. -- 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 )
[Zope-dev] Re: [Zope-Coders] Zope 2.8 coming this weekend
[Paul Winkler] Holy crap, FAQ.txt is rally crufty. It's loaded with pcgi information and other useless crap. Gimme a minute to come up with a better patch. I should make a branch for this. I vote you check in changes instead, until you run out of time. Every improvement will lessen confusion for countless multitudes until the end of time. Perfection is overrated 0.9 wink. Thanks for doing it, BTW! Some things get so out of date that paralysis is the natural reaction -- but a chain of small improvements can turn that around. ___ 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: [Zope-Coders] Zope 2.8 coming this weekend
On Fri, Jun 10, 2005 at 02:21:32PM -0400, Paul Winkler wrote: Done. Like I said, just trivial docs typos. Yeah, but improvements are improvements! On 6/10/05, Paul Winkler [EMAIL PROTECTED] wrote: While I'm at it, anybody object to the attached patch to doc/FAQ.txt ? I don't see a need to include the disclaimer about Python 2.4; I test on 2.4, and use Zope 3 trunk with 2.4.1 all the time. -Fred -- Fred L. Drake, Jr.fdrake at gmail.com Zope Corporation ___ 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: [Zope-Coders] Zope 2.8 coming this weekend
On Fri, Jun 10, 2005 at 03:40:41PM -0400, Tim Peters wrote: [Paul Winkler] Holy crap, FAQ.txt is rally crufty. It's loaded with pcgi information and other useless crap. Gimme a minute to come up with a better patch. I should make a branch for this. I vote you check in changes instead, until you run out of time. OK, done on 2_8-branch and merged to trunk. Every improvement will lessen confusion for countless multitudes until the end of time. Perfection is overrated 0.9 wink. Yeah, e.g. even if we never get our butts in gear to release it, Chris's 2.7 version of the Zope Book is still vastly better than the 2.6 version (which was vastly better than 2.5, etc.) Thanks for doing it, BTW! Some things get so out of date that paralysis is the natural reaction -- but a chain of small improvements can turn that around. Agreed. If I had nothing else to do I would poke around in that directory some more. I think WEBSERVERS.txt could use some attention, and probably others too. Sadly there's other things in doc/ that could use the attention, and I have to get back to Real Work now. -- 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 )
[Zope-dev] Re: [Zope-Coders] Zope 2.8 coming this weekend
On Fri, Jun 10, 2005 at 04:04:48PM -0400, Fred Drake wrote: On Fri, Jun 10, 2005 at 02:21:32PM -0400, Paul Winkler wrote: Done. Like I said, just trivial docs typos. Yeah, but improvements are improvements! On 6/10/05, Paul Winkler [EMAIL PROTECTED] wrote: While I'm at it, anybody object to the attached patch to doc/FAQ.txt ? I don't see a need to include the disclaimer about Python 2.4; I test on 2.4, and use Zope 3 trunk with 2.4.1 all the time. Maybe you do, but it really is a FAQ, and that's the consensus response from the chorus every time it comes up on the main zope list, so I feel justified :-) -- 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: ZClass problem in 2.8 (Was: Re: [Zope-dev] Upcoming Zope 2.8 release)
Am 09.06.2005, 19:28 Uhr schrieb Dieter Maurer [EMAIL PROTECTED]: A long time ago, Shane posted a very useful function to analyse acquisition wrappers: showaq. Maybe, the mailing list archive is still able to locate his post... Just ask Google: http://www.zope.org/Members/chrisw/showaq Jo. -- internetmanufaktur jo- Berlin, Germany |||meder---fon: ++49-30-417 17 63 33 http://www.meder.de/ --- fax: ++49-30-417 17 63 45 Kollwitzstr. 75 mob: ++49-170- 2 98 89 97 10435 Berlin ---http://www.meder.de/keys/jo-pubkey.txt ___ 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: [Zope-Coders] Zope 2.8 coming this weekend
[Fred Drake] I don't see a need to include the disclaimer about Python 2.4; I test on 2.4, and use Zope 3 trunk with 2.4.1 all the time. [Paul Winkler] Maybe you do, but it really is a FAQ, and that's the consensus response from the chorus every time it comes up on the main zope list, so I feel justified :-) It's the right answer, too. No security audit has been done against Python 2.4 for Zope use yet, and Zope Corp won't officially bless 2.4 for use with Zope until that's been done. Note that the story is different for ZODB: Python 2.4+ is officially blessed for standalone ZODB use. This is one advantage of keeping DTML out of the storage layer wink. ___ 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: Logging after ConflictError Retries
Malcolm Cleaton wrote at 2005-6-10 11:00 +0100: ... 2. If there is at least one ConflictError and then the request finishes with an error (either more ConflictErrors or something else), the Z2 log shows the request as having been answered with status 200, although actually a status 500 error response has been served. I've managed to work out what's causing this, but fixing may be more fiddly. What happens is, once the request is abandoned because of the error, when control comes back to publish_module_standard in Publish.py, response.exception() is called on the original response, not on the latest retry. Then, when HTTPResponse _finish() is called, it traces down to the latest retry to find the status code for the logging, which is now the wrong one. This should only happen when publish itself raises an exception. Usually, publish should *NOT* raise an exception, when the request fails (although exceeding the maximal number of retries may cause this). My debugger indicates that publish in fact does raise an exception, whether or not retries are in play. zpublisher_exception_hook calls raise_standardErrorMessage, which raises, and this exception propagates all the way to the catch in publish_module_standard. You and your debugger are right! I do not understand why raise_standardErrorMessage needs to raise an exception rather than just set up the response -- but it indeed raise an exception... Apparently, Retry must be carefully rethought. Please file a critical bug report... -- Dieter ___ 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] backing up a running zodb fileStorage
hi, i am trying to backup a zodb filestorage of a running zope. i'm on linux. i've read that you simply make a copy of the Data.fs file.. but what about the modifications/transactions that are happening when i make the copy. will not the database be in a corrupt state then? gabor ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Re: backing up a running zodb fileStorage
On Fri, 10 Jun 2005 09:30:35 +0200, gabor wrote: hi, i am trying to backup a zodb filestorage of a running zope. i'm on linux. i've read that you simply make a copy of the Data.fs file.. but what about the modifications/transactions that are happening when i make the copy. will not the database be in a corrupt state then? I backup my Data.fs with repozo.py. you can find some info about it in the plone book: http://docs.neuroinf.de/PloneBook/ch14.rst Bye -- Haim ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] backing up a running zodb fileStorage
[gabor] i am trying to backup a zodb filestorage of a running zope. i'm on linux. i've read that you simply make a copy of the Data.fs file.. but what about the modifications/transactions that are happening when i make the copy. will not the database be in a corrupt state then? It can be, although the odds are in your favor. The intended way to make backups is explained here: http://zope.org/Wikis/ZODB/FileStorageBackup ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] aggreagating and merging logs under Zope 2.7.X
Is there any way to configure multi-headed Zopes running on different machines but sharing the same ZEO to log to the same file (in time order would also be nice...)? -- Dennis Allison * Computer Systems Laboratory * Gates 227 * Stanford University * Stanford CA 94305 * (650) 723-9213 * (650) 723-0033 fax * [EMAIL PROTECTED] * [EMAIL PROTECTED] ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] undo many things
Rakotomandimby (R12y) Mihamina wrote at 2005-6-9 22:40 +0200: If I want to undo a very early action, I have to also undo all the actions done after the one I want to undo. The problem is that the action to undo is 4 pages earlier, so that I want to one time check all the actions of the 4 last pages. How to manage it? Everything, you can do via the ZMI, you can do in a script (or an interactive Python interpreter). This is more appropriate for all kinds of mass operations. To find out what you can put into your script, you have 2 options: * you look at the Python source The undo methods are for example implememented in App.Undo.UndoSupport. * you look at the HTML source of the ZMI pages and see there how the ZMI performs the task. -- Dieter ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: Voodoo with ModuleSecurityInfo, was Re: [Zope] importing encode_base64
Paul Winkler wrote at 2005-6-9 15:42 -0400:
...
ModuleSecurityInfo('Products.FooProduct').declarePublic(
'blah', 'foo')
This allows something like:
from Products.FooProduct import foo
But, in fact, you use
from Products.FooProduct import Utils
... Utils.foo ...
Strange, that it worked at all...
Yeah, I think I just happened to hit on some undocumented
behavior that *mostly* works.
Maybe, you should file a bug report:
Undocumented security related features might be viewed
as security holes...
Especially, if something unexpectedly becomes possible...
However, I think, this one in not overly critical.
--
Dieter
___
Zope maillist - Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Product architecture question (long)
Nikko Wolf wrote at 2005-6-9 11:34 -0600: ... I would model a file as a folder like structure containing the various versions and give it the right behaviour. Currently, I've implemented scripts to do part of this -- although I would not say I've modeled anything as much as simply implemented scripts ZPT to allow access in the manner needed. Modelling describes the intellectual work before the implementation. It indentifies the major use cases, looks for the primary concepts and designs the outline of the necessary classes and their interactions. It is an essential preparation for the actual implementation -- for any non-trivial task... The issue is that there is no separation of workflow and content view/actions, and there should be, since the workflow may change and I'd like to use the workflow interface to handle those changes (if possible). It is the task of the modelling phase to answer such questions. ... However my question is this -- is it necessary for me to shutdown zope to snapshot the directory? No, it is not necessary. You should read: http://zope.org/Wikis/ZODB/FileStorageBackup Knowing that zope is event-driven (and no sleeper thread): -- is there any consistency issues of backing up (Data.fs) without stopping? -- is there another feature of zopectl that would tell it to sync the DB to the file system? help gives: EOF fg kill quitrun start test adduser foreground logreopen reload shell status wait debug help logtail restart show stop No, because it is not necessary. ... I've looked but found no Zope SSL capabilities, so does this requires placing Zope behind Apache, right? It is the easiest and most standard solution. But there is also an SSL enabled ZServer (as a third party product). I do not know its name -- search for it if you mistrust Apache... -- Dieter ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Re: aggreagating and merging logs under Zope 2.7.X
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dennis Allison wrote: Is there any way to configure multi-headed Zopes running on different machines but sharing the same ZEO to log to the same file (in time order would also be nice...)? zope.conf supports logging to syslog, which would be the sanest way to do that, assuming that you can run the syslog daemon; otherwise, you have to work out the multiple concurrent writers in the same file across NFS problem, which would probably involve more research than I imagine you are contemplating. Tres. - -- === Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCqgJL+gerLs4ltQ4RArqRAJ9TkXM0EG2lcI3uKOIVFGps7ULUGgCeMVfA N4hy/9kViG9e5BDzBbj6hbg= =5dA5 -END PGP SIGNATURE- ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Re: aggreagating and merging logs under Zope 2.7.X
Well, I am not really ready to address the multiple concurrent writers problem across NFS and all the issues it entails. I'd somehow dismissed the SysLog solution, but I can certainly configure to use it. Thanks for the pointer. On Fri, 10 Jun 2005, Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dennis Allison wrote: Is there any way to configure multi-headed Zopes running on different machines but sharing the same ZEO to log to the same file (in time order would also be nice...)? zope.conf supports logging to syslog, which would be the sanest way to do that, assuming that you can run the syslog daemon; otherwise, you have to work out the multiple concurrent writers in the same file across NFS problem, which would probably involve more research than I imagine you are contemplating. Tres. - -- === Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCqgJL+gerLs4ltQ4RArqRAJ9TkXM0EG2lcI3uKOIVFGps7ULUGgCeMVfA N4hy/9kViG9e5BDzBbj6hbg= =5dA5 -END PGP SIGNATURE- ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev ) -- Dennis Allison * Computer Systems Laboratory * Gates 227 * Stanford University * Stanford CA 94305 * (650) 723-9213 * (650) 723-0033 fax * [EMAIL PROTECTED] * [EMAIL PROTECTED] ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
