[Zope-Checkins] SVN: Zope/branches/Zope-2_8-branch/skel/ Make instances have a lib/python directory with a proper README.txt by default.
Log message for revision 41323: Make instances have a lib/python directory with a proper README.txt by default. Note that it's already automatically put on the PYTHONPATH by Zope, it just wasn't there yet by default. Changed: U Zope/branches/Zope-2_8-branch/skel/README.txt A Zope/branches/Zope-2_8-branch/skel/lib/ -=- Modified: Zope/branches/Zope-2_8-branch/skel/README.txt === --- Zope/branches/Zope-2_8-branch/skel/README.txt 2006-01-16 11:30:06 UTC (rev 41322) +++ Zope/branches/Zope-2_8-branch/skel/README.txt 2006-01-16 13:33:20 UTC (rev 41323) @@ -5,5 +5,6 @@ etc/ Configuration files Extensions/ Python sources for External Methods log/ Log files - Products/Installed products specific to the instance + lib/python/ Installed Python packages specific to the instance + Products/Installed Zope Products specific to the instance var/ Run-time data files, including the object database Copied: Zope/branches/Zope-2_8-branch/skel/lib (from rev 41322, Zope3/trunk/zopeskel/lib) ___ Zope-Checkins maillist - Zope-Checkins@zope.org http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/branches/2.9/skel/ Merge r41323 from 2.8 branch:
Log message for revision 41324: Merge r41323 from 2.8 branch: Make instances have a lib/python directory with a proper README.txt by default. Note that it's already automatically put on the PYTHONPATH by Zope, it just wasn't there yet by default. Changed: U Zope/branches/2.9/skel/README.txt A Zope/branches/2.9/skel/lib/ -=- Modified: Zope/branches/2.9/skel/README.txt === --- Zope/branches/2.9/skel/README.txt 2006-01-16 13:33:20 UTC (rev 41323) +++ Zope/branches/2.9/skel/README.txt 2006-01-16 14:11:35 UTC (rev 41324) @@ -5,5 +5,6 @@ etc/ Configuration files Extensions/ Python sources for External Methods log/ Log files - Products/Installed products specific to the instance + lib/python/ Installed Python packages specific to the instance + Products/Installed Zope Products specific to the instance var/ Run-time data files, including the object database Copied: Zope/branches/2.9/skel/lib (from rev 41323, Zope/branches/Zope-2_8-branch/skel/lib) ___ Zope-Checkins maillist - Zope-Checkins@zope.org http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/trunk/skel/ Merge r41323 from 2.8 branch:
Log message for revision 41325: Merge r41323 from 2.8 branch: Make instances have a lib/python directory with a proper README.txt by default. Note that it's already automatically put on the PYTHONPATH by Zope, it just wasn't there yet by default. Changed: U Zope/trunk/skel/README.txt A Zope/trunk/skel/lib/ -=- Modified: Zope/trunk/skel/README.txt === --- Zope/trunk/skel/README.txt 2006-01-16 14:11:35 UTC (rev 41324) +++ Zope/trunk/skel/README.txt 2006-01-16 14:18:48 UTC (rev 41325) @@ -5,5 +5,6 @@ etc/ Configuration files Extensions/ Python sources for External Methods log/ Log files - Products/Installed products specific to the instance + lib/python/ Installed Python packages specific to the instance + Products/Installed Zope Products specific to the instance var/ Run-time data files, including the object database Copied: Zope/trunk/skel/lib (from rev 41323, Zope/branches/Zope-2_8-branch/skel/lib) ___ Zope-Checkins maillist - Zope-Checkins@zope.org http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/branches/2.9/lib/python/ZClasses/ZClass.txt Fix temp_folder mounting problem.
Log message for revision 41327:
Fix temp_folder mounting problem.
Othere tests don't pass though, maybe I think due to __implemented__ and
__provides__ attributes in the persistentclass state.
Changed:
U Zope/branches/2.9/lib/python/ZClasses/ZClass.txt
-=-
Modified: Zope/branches/2.9/lib/python/ZClasses/ZClass.txt
===
--- Zope/branches/2.9/lib/python/ZClasses/ZClass.txt2006-01-16 15:10:30 UTC
(rev 41326)
+++ Zope/branches/2.9/lib/python/ZClasses/ZClass.txt2006-01-16 16:38:25 UTC
(rev 41327)
@@ -16,6 +16,8 @@
from OFS.Application import Application
app = Application()
conn.root()['Application'] = app
+ from OFS.Folder import manage_addFolder
+ manage_addFolder(app, 'temp_folder')
from OFS.Application import initialize
initialize(app)
app.manage_addFolder('sandbox')
___
Zope-Checkins maillist - Zope-Checkins@zope.org
http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/trunk/lib/python/Zope2/Startup/handlers.py Remove use of deprecated module.
Log message for revision 41330: Remove use of deprecated module. Changed: U Zope/trunk/lib/python/Zope2/Startup/handlers.py -=- Modified: Zope/trunk/lib/python/Zope2/Startup/handlers.py === --- Zope/trunk/lib/python/Zope2/Startup/handlers.py 2006-01-16 17:35:51 UTC (rev 41329) +++ Zope/trunk/lib/python/Zope2/Startup/handlers.py 2006-01-16 17:50:57 UTC (rev 41330) @@ -175,8 +175,8 @@ # Augment the set of MIME types: if config.mime_types: -import OFS.content_types -OFS.content_types.add_files(config.mime_types) +from zope.app.contenttypes import add_files +add_files(config.mime_types) # if no servers are defined, create default http server and ftp server if not config.servers: ___ Zope-Checkins maillist - Zope-Checkins@zope.org http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/branches/ajung-zpt-strict-unicode/ This branch contains a ZPT implementation where the content _must_ be unicode in any case
Log message for revision 41331: This branch contains a ZPT implementation where the content _must_ be unicode in any case Changed: A Zope/branches/ajung-zpt-strict-unicode/ -=- Copied: Zope/branches/ajung-zpt-strict-unicode (from rev 41330, Zope/branches/ajung-zpt-integration) ___ Zope-Checkins maillist - Zope-Checkins@zope.org http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/branches/ajung-zpt-integration/lib/python/Products/PageTemplates/ZopePageTemplate.py a less restrictive implementation whose default behaviour
Log message for revision 41333:
a less restrictive implementation whose default behaviour
is the same as in all current Zope 2 implementation. Restrictive
unicode usage can be enforced by setting strict=True.
The code needs some more work concerning the encoding handling.
Changed:
U
Zope/branches/ajung-zpt-integration/lib/python/Products/PageTemplates/ZopePageTemplate.py
-=-
Modified:
Zope/branches/ajung-zpt-integration/lib/python/Products/PageTemplates/ZopePageTemplate.py
===
---
Zope/branches/ajung-zpt-integration/lib/python/Products/PageTemplates/ZopePageTemplate.py
2006-01-16 18:05:08 UTC (rev 41332)
+++
Zope/branches/ajung-zpt-integration/lib/python/Products/PageTemplates/ZopePageTemplate.py
2006-01-16 18:32:03 UTC (rev 41333)
@@ -90,8 +90,8 @@
_default_content_fn = os.path.join(package_home(globals()), 'pt',
'default.html')
+
-
class ZopePageTemplate(Script, PageTemplate, Historical, Cacheable,
Traversable, PropertyManager):
Z2 wrapper class for Zope 3 page templates
@@ -124,9 +124,10 @@
security.declareObjectProtected(view)
security.declareProtected(view, '__call__')
-def __init__(self, id, text=None, content_type=None, encoding='utf-8'):
+def __init__(self, id, text=None, content_type=None, encoding='utf-8',
strict=False):
self.id = id
-self.expand = 0
+self.expand = 0
+self.strict = strict
self.ZBindings_edit(self._default_bindings)
self.pt_edit(text, content_type, encoding)
@@ -134,7 +135,7 @@
def pt_edit(self, text, content_type, encoding='utf-8'):
text = text.strip()
-if not isinstance(text, unicode):
+if self.strict and not isinstance(text, unicode):
text = unicode(text, encoding)
self.ZCacheable_invalidate()
@@ -162,7 +163,7 @@
security.declareProtected(change_page_templates, 'pt_setTitle')
def pt_setTitle(self, title, encoding='utf-8'):
-if not isinstance(title, unicode):
+if self.strict and not isinstance(title, unicode):
title = unicode(title, encoding)
self._setPropValue('title', title)
@@ -368,7 +369,14 @@
def wl_isLocked(self):
return 0
+security.declareProtected(view, 'strictUnicode')
+def strictUnicode(self):
+ Return True if the ZPT enforces the use of unicode,
+False otherwise.
+
+return self.strict
+
def manage_convertUnicode(self, preferred_encodings=preferred_encodings,
RESPONSE=None):
convert non-unicode templates to unicode
@@ -430,7 +438,7 @@
manage_addPageTemplateForm= FSZPT('manage_addPageTemplateForm',
os.path.join(package_home(globals()), 'pt', 'ptAdd.pt'))
-def manage_addPageTemplate(self, id, title='', text=None, encoding='utf-8',
submit=None, REQUEST=None, RESPONSE=None):
+def manage_addPageTemplate(self, id, title='', text='', encoding='utf-8',
submit=None, REQUEST=None, RESPONSE=None):
Add a Page Template with optional file content.
filename = ''
___
Zope-Checkins maillist - Zope-Checkins@zope.org
http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-dev] Re: Zope tests: 6 OK, 2 Failed
The problem is that when I do: bin/zopectl test -s AccessControl everything works fine. However the buildbots do: python test.py -s AccessControl and this fails. I included a workaround, sigh. Florent Stefan H. Holek wrote: AFAIK the default configuration used by tests does not have a dbtab. See lib/python/App/config.py. Stefan On Jan 14, 2006, at 16:45, Florent Guillaume wrote: I'll look at it. Florent Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This failure is tie up with Florent's recent checkin: Log message for revision 41303: When a database is created by hand from a custom_zodb.py during startup, we still want to put it in the dbtab multidatabases dict. This happens when unit tests call Zope2.startup(), because Testing has a specific custom_zodb.py loaded at startup that uses a DemoStorage. Zope tests summarizer wrote: Summary of messages to the zope-tests list. Period Fri Jan 13 12:01:01 2006 UTC to Sat Jan 14 12:01:01 2006 UTC. There were 8 messages: 8 from Zope Unit Tests. Test failures - Subject: FAILED : Zope-2_9-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Fri Jan 13 21:10:37 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004008.html Subject: FAILED : Zope-trunk Python-2.4.2 : Linux From: Zope Unit Tests Date: Fri Jan 13 21:12:07 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004009.html -- 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] Zope tests: 6 OK, 2 Failed
Summary of messages to the zope-tests list. Period Sun Jan 15 12:01:02 2006 UTC to Mon Jan 16 12:01:02 2006 UTC. There were 8 messages: 8 from Zope Unit Tests. Test failures - Subject: FAILED : Zope-2_9-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Sun Jan 15 21:10:28 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004024.html Subject: FAILED : Zope-trunk Python-2.4.2 : Linux From: Zope Unit Tests Date: Sun Jan 15 21:11:58 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004025.html Tests passed OK --- Subject: OK : Zope-2_6-branch Python-2.1.3 : Linux From: Zope Unit Tests Date: Sun Jan 15 21:01:27 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004018.html Subject: OK : Zope-2_6-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Sun Jan 15 21:02:57 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004019.html Subject: OK : Zope-2_7-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Sun Jan 15 21:04:27 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004020.html Subject: OK : Zope-2_7-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Sun Jan 15 21:05:57 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004021.html Subject: OK : Zope-2_8-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Sun Jan 15 21:07:27 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004022.html Subject: OK : Zope-2_8-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Sun Jan 15 21:08:58 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004023.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] Strange traceback or Error in the traceback ?
Hi,
While seaching for objects of all types containing some text through the
ZMI find tab, I got the traceback hereunder. (Zope 2.7.8-final on
windows)
Traceback (innermost last):
Module ZPublisher.Publish, line 101, in publish
Module ZPublisher.mapply, line 88, in mapply
Module ZPublisher.Publish, line 39, in call_object
Module Shared.DC.Scripts.Bindings, line 306, in __call__
Module Shared.DC.Scripts.Bindings, line 343, in _bindAndExec
Module App.special_dtml, line 175, in _exec
Module DocumentTemplate.DT_With, line 61, in render
Module DocumentTemplate.DT_Util, line 198, in eval
- __traceback_info__: _
Module string, line 0, in ?
Module OFS.FindSupport, line 151, in ZopeFind
Module OFS.FindSupport, line 151, in ZopeFind
Module OFS.FindSupport, line 113, in ZopeFind
Module OFS.Image, line 425, in PrincipiaSearchSource
AttributeError: content_typestartswith
I went to the code and found the following :
def PrincipiaSearchSource(self):
Allow file objects to be searched.
if self.content_type.startswith('text/'):
return str(self.data)
return ''
IOW, the traceback is really strange.
Anybody with a clue ?
--
Godefroid Chapelle (aka __gotcha)http://bubblenet.be
___
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] Strange traceback or Error in the traceback ?
Hi,
Em Seg, 2006-01-16 às 16:20 +0100, Godefroid Chapelle escreveu:
Hi,
While seaching for objects of all types containing some text through the
ZMI find tab, I got the traceback hereunder. (Zope 2.7.8-final on
windows)
Traceback (innermost last):
[...]
Module OFS.Image, line 425, in PrincipiaSearchSource
AttributeError: content_typestartswith
I went to the code and found the following :
[...]
if self.content_type.startswith('text/'):
[...]
IOW, the traceback is really strange.
Anybody with a clue ?
I've seen this happen a few times before. In your case, content_type is
probably a standard python function (or method). When an unknown
attribute is looked up in a std python function like that, somehow you
get an AttributeError with the name of the function and the looked up
attribute concatenated, instead of separated by a dot (or more commonly,
instead of the attribute name alone).
Don't know if this is a bad interaction between
ExtensionClass/AttributeError and python, or a python bug.
Cheers, Leo
___
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 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: 2775 Blamelist: efge,jim 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] Deprecation process issues
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I've noticed a couple of problems with recent deprecation decisions (for OFS.content_types and zLOG). The major one is that the deprecation warning waw added without removing the code in the core which depends on the deprecated feature. The most obvious sign of this is that the tests no longer run clean, but are cluttered up with warning output. Another issue is that at least one of those choices (the zLOG one) seemed to land without accounting for the legitimate use cases which the new blessed method doesn't address (e.g, logging levels not offered by the standard 'logging' module). I'm about to check in changes which clean out the use of OFS.content_types, but am less willing to clean up the zLOG uses until the other use cases are addressed. 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 iD8DBQFDy9kb+gerLs4ltQ4RAiPBAJ0RD0HF3r0GhOm9JqTtsF/o1M/z3ACeNJTs 37iQ0WGsxgCYBOQ81xw9XnE= =+CgN -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] Deprecation process issues
Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I've noticed a couple of problems with recent deprecation decisions (for OFS.content_types and zLOG). The major one is that the deprecation warning waw added without removing the code in the core which depends on the deprecated feature. The most obvious sign of this is that the tests no longer run clean, but are cluttered up with warning output. Another issue is that at least one of those choices (the zLOG one) seemed to land without accounting for the legitimate use cases which the new blessed method doesn't address (e.g, logging levels not offered by the standard 'logging' module). I'm about to check in changes which clean out the use of OFS.content_types, but am less willing to clean up the zLOG uses until the other use cases are addressed. I haven't been following these issues, counting on y'all to figure it out. :) I'll just note that: - I agree with your point about deprecation warnings. IOW we should not check in new deprecation warnings on the trunk that cause warnings to be output when running the standard tests. We should correct any code that needs to be updated first. (Personally, I add the deprecation warning, making sure that I get the expected warnings, and then I make the warnings go away.) - I think that dropping functionality should be considered carefully. I'm inclined to accept your judgement that the use cases need to be addressed. Of course, we do want to move away from zLOG, as we want to leverage the standard logging framework. 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] Deprecation process issues
--On 16. Januar 2006 13:08:31 -0500 Jim Fulton [EMAIL PROTECTED] wrote: I'll just note that: - I agree with your point about deprecation warnings. IOW we should not check in new deprecation warnings on the trunk that cause warnings to be output when running the standard tests. We should correct any code that needs to be updated first. (Personally, I add the deprecation warning, making sure that I get the expected warnings, and then I make the warnings go away.) But you can only correct code when you have a reasonable replacement. In case we should use my current ZPT replacement based on the Z3 implementation we would deprecate lib/python/TALES and have deprecation warnings for two major releases. But we can't replace lib/python/TALES with the Z3 tal|tales packages since we can expect incompatibilities which are not acceptable for backward compatibility issues. One could write fascades for such modules (Philipp already wrote one for STX) but I doubt that they will be 100% compatible. I would prefer to keep such modules in place and to just remove them after the deprecation period. Of course, we do want to move away from zLOG, as we want to leverage the standard logging framework. Has there ever been the need/demand for additional log levels in Z3? -aj pgpO4ad33XNks.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] ZPT backward compatibility
Andreas Jung wrote: --On 16. Januar 2006 13:08:31 -0500 Jim Fulton [EMAIL PROTECTED] wrote: I'll just note that: - I agree with your point about deprecation warnings. IOW we should not check in new deprecation warnings on the trunk that cause warnings to be output when running the standard tests. We should correct any code that needs to be updated first. (Personally, I add the deprecation warning, making sure that I get the expected warnings, and then I make the warnings go away.) But you can only correct code when you have a reasonable replacement. In case we should use my current ZPT replacement based on the Z3 implementation we would deprecate lib/python/TALES and have deprecation warnings for two major releases. But we can't replace lib/python/TALES with the Z3 tal|tales packages since we can expect incompatibilities which are not acceptable for backward compatibility issues. One could write fascades for such modules (Philipp already wrote one for STX) but I doubt that they will be 100% compatible. I would prefer to keep such modules in place and to just remove them after the deprecation period. There are two separate issues here: 1. ZPT backward compatibility. Are we introdcuting ZPT backward incompatibilities? (Aside from module paths)? If so, then I think we need to have a proposal. (Maybe you already made one and I wasn't paying attention. I don't see one at: http://www.zope.org/Wikis/DevSite/Proposals/FrontPage. 2. If we decide to change something, even if it's backward incompatible, we need to change Zope itself to do things the new way before we expect other people to and before we introduce the deprecation warning. If there isn't a valid new way of doing something, then we can't deprecate the old way. 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] Re: ZPT backward compatibility
--On 16. Januar 2006 13:36:32 -0500 Jim Fulton [EMAIL PROTECTED] wrote: There are two separate issues here: 1. ZPT backward compatibility. Are we introdcuting ZPT backward incompatibilities? (Aside from module paths)? My original implementation would introduce incompatibilities definitely. However I've just checked in a relaxed implementation that defaults to the current behaviour. Enforcing unicode is now an optinal feature which might be used for application that are interested to use unicode for ZPTs starting Zope 2.10. If so, then I think we need to have a proposal. (Maybe you already made one and I wasn't paying attention. I don't see one at: http://www.zope.org/Wikis/DevSite/Proposals/FrontPage. Well, I brought this issue up on zope-dev to discuss this issue directly. but with almost zero feedback :-) Also another related posting to zope-zpt got _zero_ anwers. Also other changes happened are part of a (pending) proposal written by Philipp. 2. If we decide to change something, even if it's backward incompatible, we need to change Zope itself to do things the new way before we expect other people to and before we introduce the deprecation warning. Nothing else happened so far (except the issue with OFS.content_types in Zope 2.9. I just forgot to change the code for the 2.9 final release. There was something to hinder me from doing that for 2.9b2). -aj pgpHL6IJ8WlKJ.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] Authorization Problems while using manage_addFile()
We have imported a zope application from another machine. After starting the application we are unable to create a file using using the API manage_addFile(),which is strange because we are being able to use the API manage_delObjects() to delete an existing object. This is the Error we have encountered.. *** Site Error An error was encountered while publishing this resource. Unauthorized Sorry, a site error occurred. Traceback (innermost last): * Module ZPublisher.Publish, line 175, in publish_module_standard * Module Products.iHotfix, line 88, in new_publish * Module ZPublisher.Publish, line 132, in publish * Module Zope.App.startup, line 204, in zpublisher_exception_hook * Module ZPublisher.Publish, line 101, in publish * Module ZPublisher.mapply, line 88, in mapply * Module ZPublisher.Publish, line 39, in call_object * Module Shared.DC.Scripts.Bindings, line 306, in __call__ * Module Shared.DC.Scripts.Bindings, line 343, in _bindAndExec * Module Products.PythonScripts.PythonScript, line 323, in _exec * Module None, line 4, in reset_tab PythonScript at /VCS/reset_tab Line 4 * Module Shared.DC.Scripts.Bindings, line 306, in __call__ * Module Shared.DC.Scripts.Bindings, line 343, in _bindAndExec * Module Products.PythonScripts.PythonScript, line 323, in _exec * Module None, line 1, in refresh_tab PythonScript at /VCS/refresh_tab Line 1 * Module Shared.DC.Scripts.Bindings, line 306, in __call__ * Module Shared.DC.Scripts.Bindings, line 343, in _bindAndExec * Module Products.PythonScripts.PythonScript, line 323, in _exec * Module None, line 9, in update_result PythonScript at /VCS/update_result Line 9 Unauthorized: You are not allowed to access 'manage_addFile' in this context (Also, an error occurred while attempting to render the standard error message.) *** We have tried changing all the security permissions,we have even logged in administrator but this too has been of no use. We are using Zope Version (Zope 2.7.8-final, python 2.4.0) Python Version 2.4 Thanks ___ 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] Authorization Problems while using manage_addFile()
--On 16. Januar 2006 14:02:22 +0530 Varun Bhansaly [EMAIL PROTECTED] wrote: We have imported a zope application from another machine. After starting the application we are unable to create a file using using the API manage_addFile(),which is strange because we are being able to use the API manage_delObjects() to delete an existing object. VerboseSecurity can tell you why this error occurs... -aj pgpd8jS4hKk10.pgp Description: 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] wrong directoy in Control_Panel.Products.XXXX.home
En/na Dieter Maurer ha escrit: Zope's behaviour in handling product updates below Control_Panel.Products is very difficult to understand. ;-) It usually freaks me out when I (seldom) delete a product from the filesystem and it's still there in the control panel.. Almost surely, it will help when you delete all closed products there and then restart Zope. The restart will recreate the product objects for installed products -- hopefully with the correct home attribute. yes, as I said in the original message this is what I did. I was just asking if this is the expected behaviour of Control_Panel (which could break products using the home attribute, like in my case CMFQuickInstaller) and if there is a better(?) way that doesn't involve deleting the products and restarting zope. Bye -- Luca Olivetti Wetron Automatización S.A. http://www.wetron.es/ Tel. +34 93 5883004 Fax +34 93 5883007 ___ 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] Leave the ivory tower now!
Rakotomandimby Mihamina wrote: On Mon, 2006-01-09 at 14:29 +0100, Garito wrote: I thing DTML and ZClasses will disapear someday You think, I hope :-) I beg ;-) . ___ 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] Leave the ivory tower now!
Nicolas Georgakopoulos wrote: Rakotomandimby Mihamina wrote: On Mon, 2006-01-09 at 14:29 +0100, Garito wrote: I thing DTML and ZClasses will disapear someday You think, I hope :-) I beg ;-) . ___ Can someone explain why there is a continual battle between those who like dtml and those who like zpt? Surely the two can co-exist and then individual developers can choose which most suits them. Neither seems to be broken and both provide a valid experience for users, so let's be tolerant. :-) regards Garry ___ 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] ANN: ZSyncer 0.7.1-beta1 released
Paul Winkler wrote at 2006-1-15 17:28 -0500: ... Yes. These are limitations of comparing objects that have only a bobobase_modification_time timestamp. See ZSyncer/README.txt, in the Usage section. Solving this problem is hard. See ZSyncer/TODO.txt. You should remember the synchronized bobobase_modification_times (this may cost an additional (small) request). I'm sorry, I can't seem to understand what you mean. Synchronization modifies bobobase_modification_time on the target. A safe method to check whether you have a current state is to register the bobobase_modification_time (on source and target) that resulted from the synchronization. A resynchronization is necessary when the bobobase_modification_time moved away from the registered sync_bobobase_times. -- 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] ANN: ZSyncer 0.7.1-beta1 released
On Mon, Jan 16, 2006 at 07:48:45PM +0100, Dieter Maurer wrote: Synchronization modifies bobobase_modification_time on the target. Yep. A safe method to check whether you have a current state is to register the bobobase_modification_time (on source and target) that resulted from the synchronization. A resynchronization is necessary when the bobobase_modification_time moved away from the registered sync_bobobase_times. Ahhh, now I see. Thank you, this is probably cheaper than most of my ideas. I could store that info in a BTree of some flavor. -- Paul Winkler http://www.slinkp.com ___ 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] Leave the ivory tower now!
I took part in an old thread from here from several months ago:http://www.gossamer-threads.com/lists/zope/users/184052?do=post_view_threaded In there, some of the prominent members from this list came up with some great points on the DTML vs ZPT thing. All great stuff. However, I agree with you. While some of the ZPT fans say that DTML is broke and it sucks, and from there perspective it might, for some of us DTML is great and we have no desire to use ZPT. For us, DTML is not broke. I like what you said, be tolerant. Some of us don't see the limitations of DTML as something that is broken, or that it is not good. I don't think there is anything wrong with ZPT either, I simply don't have a use for it. Coexist? Yes, I hope they always do. Personally, I am doing more and more with PHP. There are multiple reasons for that, but partly it is due to a conception in the Zope community that DTML is bad, and as such, it might go away. The *hype* is all about ZPT, not DTML. I don't want to pursue a development platform that is a foundation of my applications on something that is going away, or even hinting to it. That might not be the case, might be totally false. But we cant deny the fact that if there is no hype, then there is no attention to it, and less people will use it and even less will support it. Now don't get me wrong about that last paragraph, I LOVE ZOPE! It just does things so easily that other environments have to struggle with. (Acquisition being one of them. Which also is something that people say is broke in some ways. It does do weird things sometimes. But if you know how to deal with them... ;) I hope my opinions are of help to others. (just remember, these are just my opinions, to those to might be ready to slam me for them. I intend no offense.)GregOn 1/16/06, garry [EMAIL PROTECTED] wrote: Nicolas Georgakopoulos wrote: Rakotomandimby Mihamina wrote: On Mon, 2006-01-09 at 14:29 +0100, Garito wrote: I thing DTML and ZClasses will disapear someday You think, I hope :-) I beg ;-). ___Can someone explain why there is a continual battle between those who like dtml and those who like zpt?Surely the two can co-exist and then individual developers can choosewhich most suits them. Neither seems to be broken and both provide avalid experience for users, so let's be tolerant. :-) regardsGarry___Zope maillist-Zope@zope.orghttp://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 )-- Greg Fischer1st Byte Solutionshttp://www.1stbyte.com ___ 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] Leave the ivory tower now!
Greg Fischer schrieb: ... I like what you said, be tolerant. Some of us don't see the limitations of DTML as something that is broken, or that it is not good. I don't I see we have to improve teaching. think there is anything wrong with ZPT either, I simply don't have a use for it. Coexist? Yes, I hope they always do. Personally, I am doing more and more with PHP. There are multiple reasons for that, but partly it is due to a conception in the Zope community that DTML is bad, and as such, it might go away. The *hype* is all about ZPT, not DTML. I don't want to pursue a development platform You can have PT with PHP too. Thats the cool part about it. Its really kinda standard. You have PT for Zope, PHP, Perl, Java, ... that is a foundation of my applications on something that is going away, or even hinting to it. That might not be the case, might be totally false. But we cant deny the fact that if there is no hype, then there is no attention to it, and less people will use it and even less will support it. I dont think thats the problem. I saw even weirder frameworks to work with. I guess we could introduce an even suckier template language and people would fall in love with it. BTW: ZPT is not, and was never a replacement for DTML. DTML would be replaced by application logic in python or python scripts and ZPT together. No matter if DTML is still there (and it will) we should find better ways to teach people how to easy develope in Zope. ++Tino ___ 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] Where oh where is Repozo
Does the Zope Wiki article on Repozo tell you where to find it, maybe I missed it. I actually looked for quite a while. Maybe it just needs to be a little clearer... or maybe I need a smack in the head. I didn't have much success anyway, I setup my Zope/ZEO setup using SuSE 9.0's onboard Python and PIL installs, which, at the time, seemed an easy way to reproduce a ZEO client machine over and over. Upon running repozo, it can't find the pieces of Zope/ZODB, it needs to run, and I get an immediate traceback refering to the import of ZODB. After trying to adjust the pythonpath (wouldn't stick), and trying to drop repozo in the right directory. I couldn't get it to work. And, frankly, with everything Zope/Python/PIL working fine, I didn't mess with it very hard, fearing breaking it. Using SuSE's YAST installed Python seems to be my mistake... but It made sense at the time, and the right versions and everything... and although it works, upgrading Zope and using repozo are major drawbacks. I'll have to build a new box, correctly, and migrate to it. In any case, thanks for your time, -Jon Tim Peters wrote: [Jonathan Cyr] Where is the latest version of Repozo, the backup tool, kept? Is there a reason, that it's not included with the Zope install/utilities (at least the 2.7.x I'm using). [... time passes ...] Thanks for the quick response, I noticed that the my WinXP Zope (sandbox) doesn't have it, but my production SuSE Linux does. It's in my WinXP Zope-2_7-branch sandbox: C:\Code\Zope-2_7-branchdir/b utilities\ZODBTools\rep* repozo.py It's also in Zope 2.8 branch, 2.9 branch, and current Zope trunk. For some reason (oversight?), Zope3 does not include ZODB tools, but you should find them in every flavor of Zope2 (and of course a CVS or SVN sandbox gets you the same stuff no matter which platform you use to do the checkout). ___ 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 ) -- Jonathan Cyr http://www.cyr.info http://www.weddingweblog.com [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] Leave the ivory tower now!
>From Tino: --No matter if DTML is still there (and it will) we shouldfind better ways to teach people how to easy develope inZope.--Yes, you are right on all you mention. I didn't know PT was available in other environments/languages. Interesting. However, I still don't want to use them. Doesn't mean that someday I wont find a need and desire for it though. The reason I don't use PT is because I can do what I want without it. You mention that better ways to teach is needed, and you are right about that, but when someone like me has no desire to learn it, then it wont help. Worth noting though, I have looked at it briefly, and it confused the hell out of me. So, you may be right on anyway, because if it were explained in a such a way that caused me to just *get it*, then maybe I would go that route. I guess it's really a matter of, do I want to spend the time to learn something when I am loaded with other things to learn all the time, and why fix it if it isnt broke? (broke from my perspective ,that is.) Well, why can't there also be good training on DTML as well? (actually, I don't thinks it's all that bad anyway.) And, like Gary asked, why can't there be a peaceful coexistence bewteen the ZPT and DTML fans? The reason why I ask? Because there is commonley someone saying *DTML sucks, use PT* when users ask questions about DTML. (maybe not in those words, but you get the idea.) I don't know. I do appreciate your responses and thoughts Tino. (as you have always done for me in the past)GregOn 1/16/06, Tino Wildenhain [EMAIL PROTECTED] wrote:Greg Fischer schrieb: ... I like what you said, be tolerant.Some of us don't see the limitations of DTML as something that is broken, or that it is not good.I don'tI see we have to improve teaching. think there is anything wrong with ZPT either, I simply don't have a use for it.Coexist? Yes, I hope they always do. Personally, I am doing more and more with PHP.There are multiple reasons for that, but partly it is due to a conception in the Zope community that DTML is bad, and as such, it might go away. The *hype* is all about ZPT, not DTML.I don't want to pursue a development platformYou can have PT with PHP too. Thats the cool part about it. Its reallykinda standard. You have PT for Zope, PHP, Perl, Java, ... that is a foundation of my applications on something that is going away, or even hinting to it.That might not be the case, might be totally false.But we cant deny the fact that if there is no hype, then there is no attention to it, and less people will use it and even less will support it.I dont think thats the problem. I saw even weirder frameworksto work with. I guess we could introduce an even suckier template language and people would fall in love with it.BTW: ZPT is not, and was never a replacement for DTML.DTML would be replaced by application logic in pythonor python scripts and ZPT together.No matter if DTML is still there (and it will) we should find better ways to teach people how to easy develope inZope.++Tino-- Greg Fischer1st Byte Solutionshttp://www.1stbyte.com ___ 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] Autoconnect with ZMySQLDA 2.0.9
I have been seeing occasional release unlocked lock errors from a storage error in a two-phase commit which really comes from a Lost connection to MySQL server during query. Apparently this arises from a failure of self.db.ping() to find a connected database as the transaction is opened. It is possible that the connection has really timed out. Looking at the code it appears that ZMySQLDA does not attempt to recreate the connection. Is that correct? What's the recommend approach to re-establish the connection? -d -- ___ 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] MySql 5.0, ZMySQLDA and stored procedures
I was getting the following error when attempting to call a stored procedure
via a Z SQL Method:
_mysql_exceptions.OperationalError: (1312, etc
So I made the following change to
/usr/lib/zope/lib/python/Products/ZMySQLDA/db.py:
def _parse_connection_string(self, connection):
kwargs = {'conv': self.conv,
'client_flag': 65536 #inserted by CSB
}
I then restarted Zope. I can now successfully call stored procedures. There
may be a better way to do it. Feel free to advise if so.
Apologies if this information has already been posted.
Cameron
___
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] Where oh where is Repozo
On Jan 16, 2006, at 22:52, Jonathan Cyr wrote: Does the Zope Wiki article on Repozo tell you where to find it, maybe I missed it. I actually looked for quite a while. Maybe it just needs to be a little clearer... or maybe I need a smack in the head. I didn't have much success anyway, I setup my Zope/ZEO setup using SuSE 9.0's onboard Python and PIL installs, which, at the time, seemed an easy way to reproduce a ZEO client machine over and over. Upon running repozo, it can't find the pieces of Zope/ZODB, it needs to run, and I get an immediate traceback refering to the import of ZODB. After trying to adjust the pythonpath (wouldn't stick), and trying to drop repozo in the right directory. I couldn't get it to work. And, frankly, with everything Zope/Python/PIL working fine, I didn't mess with it very hard, fearing breaking it. Using SuSE's YAST installed Python seems to be my mistake... but It made sense at the time, and the right versions and everything... and although it works, upgrading Zope and using repozo are major drawbacks. I'll have to build a new box, correctly, and migrate to it. In any case, thanks for your time, -Jon I had the same problem with repozo. I solved it by modifying the repozo.py file and adding sys.path.append( PATH/TO/ZOPE/lib/python ) right before the from ZODB.FileStorage ... line. It's not a beautiful fix, but it works. ___ 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-DB] I need urgent help !!!
HEllo my name is Gustavo I am from chile(southamerica), my english is not so good, sorry for that, well my cuestion is the next, i need do a web single sign-on whit my plone (ZOPE) web sites, i have a apache2.0 server too, i need help whit these item because my job depend of taht, any answer send me to my mail adress [EMAIL PROTECTED], thank you very much, and i hope for your help, bye bye... - Stay ahead of the information curve. Receive EDA news and jobs on your desktop daily. Subscribe today to the EDA CafeNews newsletter. [ http://www10.edacafe.com/nl/newsletter_subscribe.php ] It's informative and essential. ___ Zope-DB mailing list Zope-DB@zope.org http://mail.zope.org/mailman/listinfo/zope-db
