[Zope-dev] Re: zope.traversing dependencies
Stephan Richter wrote: I think the application control namespace code could simply be moved to zope.app.applicationcontrol, since the latter package does needs zope.traversing anyways. True, but I don't see how to do this cleanly as long as the namespace handler for the etc namespace is implemented as straight-forward as it is now. Have we reached the point where we want to introduce that registry the comment in zope.traversing.namespace.etc.traverse suggests? -- Thomas ___ 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.traversing dependencies
Tres Seaver wrote: +100 to shedding the dependencies. Could we have the conditional import work as a fallback to a utility lookup? And then change 'zope.applicationcontrol' to register such a utility? This should be possible, but the utility lookup would have to be conditional as well since it would have to target zope.app.applicationcontrol.interfaces.IApplicationControl which may not be available either after the dependency on zope.app.applicationcontrol has been lifted. OTOH, if the application controller were to be registered as a utility, should it stay importable from the module, at least for a transition period? If zope.app.applicationcontrol.applicationController was removed, would it be sufficient to adapt the zope.app.publication tests, or are there other packages expected to break in that case? Philosophically, when is it best to provide something like the application controller as a global utility and when is it sufficient to bind it to a name in a module? -- Thomas ___ 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: 5 OK
Summary of messages to the zope-tests list. Period Tue Nov 20 13:00:00 2007 UTC to Wed Nov 21 13:00:00 2007 UTC. There were 5 messages: 5 from Zope Unit Tests. Tests passed OK --- Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Tue Nov 20 20:53:00 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-November/008676.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Tue Nov 20 20:54:30 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-November/008677.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Tue Nov 20 20:56:00 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-November/008678.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Tue Nov 20 20:57:31 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-November/008679.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Tue Nov 20 20:59:01 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-November/008680.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: Splitting 'Signals' into an egg?
On Oct 4, 2007 11:02 AM, Sidnei da Silva [EMAIL PROTECTED] wrote: Not sure what Zope 3 is using these days (haven't checked), but Zope 2 had a 'Signals' package that handled signaling events on both Windows and *nix in a somewhat transparent way. Has anyone thought of packaging that as an egg? Toc toc, is there anybody out there? -- Sidnei da Silva Enfold Systemshttp://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214 ___ 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: RestrtrictedPython vs zope.security.untrustedpython
Chris Withers wrote at 2007-11-20 23:55 +: Dieter Maurer wrote: You execute their code in a globals the __builtins__ of which contains precisely the builtins you want to give them. unfortunately that still leaves the import problems, correct? The import command is mapped to the __import__ builtin. Thus, changing the __import__ builtin -- 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: zope.traversing dependencies
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thomas Lotze wrote: Tres Seaver wrote: +100 to shedding the dependencies. Could we have the conditional import work as a fallback to a utility lookup? And then change 'zope.applicationcontrol' to register such a utility? This should be possible, but the utility lookup would have to be conditional as well since it would have to target zope.app.applicationcontrol.interfaces.IApplicationControl which may not be available either after the dependency on zope.app.applicationcontrol has been lifted. Hmm, I guess I hadn't realized that the interface was in the zope.app package. Shouldn't the interface be in a more dependable package, from which clients can import it without depending on a given implementation? One logical place for the interface is actually in zope.traversing: that would break the dependency inversion. OTOH, if the application controller were to be registered as a utility, should it stay importable from the module, at least for a transition period? If zope.app.applicationcontrol.applicationController was removed, would it be sufficient to adapt the zope.app.publication tests, or are there other packages expected to break in that case? Philosophically, when is it best to provide something like the application controller as a global utility and when is it sufficient to bind it to a name in a module? Philosophically, a utility lookup allows for pluggability: it is a looser coupling (to the implementation) than an import. I would prefer such an indirection over dependency cycles, any day of the week. Tres. - -- === Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHRIAs+gerLs4ltQ4RAuf3AJ0eQtloAkzay4NlbEbYob5sUJh4+QCgr1M4 bAqX0YqQrxpq1A5/Ir1cPiw= =NQgZ -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 )
[Zope-dev] easier install
FYI, this is somewhat related to the convos we've had about the KGS/ PyPi/buildout/setuptools/easy_install: http://www.plope.com/Members/chrism/easier_install - C ___ 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: Splitting 'Signals' into an egg?
I suspect nobody responded because we're a litle behind the 8-ball on getting the set of eggs we've already released into the wild working right, but +1 to this eventually... On Nov 21, 2007, at 8:09 AM, Sidnei da Silva wrote: On Oct 4, 2007 11:02 AM, Sidnei da Silva [EMAIL PROTECTED] wrote: Not sure what Zope 3 is using these days (haven't checked), but Zope 2 had a 'Signals' package that handled signaling events on both Windows and *nix in a somewhat transparent way. Has anyone thought of packaging that as an egg? Toc toc, is there anybody out there? -- Sidnei da Silva Enfold Systemshttp://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214 ___ 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 )
