[Zope-dev] traversable methods / docstrings.
Hi! I didn't know that methods needed to have docstrings to be traversable (it took me some time to find out why I was getting Not found errors on some of a tool's methods). Is there any reason to still have such a feature in Zope2.9? or at least maybe there could be a hint in the trace log. regards /JM ___ 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 Sun Jan 29 12:01:01 2006 UTC to Mon Jan 30 12:01:01 2006 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: Sun Jan 29 21:05:42 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004130.html Subject: OK : Zope-2_6-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Sun Jan 29 21:07:12 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004131.html Subject: OK : Zope-2_7-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Sun Jan 29 21:08:42 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004132.html Subject: OK : Zope-2_7-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Sun Jan 29 21:10:13 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004133.html Subject: OK : Zope-2_8-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Sun Jan 29 21:11:43 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004134.html Subject: OK : Zope-2_8-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Sun Jan 29 21:13:13 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004135.html Subject: OK : Zope-2_9-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Sun Jan 29 21:14:43 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004136.html Subject: OK : Zope-trunk Python-2.4.2 : Linux From: Zope Unit Tests Date: Sun Jan 29 21:16:13 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004137.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] Re: traversable methods / docstrings.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jean-Marc Orliaguet wrote: I didn't know that methods needed to have docstrings to be traversable (it took me some time to find out why I was getting Not found errors on some of a tool's methods). Is there any reason to still have such a feature in Zope2.9? Publishable methods have docstrings is the oldest security model in Zope / Bobo. It would open unknown security holes in 3rd party applications if we removed that restriction. Even setting the default value of '__allow_access_to_unprotected_subobjects__' to False wouldn't help, because there are many products which set that to True for their objects, relying on the lack of docstring to make their methods safe from direct URL access. In fact, this restriction is *different* than the permission-role one: even methods whose roles are None (i.e. public), and therefore can be called by scripts run by anonymous users, are prevented from being published if they have no docstrings. or at least maybe there could be a hint in the trace log. I *thinK* if you run in debug mode with verbose security turned on, it suggests that as one possible reason. 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 iD8DBQFD3h0R+gerLs4ltQ4RAlmLAKCrmf+35VoB3BDFS2EhmL/xdTsPgQCgsVOw wQwUqnMOPLJcamP13ziZ4rQ= =KoIC -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: traversable methods / docstrings.
If somebody gets time to do the suggested refactoring of the publisher for 2.10, then the docstring requirement could be dropped for IFiveTraversable objects, I think. or? ___ 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: traversable methods / docstrings.
Lennart Regebro schrieb: If somebody gets time to do the suggested refactoring of the publisher for 2.10, then the docstring requirement could be dropped for IFiveTraversable objects, I think. Otoh, whats wrong with docstrings anyway? :-) Regards Tino ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] traversable methods / docstrings.
On Mon, Jan 30, 2006 at 11:34:17AM +0100, Jean-Marc Orliaguet wrote: Hi! I didn't know that methods needed to have docstrings to be traversable (it took me some time to find out why I was getting Not found errors on some of a tool's methods). Is there any reason to still have such a feature in Zope2.9? or at least maybe there could be a hint in the trace log. I thought the docstring requirement only applied to publishing, not traversal per se? Do you get Not found when doing e.g. restrictedTraverse(some_path)? -- 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] traversable methods / docstrings.
Paul Winkler wrote: On Mon, Jan 30, 2006 at 11:34:17AM +0100, Jean-Marc Orliaguet wrote: Hi! I didn't know that methods needed to have docstrings to be traversable (it took me some time to find out why I was getting Not found errors on some of a tool's methods). Is there any reason to still have such a feature in Zope2.9? or at least maybe there could be a hint in the trace log. I thought the docstring requirement only applied to publishing, not traversal per se? Do you get Not found when doing e.g. restrictedTraverse(some_path)? no then it works, and also when methods are called from inside page templates. That's the publisher that doesn't find it. /JM ___ 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: traversable methods / docstrings.
Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jean-Marc Orliaguet wrote: I didn't know that methods needed to have docstrings to be traversable (it took me some time to find out why I was getting Not found errors on some of a tool's methods). Is there any reason to still have such a feature in Zope2.9? Publishable methods have docstrings is the oldest security model in Zope / Bobo. It would open unknown security holes in 3rd party applications if we removed that restriction. Even setting the default value of '__allow_access_to_unprotected_subobjects__' to False wouldn't help, because there are many products which set that to True for their objects, relying on the lack of docstring to make their methods safe from direct URL access. In fact, this restriction is *different* than the permission-role one: even methods whose roles are None (i.e. public), and therefore can be called by scripts run by anonymous users, are prevented from being published if they have no docstrings. or at least maybe there could be a hint in the trace log. I *thinK* if you run in debug mode with verbose security turned on, it suggests that as one possible reason. Tres. One extra difficulty when debugging with that model is that .pyc files must be deleted if the .py is modified. since apparently docstrings are ignored during the compilation. But now I know :-) /JM ___ 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: traversable methods / docstrings.
Jean-Marc Orliaguet wrote at 2006-1-30 16:52 +0100: ... One extra difficulty when debugging with that model is that .pyc files must be deleted if the .py is modified. since apparently docstrings are ignored during the compilation. This is not the case (unless you use -OO and even then, the .pyc file would be recreated). -- 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-dev] Re: [ZODB-Dev] Weird ConflictErrors - TemporaryStorage bug?
Dieter Maurer wrote: Okay, I see: TemporaryStorage raises ConflictError when other storages would raise POSKeyError: something tries to access an oid that was recently garbage collected (i.e. deleted). You will never again be able to load this oid without exception (as it was deleted). Okay, so is this a bug in TemporaryStorage? If so, should I just chuck it in the collector? 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 )
