[Zope-dev] Re: [CMF-checkins] SVN: CMF/trunk/ CMFSetup is dead. Long live GenericSetup!
I'm probably missing something, hence my asking.
If GenericSetup is generic, why is it in the CMF repository?
Sure, bundle it with CMF, like BTreeFolder2 used to be, but why not also
release it seperately and have it in its own repo?
cheers,
Chris
Yvo Schubbe wrote:
Log message for revision 40429:
CMFSetup is dead. Long live GenericSetup!
- removed obsolete CMFSetup product
- added bbb code and __module_aliases__ to support setup tools created with
CMFSetup
Changed:
U CMF/trunk/CHANGES.txt
D CMF/trunk/CMFSetup/
U CMF/trunk/GenericSetup/__init__.py
A CMF/trunk/GenericSetup/bbb/
A CMF/trunk/GenericSetup/bbb/__init__.py
A CMF/trunk/GenericSetup/bbb/registry.py
A CMF/trunk/GenericSetup/bbb/tool.py
-=-
Modified: CMF/trunk/CHANGES.txt
===
--- CMF/trunk/CHANGES.txt 2005-11-30 12:47:07 UTC (rev 40428)
+++ CMF/trunk/CHANGES.txt 2005-11-30 22:12:58 UTC (rev 40429)
@@ -43,7 +43,7 @@
- ActionsTool: Improved add form for 'CMF Action' objects.
Presettings can now be loaded from Action settings in setup profiles.
-- CMFSetup and GenericSetup: Added catalog tool setup handlers.
+- CMFCore and GenericSetup: Added catalog tool setup handlers.
This includes node adapters for PluginIndexes, ZCTextIndex and ZCatalog.
Support for additional indexes can be added by providing INodeExporter
and INodeImporter adapters. All indexes are cleared by this handler, so
@@ -87,7 +87,7 @@
- Replaced user messages by MassageIDs to improve the i18n support.
-- CMFDefault CMFSetup profile: Added CMF BTree Folder to the list of
+- CMFDefault GenericSetup profile: Added CMF BTree Folder to the list of
automatically instantiated types in the types tool.
(http://www.zope.org/Collectors/CMF/371)
@@ -117,9 +117,6 @@
Bug Fixes
-- CMFSetup: fixed empty attribute parsing when an encoding is
- defined.
-
- ActionProviderBase: getActionObject did stumble over newstyle Actions.
- CMFCore.exportimport.content: Ensure that BODYFILE in our faux
@@ -163,6 +160,9 @@
Others
+- CMFSetup and GenericSetup: Removed obsolete CMFSetup product.
+ Added __module_aliases__ to support setup tools created with CMFSetup.
+
- DCWorkflow: Removed hardcoded default workflows.
- Workflow: Removed deprecated WorkflowInformation and getActionsFor.
Modified: CMF/trunk/GenericSetup/__init__.py
===
--- CMF/trunk/GenericSetup/__init__.py 2005-11-30 12:47:07 UTC (rev 40428)
+++ CMF/trunk/GenericSetup/__init__.py 2005-11-30 22:12:58 UTC (rev 40429)
@@ -24,3 +24,15 @@
interfaces=None,
icon='www/tool.png',
)
+
+# BBB: for setup tools created with CMF 1.5 if CMFSetup isn't installed
+try:
+import Products.CMFSetup
+except ImportError:
+import bbb
+import bbb.registry
+import bbb.tool
+
+__module_aliases__ = (('Products.CMFSetup', bbb),
+ ('Products.CMFSetup.registry', bbb.registry),
+ ('Products.CMFSetup.tool', bbb.tool))
Copied: CMF/trunk/GenericSetup/bbb/__init__.py (from rev 40417,
CMF/trunk/CMFSetup/__init__.py)
===
--- CMF/trunk/CMFSetup/__init__.py 2005-11-29 20:40:33 UTC (rev 40417)
+++ CMF/trunk/GenericSetup/bbb/__init__.py 2005-11-30 22:12:58 UTC (rev
40429)
@@ -0,0 +1,16 @@
+##
+#
+# Copyright (c) 2004 Zope Corporation and Contributors. All Rights Reserved.
+#
+# This software is subject to the provisions of the Zope Public License,
+# Version 2.1 (ZPL). A copy of the ZPL should accompany this distribution.
+# THIS SOFTWARE IS PROVIDED AS IS AND ANY AND ALL EXPRESS OR IMPLIED
+# WARRANTIES ARE DISCLAIMED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+# WARRANTIES OF TITLE, MERCHANTABILITY, AGAINST INFRINGEMENT, AND FITNESS
+# FOR A PARTICULAR PURPOSE.
+#
+##
+ CMFSetup product initialization.
+
+$Id$
+
Copied: CMF/trunk/GenericSetup/bbb/registry.py (from rev 40417,
CMF/trunk/CMFSetup/registry.py)
Copied: CMF/trunk/GenericSetup/bbb/tool.py (from rev 40417,
CMF/trunk/CMFSetup/tool.py)
___
CMF-checkins mailing list
CMF-checkins@zope.org
http://mail.zope.org/mailman/listinfo/cmf-checkins
--
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
Re: [Zope-dev] DateTime iso8601 bad handling of dates
Evan Simpson wrote: It was asserted, last time this came up, that this is compliant with the ISO8601 spec, but my own research shows this to be false. If someone can point me to a truly authoritative source that supports the current behavior, I would appreciate it, but that would not change the fact that the manifested behavior is *broken*. This is a simple two-line fix, folks. I've already done it on my production systems. Philipp is your man for this, since he's biting the bullet on the DateTime front... 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] Folderish or SimpleItem object types for structural content
Martijn Jacobs wrote: catalog. The estimation about the amount of objects, with only the leave nodes as 'SimpleItem' objects will be 30.000. 30,000 is nothing. The production catalog on one of my projects has 220,000 objects in it, and I still wouldn't class that as huge. cheers, 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: DateTime mess
Andreas Jung wrote: For people it might be more comfortable to have a on-the-fly migration somehow under the hood...however this leads to ugly migration code in the sources (Zope is full of such scary code). Personally I prefer a dedicated migration step. + lotz 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] zope.conf extensibility
Fred Drake wrote: I don't know that there's any real documentation for this. Feel free to add some. In this case, I think zopeschema.xml should be documentation enough, especially as any product author wanting to use this feature is going to have to write a component.xml at least ;-) cheers, 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 )
[Zope-dev] Zope tests: 8 OK
Summary of messages to the zope-tests list. Period Wed Nov 30 12:01:02 2005 UTC to Thu Dec 1 12:01:02 2005 UTC. There were 8 messages: 8 from Zope Unit Tests. Tests passed OK --- Subject: OK : Zope-2_6-branch Python-2.1.3 : Linux From: Zope Unit Tests Date: Wed Nov 30 22:15:17 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-November/003682.html Subject: OK : Zope-2_6-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Wed Nov 30 22:16:47 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-November/003683.html Subject: OK : Zope-2_7-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Wed Nov 30 22:18:17 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-November/003684.html Subject: OK : Zope-2_7-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Wed Nov 30 22:19:47 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-November/003685.html Subject: OK : Zope-2_8-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Wed Nov 30 22:21:17 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-November/003686.html Subject: OK : Zope-2_8-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Wed Nov 30 22:22:47 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-November/003687.html Subject: OK : Zope-2_9-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Wed Nov 30 22:24:17 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-November/003688.html Subject: OK : Zope-trunk Python-2.4.2 : Linux From: Zope Unit Tests Date: Wed Nov 30 22:25:47 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-November/003689.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: [Zope-dev] zope.conf extensibility
On 12/1/05, Chris Withers [EMAIL PROTECTED] wrote: In this case, I think zopeschema.xml should be documentation enough, especially as any product author wanting to use this feature is going to have to write a component.xml at least ;-) Actually, a product author isn't required to write a component.xml, though they probably should for anything interesting. -Fred -- Fred L. Drake, Jr.fdrake at gmail.com There is no wealth but life. --John Ruskin ___ 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: [Zope3-dev] RFC: Reunite Zope 2 and Zope 3 in the source code repository
On Nov 30, 2005, at 2:18 PM, Chris Withers wrote: Gary Poster wrote: Zope 2 depends on Zope 3, via Five. Zope 3 does not depend on Zope 2. A very good point, but one which makes me feel that Zope 2 shouldn't be merged in with Zope 3 ;-) Actually, yes, all of my points were made to that end--so AFAICT you are agreeing with me, not disagreeing. :-) Gary ___ 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] Short tutorial on I18n with Five
I'm happy to announce that I've finally managed to document the internationalization (i18n) features that Five has brought to the Zope 2 world since version 1.1: http://worldcookery.com/files/fivei18n This short tutorial compares current Zope-2-based solutions to the i18n problem with the Zope 3 i18n framework. It also gives a few pointers on how to use the latter in Zope 2 applications through the means of Five. It is not a full-blown tutorial and it expects the reader to be quite familiar with i18n-aware software development in Zope already. Target audience is mostly people switching over their Zope 2 products to Zope 3 technology which i18n is a part of. The tutorial also serves as a documentation of a new Zope 2 core feature because Five 1.3 is included in Zope 2.9 which is thus the first Zope 2 version to come with built-in i18n support! ___ 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] Logging of ConflictError
I've improved the logging of ConflictError in Zope 2.9 and trunk. http://svn.zope.org/?rev=40454view=rev Now you'll get two things: - logs at level BLATHER for each conflict, but it may be retried - log at level ERROR when the conflict can't be retried anymore and is returned to the browser as an error. I removed the log at level INFO because it is very misleading for system administrators in my experience. Do people want this also for 2.8? Note that it changes the log format, so may break third party tools that parse logs. Florent -- Florent Guillaume, Nuxeo (Paris, France) CTO, Director of RD +33 1 40 33 71 59 http://nuxeo.com [EMAIL PROTECTED] ___ 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: Logging of ConflictError
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Florent Guillaume wrote: I've improved the logging of ConflictError in Zope 2.9 and trunk. http://svn.zope.org/?rev=40454view=rev Now you'll get two things: - logs at level BLATHER for each conflict, but it may be retried - log at level ERROR when the conflict can't be retried anymore and is returned to the browser as an error. I removed the log at level INFO because it is very misleading for system administrators in my experience. Do people want this also for 2.8? Note that it changes the log format, so may break third party tools that parse logs. +1. 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 iD8DBQFDj0kX+gerLs4ltQ4RAjRvAJsHXdNzYc9AAXxoWQQYk5FPNzC9RwCdHgRa 7vgGgKQCJEmSXIrl3Jwzq1k= =ota4 -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: Logging of ConflictError
On Thu, Dec 01, 2005 at 02:03:51PM -0500, Tres Seaver wrote: Do people want this also for 2.8? Note that it changes the log format, so may break third party tools that parse logs. +1. +1 from me too, the added information is worth potential tool breakage IMO. Just put an obvious note in CHANGES.txt as usual. -- 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] Logging of ConflictError
+1 On Dec 1, 2005, at 1:49 PM, Florent Guillaume wrote: I've improved the logging of ConflictError in Zope 2.9 and trunk. http://svn.zope.org/?rev=40454view=rev Now you'll get two things: - logs at level BLATHER for each conflict, but it may be retried - log at level ERROR when the conflict can't be retried anymore and is returned to the browser as an error. I removed the log at level INFO because it is very misleading for system administrators in my experience. Do people want this also for 2.8? Note that it changes the log format, so may break third party tools that parse logs. Florent -- Florent Guillaume, Nuxeo (Paris, France) CTO, Director of RD +33 1 40 33 71 59 http://nuxeo.com [EMAIL PROTECTED] ___ 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] KeyError: 'URL' in HTTPRequest using zope2.7-py2.3.3
hello all,
i'm running into a wierd zope/plone error. it is the same error as the
RESPONSE eaten post at:
http://mail.zope.org/pipermail/zope-dev/2003-November/020952.html
i asked the poster for help since there were no followups, but unfortunately he
would not help me and told me he was not my personal helpdesk. these posters
had a similar issue/solution:
http://mail.zope.org/pipermail/zope-dev/2004-February/021793.html
but i cannot find a similar culprit. any help would be much appreciated.
below is my traceback.
thanks a million,
brian w.
Traceback (most recent call last):
File E:\NBCJEAP\Zope\lib\python\zExceptions\ExceptionFormatter.py, line 157,
in formatLine
result.extend(self.formatSupplement(supp, tb))
File E:\NBCJEAP\Zope\lib\python\zExceptions\ExceptionFormatter.py, line 105,
in formatSupplement
extra = self.formatExtraInfo(supplement)
File E:\NBCJEAP\Zope\lib\python\zExceptions\ExceptionFormatter.py, line 231,
in formatExtraInfo
extra = getInfo(1)
File E:\NBCJEAP\Zope\lib\python\Products\PageTemplates\TALES.py, line 277, i
n getInfo
s = pprint.pformat(data)
File E:\NBCJEAP\Python\lib\pprint.py, line 58, in pformat
return PrettyPrinter().pformat(object)
File E:\NBCJEAP\Python\lib\pprint.py, line 109, in pformat
self._format(object, sio, 0, 0, {}, 0)
File E:\NBCJEAP\Python\lib\pprint.py, line 127, in _format
rep = self._repr(object, context, level - 1)
File E:\NBCJEAP\Python\lib\pprint.py, line 191, in _repr
self._depth, level)
File E:\NBCJEAP\Python\lib\pprint.py, line 203, in format
return _safe_repr(object, context, maxlevels, level)
File E:\NBCJEAP\Python\lib\pprint.py, line 246, in _safe_repr
vrepr, vreadable, vrecur = saferepr(v, context, maxlevels, level)
File E:\NBCJEAP\Python\lib\pprint.py, line 286, in _safe_repr
rep = `object`
File E:\NBCJEAP\Zope\lib\python\ZPublisher\HTTPRequest.py, line 1295, in __r
epr__
return %s, URL=%s % (self.__class__.__name__, self['URL'])
File E:\NBCJEAP\Zope\lib\python\ZPublisher\HTTPRequest.py, line 1214, in __g
etitem__
raise KeyError, key
KeyError: 'URL'
--
___
Play 100s of games for FREE! http://games.mail.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] Re: Python2.4 Security Audit ETA???
Hi, Am Mittwoch, den 30.11.2005, 15:52 +0100 schrieb Philipp von Weitershausen: Andreas Jung wrote: Let's say it this way: it's safer than with Zope 2.8.3 but it is still not supported :-) From where I'm standing, with Zope 2.8.4 it's as safe as with Zope 2.9 (which actually *requires* Python 2.4...) So it is really just a label we put on the 2.8 and 2.9 branches, in terms of the relevant code base they're the same... Statements like that are *dangerous*. The label is all that it is about. It is against the possibility that although the likely relevant code base is the same, there might be some minor minor minor switch that makes everything burn. There are _several_ major linux distributions out there that already ignore this label and shipped Zope with Python 2.4. It's not helpful to argue them out of that if we don't care for the label ourselves. 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 )
