- Zope-Dev - Zope lists

Minor windows intaller bug and a question
by Sergey Volobuev 05 Feb '04

05 Feb '04

Hi all, Installing 2.7.0rc2 windows zope installer, i noticed that it uses hard-coded value for instance directory. The proposed value is "C:\Zope-Instance". However, some users (me :) don't have C: drive. For some reasons windows choose G: letter for boot drive and (unlike not-boot drives) this letter can't be changed. Most installers autodetect this situation but Zope installer not. And now the question: I want to make customized Zope installer. I.e. i want to include some products, data in ZODB, etc. so i can give single exe file to my customer, he will install it and get ready-to-work site figurally in one click. Something like Plone installer did. So, are there some guidelines how it can be done (howtos, docs, scripts, etc)? Unfortunately, my expirience in making installers is limited to InstallShield usage in mid 90th :(

5 9

FW: [Zope-dev] strange behavior of VirtualHostMonster
by zope-dev＠netchan.cotse.net 05 Feb '04

05 Feb '04

Okay, I debugged a bit more: > [u'loginUser', u'usermgrFolder', '/', 'VHM'] <= this looks weird to me It seems it's pretty okay, however the last line in VirtualHostMonster.__bobo_traverse__ says: return parents.pop() # He'll get put back on Of course, the popped item is 'a', that's the one with the beforetraversal hook, so if it's really put back on later, than the hook will run again. I think this is the explanation, but the question remains: how can I avoid the second call to the beforetraverse hook? Regards, Sandor _______________________________________________ Zope-Dev maillist - Zope-Dev(a)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 )

2 1

strange behavior of VirtualHostMonster
by zope-dev＠netchan.cotse.net 05 Feb '04

05 Feb '04

I have a zope-behind-an-apache configuration (OpenBSD 3.4, Zope2.7rc1, python 2.3.3, apache 1.3x). Inside the zope root, there's a folder called 'Instances', and inside this there's my custmo object (eLMS) called 'a': /Instances/a. A beforetraverse hook is registered on 'a'. I configured two access paths to this object in apache: <VirtualHost 1.2.3.4:443> RewriteRule ^/(.*) http://127.0.0.1:8003/VirtualHostBase/https/test.server.org:443/Instance s/a/VirtualHostRoot/$1 [L,P] </VirtualHost> <VirtualHost 1.2.3.4:444> RewriteRule ^/(.*) http://127.0.0.1:8003/VirtualHostBase/https/test.server.org:444/VirtualH ostRoot/$1 [L,P] </VirtualHost> (I omitted the irrelevant parts) The first one is the 'main entrance' directly to the 'a' object via https://test.server.org, the other one is a 'service entrance' to the root folder via https://test.server.org:444. Problem: if I try to access anything via the 'main entrance', the beforetraverse hook is called two times. Also I have strange things inside BaseRequest.traverse, like '/' on the path. My question: is the first rewrite rule a valid one? If not, how can I achieve the same results with a valid one? A debug shot from the traverse call: > /zope/zopestable/lib/python/ZPublisher/BaseRequest.py(257)traverse() (Pdb) path [u'loginUser', u'usermgrFolder', '/', 'VHM'] <= this looks weird to me (Pdb) parents [<Application instance at 3cdb9fb0>, <Folder instance at 3cdcc8f0>, <eLMS instance at 3cdc5260>] (Pdb) request.get_header('PATH_INFO') '/VirtualHostBase/https/test.elms.vanth.org:443/Instances/a/VirtualHostR oot/' Regards, Sandor

1 0

change to zLOG.LOG() behavior
by Jeremy Hylton 04 Feb '04

04 Feb '04

I noticed that Zope 2.7 and Zope 2.8 changed the default zLOG implementation to use the logging package. There's one subtle consequence of that change that I wonder if people are aware of. The zLOG.LOG() call takes an optional error argument that contains a 3-tuple of exception information as returned by sys.exc_info(). In the old zLOG, this exception was formatted and logged. In the new zLOG, the error argument is treated as a flag; if it is not None, the *current* exception is formatted and logged. Should I change my code to pass True for error instead of sys.exc_info()? There is at least one place in ZODB that is broken as a result of that change. The old API allowed code to capture an exception with sys.exc_info() and log it later. The common pattern seemed to be to capture the error, try to recover, and only log the original exception of recovery failed. I don't think there's a good solution to the problem, except to change all the code that tries to be clever about capturing exceptions. This affects some ZODB code that was a culprit in recent bug reports that locked up Zope. As a result my fix -- which was supposed to log a helpful traceback rather than prevent Zope from locking up -- probably didn't work. Should we give up on fixing this bug for Zope 2.7? Jeremy

1 0

bug in 2.6.2, 2.6.1 , and probably others.
by Romain Slootmaekers 04 Feb '04

04 Feb '04

Yo, I just stumbled on a bug in the python scripting parameter passing. It seems that under certain conditions, the actual parameters are ignored, and the default parameters are always used. It is best shown by the following example: 0) create a python script with the following source: ## Script (Python) "buggy" ##bind container=container ##bind context=context ##bind namespace= ##bind script=script ##bind subpath=traverse_subpath ##parameters=a = 'default_a', b = 'default_b', c = 'default_c' ##title=exposes a bug in 2.6.1 and 2.6.2 ## print a print b print c return printed 1) in the ZMI click on the "test" tab and fill in the values: parameter value a a b b c c 2) click on "run script" 3) the result page is: default_a default_b default_c that's not what it should be. I quickly browsed the bug collector and did not found a related issue, but before I file a bug report, I'd like to know what versions are affected. I don't have the time nor the desire to install all versions and test this. So if you guys could take a minute to test it on your version. tia, Romain Slootmaekers.

