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 -
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
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
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
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
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
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
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
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:
-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
--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
11 matches
Mail list logo