* "Roger Ineichen" [2009-03-09 02:12]:
> The zope.container package was broken.
> I added a missing ComponentLookupError import.
Also, there was a typo in that conditional branch, it should have been
self.context, not just context. I guess that's what I got for not writing a test
in the first pla
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martijn Faassen wrote:
> Chris Withers wrote:
>> Wichert Akkerman wrote:
>>> I would like to see a move away from zope testing frameworks to a more
>>> standard testing infrastructure: setup.py test, possibly combined with
>>> using nose.
>> I'd love t
Hi steering group and Dan
During update z3c.authenticator and replace the password with the
new zope.apssword implementation, I saw that the vocabulary
"Passsword Manager Names" is not available in the zope.password
package.
I think the password package should also provide this vocabulary.
Or at
2009/3/5 Martijn Faassen :
> Chris Withers wrote:
>> Martijn Faassen wrote:
>>> I think we can only make the correct determination if we get an idea of
>>> the performance implications. If it turns out the C code brings
>>> significant speedups in real-world applications, we should create a
>>> zop
Hi there,
Gary Poster wrote:
[snip]
> Fair enough.
Thanks for the feedback! I've recorded these as decisions of the
steering group.
Regards,
Martijn
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cr
On Mar 9, 2009, at 6:32 PM, Martijn Faassen wrote:
> Chris Withers wrote:
>> Wichert Akkerman wrote:
>>> I would like to see a move away from zope testing frameworks to a
>>> more
>>> standard testing infrastructure: setup.py test, possibly combined
>>> with
>>> using nose.
>>
>> I'd love to
2009/3/10 Martijn Pieters :
> On Mon, Mar 9, 2009 at 22:20, Dan Korostelev wrote:
>> As you may know, python 3 introduced the concept of annotations for
>> callable objects. That annotations store information about arguments
>> and return values, which is kinda nice language feature that will
>> a
Chris Withers wrote:
> Wichert Akkerman wrote:
>> I would like to see a move away from zope testing frameworks to a more
>> standard testing infrastructure: setup.py test, possibly combined with
>> using nose.
>
> I'd love to see a side-by-side feature comparison of the major python
> test discov
On Mon, Mar 9, 2009 at 22:20, Dan Korostelev wrote:
> As you may know, python 3 introduced the concept of annotations for
> callable objects. That annotations store information about arguments
> and return values, which is kinda nice language feature that will
> allow us to do interesting things.
On Mar 9, 2009, at 5:20 PM, Dan Korostelev wrote:
> Hi zope developers!
>
> As you may know, python 3 introduced the concept of annotations for
> callable objects. That annotations store information about arguments
> and return values, which is kinda nice language feature that will
> allow us to
Hi zope developers!
As you may know, python 3 introduced the concept of annotations for
callable objects. That annotations store information about arguments
and return values, which is kinda nice language feature that will
allow us to do interesting things.
But there's a problem: those annotation
Code snippet:
>>>def open(self, url, data=None):
>>> """See zope.testbrowser.interfaces.IBrowser"""
>>>url = str(url)
This string coercion is unfortunate, because ``mechanize`` accepts a
(mechanize-) request-object in place of a URL string here. Using a
custom request object all
Hi Tres
> Betreff: Re: AW: [Zope-dev] zope.container broken
[...]
> >>> Can someone with a linux/windows system release
> zope.component with
> >>> the C extensions?
> >> Why do you need a release?
> >
> > Hm, I'm confused. Because the existing release is broken.
> >
> >> I don't think we
On Mon, Mar 9, 2009 at 15:56, Dieter Maurer wrote:
> The "product_name" parameter used to be mandatory -- thus all
> calls to "ToolInit" had to use it.
> Then, a means was found to derive it automatically
> from the context. The developper was so happy that he wanted all
> others immediately drop
2009/3/9 Dieter Maurer :
> Jacob Holm wrote at 2009-3-6 01:55 +0100:
>> ...
>>I added it while working for ZC two years ago. It was needed to support
>>a use case where the context used for looking up the annotation was not
>>necessarily the current site. I don't know if the use case is still
>>rel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Roger Ineichen wrote:
> Hi Tres
>
>> Betreff: Re: [Zope-dev] zope.container broken
>>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Roger Ineichen wrote:
>>
>>> The zope.container package was broken.
>>> I added a missing ComponentLookupEr
Roger Ineichen wrote at 2009-3-8 14:38 +0100:
> ...
>Can you give an example of a meaningless deprecation
>warning?
A few of the deprecations I have disliked for a long time:
> /home/dieter/Z/Products/Archetypes/__init__.py:15: DeprecationWarning: The
> module, 'Products.CMFCore.CMFCorePermissio
Hi Tres
> Betreff: Re: [Zope-dev] zope.container broken
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Roger Ineichen wrote:
>
> > The zope.container package was broken.
> > I added a missing ComponentLookupError import.
>
> Yup, and there is no test for that 'browserDefault' raising
Jacob Holm wrote at 2009-3-6 01:55 +0100:
> ...
>I added it while working for ZC two years ago. It was needed to support
>a use case where the context used for looking up the annotation was not
>necessarily the current site. I don't know if the use case is still
>relevant to ZC, but the pattern
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tres Seaver wrote:
> Roger Ineichen wrote:
>
>> The zope.container package was broken.
>> I added a missing ComponentLookupError import.
>
> Yup, and there is no test for that 'browserDefault' raising the error,
> either.
>
>> Can someone with a lin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Roger Ineichen wrote:
> The zope.container package was broken.
> I added a missing ComponentLookupError import.
Yup, and there is no test for that 'browserDefault' raising the error,
either.
> Can someone with a linux/windows system release
> zope.c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Roger Ineichen wrote:
> The zope.container package was broken.
> I added a missing ComponentLookupError import.
Yup, and there is no test for that 'browserDefault' raising the error,
either.
> Can someone with a linux/windows system release
> zope.c
22 matches
Mail list logo