6 6

Zope 2.7.0 rc2 + python 2.3.3 problem
by Florent Guillaume 03 Feb '04

03 Feb '04

I should have copied zope-dev, sorry. -------- Original Message -------- To: zope-coders(a)zope.org I'm having a weird failure here using Zope 2.7.0 rc2 and python 2.3.3 (Debian). When I execute a python script with the code: foo = range(1.0) I get this: Error Type: TypeError Error Value: unsubscriptable object Traceback (innermost last): * Module ZPublisher.Publish, line 104, in publish * Module warnings, line 57, in warn * Module warnings, line 63, in warn_explicit Instead of the expected: DeprecationWarning: integer argument expected, got float I don't know if it's python's fault or Zope's... But I guess python assumes too much about something as it fails in its standard libraries. If i use the code for i in range(1.0): pass The traceback is a bit longer: Error Type: TypeError Error Value: unsubscriptable object Traceback (innermost last): * Module ZPublisher.Publish, line 100, in publish * Module ZPublisher.mapply, line 88, in mapply * Module ZPublisher.Publish, line 40, 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 318, in _exec * Module None, line 1, in testbug <PythonScript at /testbug> Line 1 * Module AccessControl.ZopeGuards, line 210, in next * Module warnings, line 57, in warn * Module warnings, line 63, in warn_explicit TypeError: unsubscriptable object Florent -- Florent Guillaume, Nuxeo (Paris, France) +33 1 40 33 79 87 http://nuxeo.com mailto:fg@nuxeo.com

4 6

[leadership/opensource] invitation to online survey
by Gianluca Bosco 03 Feb '04

03 Feb '04

Dear all, I have just put online a survey addressing the topic of "leadership in the open-source environment". Basically, my objective is to identify the personal conceptions of good leadership that reside in the minds of the contributors, in terms of leaders' _behaviors_ and _characteristics_. What is a good open-source project leader, from the contributor's point of view? To what extent, those personal believes are shared among developers? Can the contributor's national cultural belonging and level of experience in contributing to open-source projects explain such differences in their idea of what a good leader is? I would really appreciate your participation to the survey! Contribution (*completely* anonymous) consists in rating a list of statements that may be used to describe the behaviors of an open-source leader. It will take around ten minutes - there aren't any "time-consuming" open ended questions;) Following, the link to the survey: http://freeonlinesurveys.com/rendersurvey.asp?id=52191 If you are interested, I will not miss to email you a link to the final report, when ready ;) (approx, a couple of months from now) Thank you in advance, and don't hesitate to contact me if you have any questions or comments :) Gianluca Bosco g.bosco(a)GETRIDOFTHISinwind.it Denmark Technical University Department of manufacturing engineering and management

1 0

Security validation issue
by Herman Geldenhuys 30 Jan '04

30 Jan '04

I've written a Zope product that exposes a "MenuItem". I add a menuItem in a Zope folder, and I have no difficulty accessing and editing it via the ZMI. I've written an xml-rpc-like protocol for Zope, that basically validates the security "manually". This menuItem has an attribute called "def getVersion(self):" which returns an int. This is the Code that prevents me from accessing the method in python, via my protocol: if not AccessControl.getSecurityManager().validate(None, object, attributes[-1]): raise UnauthorisedAccessException('Unauthorised: ' + originalAddress) object = <bound method HWMenuItem.getVersion of <HWMenuItem instance at 01B7B290>> This is the method getVersion attributes[-1] = "getVersion" (string) UnauthorisedAccessException: Unauthorised: menus.administration.addUser.getVersion This code works for any other default Zope type, but not mine. Did I perhaps forgot a permission or something? I can access this fine via the ZMI, but when I validate it this way, python just starts cursing at me. Can somebody help? Thanks H

2 2

Call for testing (2.6.4 / 2.7.0)
by Brian Lloyd 29 Jan '04

29 Jan '04

Hi all - Tres and I have been working to merge some final fixes, and I'd like to be able to make rc2 releases for 2.6.4 and 2.7.0 tomorrow. In the meantime, it would be helpful for anyone who runs from the 2.6 or 2.7 branches in CVS to update and let us know if you have any unresolved problems. It would be especially helpful for those who were having trouble with things like workflow scripts under the rc1 releases to give this a shot and let us know if the trouble is resolved. **Note that you need to rebuild the C extensions, due to a fix to cAccessControl. Be sure to do this before reporting any lingering issues!** Thanks, Brian Lloyd brian(a)zope.com V.P. Engineering 540.361.1716 Zope Corporation http://www.zope.com

4 5

Features for Zope 2.8
by Christian Theune 29 Jan '04

29 Jan '04

Hi. As Zope 2.7 looks like could-be-out-soon. I'd like to ask if there is room for including the post-traverse patch in Zope 2.8. I'm currently maintaining it as a patch on a branch for Zope 2.7, but would like to see it back in the mainstream. Short description of it: - Sometimes you want to run code before the published object as in the before_traverse hooks. But there you miss to variables: The object to be published and security context. - During traversal you can register yourself to be called after those two variables have been determined. This results in a chain of methods to be callen. - When the methods are callen, they get the necessary contexts and can return None (everything as usual) or return something else, that should be used for publication instead of the object that was found by traversal. (Note: I intended it that the REQUEST['PUBLISHED'] remains the one found by traversal.) This also discontinues the chain of post traversal calls. If this is feature could be a candidate for 2.8, i'll write a more in-depth proposal on it, and can provide the necessary code. Cheers, Christian -- Christian Theune, gocept gmbh & co. kg http://www.gocept.com - ct(a)gocept.com fon: 03496 3099112 fax: 03496 3099118 mobile: 0179 7808366

2 1