Re: [Zope-dev] [Zope2.10+] zopectl run conflicts with Traversable
--On 22. Februar 2008 18:34:14 +0100 Jens Vagelpohl <[EMAIL PROTECTED]> wrote: On Feb 22, 2008, at 17:52 , Andreas Jung wrote: Hi, I (and some co-workers) encountered lately issues with traversal when running scripts using "zopectl run" from the command line. The lookup code fore views apparently expects always the existence of a REQUEST. What's the best approach to fix this issue in the traversal machinery? Is your use case not covered by creating a "fake" request using Testing.makerequest.makerequest, like so: if __name__ == "__main__": from Testing.makerequest import makerequest app = makerequest(app) Thanks for the workaround. I think the issue is way of a BBB foul. Traversal did work in the past without having a REQUEST and it should behave in the same way. Andreas pgp6UN5qLJ6NA.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] Backporting Zope3 bugfixes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 While profiling a basic Zope2 + Five application this afternoon against Zope 2.10.5, I discovered a huge performance bug in zope.security.management.newInteraction. It turns out that the bug had been fixed last summer, but only on the 3.4 branch and trunk for Zope3. I therefore cut a standalone zope.security 3.3 branch (and 3.3.3 tag) for use in the Zope2 tree checkout. I would like to raise awareness that "important" bugfixes for Zope3 components may need to get more love than we have been giving them: in particular, we may need to be prepared to backport performance-, stability-, or security-critical fixes back to earlier versions than those which are currently under active development: the set of dependents is going to be increasing, and increasingly long-lived. As we move to finer-grained egg releases, keeping up with these backports should be simpler: only the package requiring the backport should need to be re-released. Tres. - -- === Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] Palladion Software "Excellence by Design"http://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHv3f1+gerLs4ltQ4RApxMAKCXHFCCnG7uPg3+TLETkUYMmgvrAQCfRDYP D4yHHXpprf8m2N/83tW7Sqk= =cjCw -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] buildout 'versions' and 'develop' conflict
Hi, It seems that the 'versions' information in a buildout has a priority over 'develop'? What I wanted is to use the exact versions of the KGS: extends = http://download.zope.org/zope3.4/versions.cfg versions = versions Then for a particular egg (say, z3c.menu), use a develop-egg instead: develop = . z3c.menu However the develop-egg is never used, because of the version information. Shouldn't the 'develop' directive have a priority? Or is there another way to to what I want? thanks, Christophe ___ 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] Changing the system user's title
On Friday 22 February 2008, Benji York wrote: > I'd like to change it to something like "System User". I /think/ this > change shouldn't affect people much because until recently this > principle couldn't be looked up by it's ID (a recent fix to > zope.app.security made it possible). > > If this proposal meets with support (or is totally ignored ), I'll > make a bug fix release of zope.security with this change. +1 Regards, Stephan -- Stephan Richter Web Software Design, Development and Training Google me. "Zope Stephan Richter" ___ 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] [Zope2.10+] zopectl run conflicts with Traversable
On Feb 22, 2008, at 17:52 , Andreas Jung wrote: Hi, I (and some co-workers) encountered lately issues with traversal when running scripts using "zopectl run" from the command line. The lookup code fore views apparently expects always the existence of a REQUEST. What's the best approach to fix this issue in the traversal machinery? Is your use case not covered by creating a "fake" request using Testing.makerequest.makerequest, like so: if __name__ == "__main__": from Testing.makerequest import makerequest app = makerequest(app) jens ___ 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] [Zope2.10+] zopectl run conflicts with Traversable
Hi, I (and some co-workers) encountered lately issues with traversal when running scripts using "zopectl run" from the command line. The lookup code fore views apparently expects always the existence of a REQUEST. What's the best approach to fix this issue in the traversal machinery? Andreas --- File "", line 1, in ? File "import-bb-csv.py", line 92, in ? print r.getRID(),r.getObject() File "/local/HRS2/Devel/stillerj/Zope-2.11.0-b1/lib/python/Products/ZCatalog/CatalogBrains.py", line 92, in getObject target = parent.restrictedTraverse(path[-1]) File "/local/HRS2/Devel/stillerj/Zope-2.11.0-b1/lib/python/OFS/Traversable.py", line 301, in restrictedTraverse return self.unrestrictedTraverse(path, default, restricted=True) File "/local/HRS2/Devel/stillerj/Zope-2.11.0-b1/lib/python/OFS/Traversable.py", line 259, in unrestrictedTraverse next = queryMultiAdapter((obj, self.REQUEST), AttributeError: REQUEST -- ZOPYX Ltd. & Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany Web: www.zopyx.com - Email: [EMAIL PROTECTED] - Phone +49 - 7071 - 793376 Registergericht: Amtsgericht Stuttgart, Handelsregister A 381535 Geschäftsführer/Gesellschafter: ZOPYX Limited, Birmingham, UK E-Publishing, Python, Zope & Plone development, Consulting pgpvQgUVKBh73.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 )
Re: [Zope-dev] Changing the system user's title
Jim Fulton wrote: I'd prefer something even shorter, like "System". I think if someone sees this in a log, "System" will be less puzzling than "System User". An end user is likely to wonder "who" the system user is. +1 Perhaps a short explanation can be added to the description. +1 -- Benji York Senior Software Engineer Zope Corporation ___ 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] Changing the system user's title
Note that this only applies to the Zope 3 system user, which someday will be used for Zope 2 I expect. On Feb 22, 2008, at 11:32 AM, Benji York wrote: I have some automated tasks that invoke code that expects a principle to exist in the interaction, so I'd like to use the "system user" (principle ID zope.security.management.system_user, defined in zope.security) to perform them, but its current title of "Special System User that typically has all permissions" isn't exactly something I want to show end-users. I'd like to change it to something like "System User". I /think/ this change shouldn't affect people much because until recently this principle couldn't be looked up by it's ID (a recent fix to zope.app.security made it possible). I'd prefer something even shorter, like "System". I think if someone sees this in a log, "System" will be less puzzling than "System User". An end user is likely to wonder "who" the system user is. Perhaps a short explanation can be added to the description. If this proposal meets with support (or is totally ignored ), I'll make a bug fix release of zope.security with this change. +1 Jim -- Jim Fulton Zope Corporation ___ 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] Changing the system user's title
I have some automated tasks that invoke code that expects a principle to exist in the interaction, so I'd like to use the "system user" (principle ID zope.security.management.system_user, defined in zope.security) to perform them, but its current title of "Special System User that typically has all permissions" isn't exactly something I want to show end-users. I'd like to change it to something like "System User". I /think/ this change shouldn't affect people much because until recently this principle couldn't be looked up by it's ID (a recent fix to zope.app.security made it possible). If this proposal meets with support (or is totally ignored ), I'll make a bug fix release of zope.security with this change. -- Benji York Senior Software Engineer Zope Corporation ___ 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: Mailinglists on Launchpad
Christian Zagrodnick wrote: On 2008-02-18 11:20:05 +0100, Christian Theune <[EMAIL PROTECTED]> said: Launchpad started the beta tests for their mailing list offers. A while ago we discussed this option for future hosting of the mailing lists. The current implementation has the restriction that the mailing lists can not be hosted using custom domains (@zope.org). IMHO when migrating mailing lists the addresses should not change. I agree. I'm all for outsourcing the hosting of our mailing list, but I think it'd be a bad idea to change all the email addresses. It'll break people's settings, possibly break various archives, and so on. I think you should let them know that this this is important for us. Regards, Martijn ___ 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
Summary of messages to the zope-tests list. Period Thu Feb 21 12:00:00 2008 UTC to Fri Feb 22 12:00:00 2008 UTC. There were 6 messages: 6 from Zope Unit Tests. Tests passed OK --- Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Thu Feb 21 21:01:48 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-February/009149.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Thu Feb 21 21:03:18 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-February/009150.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Thu Feb 21 21:04:48 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-February/009151.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Thu Feb 21 21:06:18 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-February/009152.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Unit Tests Date: Thu Feb 21 21:07:49 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-February/009153.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Thu Feb 21 21:09:19 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-February/009154.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] z3c.blobfile
Hi all, Who is author of z3c.blobfile package? Could anybody make release? ___ 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 )
