El 1 Sep 2008, a las 19:26 , Dieter Maurer escribió:
> Chris Withers wrote at 2008-9-1 16:23 +0100:
>> ...
>>> auth = IAuthentication() # utility
>>> auth = IAuthentication(default=None)
>>> langs = IUserPreferredLanguages(request) # adapter
>>>
It's not possible to join the team:
"""
Restricted Team: New members can only be added by one of the team's
administrators.
"""
On Mon, Sep 1, 2008 at 2:06 PM, Andreas Jung <[EMAIL PROTECTED]> wrote:
> Hi there,
>
> I just submitted a possible security related Zope issue on Launchpad and
> notice
Chris Withers wrote at 2008-9-1 16:23 +0100:
> ...
>>auth = IAuthentication() # utility
>>auth = IAuthentication(default=None)
>>langs = IUserPreferredLanguages(request) # adapter
>>langs = IUserPreferredLanguages(request, default=None
Philipp von Weitershausen wrote at 2008-9-1 14:07 +0200:
> ...
>I've personally thought for some time that it would be quite nice if
>all you had to do was call an interface to look up a utility (which is
>sort of a multi-adapter of order 0) or to do some kind of adaption, no
>matter how many
Hi there,
I just submitted a possible security related Zope issue on Launchpad and
noticed that the bug has been assigned to the Zope Security Team which
consists only of Jim. I suggest that a number of competent developers
of the Zope 2 and Zope 3 world volunteer to join the team in order to ma
El 1 Sep 2008, a las 17:23 , Chris Withers escribió:
> Philipp von Weitershausen wrote:
>> I've personally thought for some time that it would be quite nice
>> if all you had to do was call an interface to look up a utility
>> (which is sort of a multi-adapter of order 0) or to do some kind
Philipp von Weitershausen wrote:
> I've personally thought for some time that it would be quite nice if
> all you had to do was call an interface to look up a utility (which is
> sort of a multi-adapter of order 0) or to do some kind of adaption, no
> matter how many objects you wanted to ada
Marius Gedminas wrote:
> So either let's make zope.app.testing not depend on the whole world,
+1
> or
> let's extract the core of zope.app.testing
+10
> and put it somewhere else
> (zope.testing?).
-1
cheers,
Chris
--
Simplistix - Content Management, Zope & Python Consulting
El 30 Aug 2008, a las 07:50 , Dieter Maurer escribió:
> Chris Withers wrote at 2008-8-29 10:25 +0100:
>> Dieter Maurer wrote:
>>> Then, we could get rid of the "{get|query}[Multi]Adapter" altogether
>>> and consistently use "I()" with appropriate optional
>>> parameters --
>>> what a simplifi
Summary of messages to the zope-tests list.
Period Sun Aug 31 11:00:00 2008 UTC to Mon Sep 1 11:00:00 2008 UTC.
There were 5 messages: 5 from Zope Tests.
Tests passed OK
---
Subject: OK : Zope-2.8 Python-2.3.6 : Linux
From: Zope Tests
Date: Sun Aug 31 20:53:12 EDT 2008
URL: http://m
Hi Christian
> Betreff: Re: [Zope-dev] Make simple ISource usable
>
> On Sun, 2008-08-31 at 16:51 -0400, Marius Gedminas wrote:
> > On Sun, Aug 31, 2008 at 10:23:00PM +0200, Christian
> Zagrodnick wrote:
> > > Wait. zope.schema really shouldn't know about terms.
> Terms are about
> > > the use
Hi Christian
> Betreff: Re: [Zope-dev] Make simple ISource usable
[...]
> > The ITrems is a standard API for handle ISource, doesn't
> nmatter how
> > you will query or get our data form an ISource.
>
> This sounds like you want to implement something different
> than ITerms but that you see
Hi Christian
> Betreff: Re: [Zope-dev] Make simple ISource usable
[...]
> > This sounds like you want to implement something different
> than ITerms
> > but that you see a structural similarity between what you want and
> > what ITerms already do.
> >
> > I think this causes some confusion
Hi Christian
> Betreff: Re: [Zope-dev] Make simple ISource usable
[...]
> > Are you arguing that zope.schema.Field should not have a title
> > attribute?
>
> No no no, sorry :)
>
> I only don't see why I need titles for a source all the time.
> If you need both tied toogether (which frankly
14 matches
Mail list logo
