Re: [Zope3-dev] Re: zope.tal.xmlparser.XMLParser() dislikes unicode

2007-01-18 Thread Andreas Jung
--On 18. Januar 2007 08:29:57 -0500 Fred Drake <[EMAIL PROTECTED]> wrote: On 1/18/07, Andreas Jung <[EMAIL PROTECTED]> wrote: We're faster with new Zope versions than the W3C with any standard. So? The recommendation for XML 1.1 is already a done deal (a "second edition" was published last

Re: [Zope3-dev] Re: wildcard adapter

2007-01-18 Thread Philipp von Weitershausen
On 18 Jan 2007, at 09:53 , Chris Withers wrote: Philipp von Weitershausen wrote: If it is, then which of the following should I use to register a generic adapter for any single object to an interface: provideAdapter(...,adapts=(None,),...) This one. Given that you can register adapters for

[Zope3-dev] Re: SVN: zope.app.annotation/ Add zope.app.annotation as a top-level package.

2007-01-18 Thread Baiju M
Philipp von Weitershausen wrote: Baiju M wrote: [snip] > > I thought we can create individual eggs instead of a big zope.app > egg for Zope 3.4. Well, I don't think we have to make every single subpackage its own egg. We should pick our battles and start with those individual eggs that c

Re: [Zope3-dev] Re: zope.tal.xmlparser.XMLParser() dislikes unicode

2007-01-18 Thread Fred Drake
On 1/18/07, Andreas Jung <[EMAIL PROTECTED]> wrote: We're faster with new Zope versions than the W3C with any standard. So? The recommendation for XML 1.1 is already a done deal (a "second edition" was published last September), so there are already multiple specified versions. Since other ve

Re: [Zope3-dev] Re: wildcard adapter

2007-01-18 Thread Marius Gedminas
On Thu, Jan 18, 2007 at 08:53:36AM +, Chris Withers wrote: > Philipp von Weitershausen wrote: > >>If it is, then which of the following should I use to register a > >>generic adapter for any single object to an interface: > >> > >>provideAdapter(...,adapts=(None,),...) > > > >This one. > > Gi

Re: [Zope3-dev] wildcard adapter

2007-01-18 Thread Marius Gedminas
On Thu, Jan 18, 2007 at 08:55:17AM +, Chris Withers wrote: > Marius Gedminas wrote: > >BTW passing interfaces to provideAdapter/ is out of fashion. > > This stuff is getting almost perl-ish in it's "there's many ways to do > it, pick the style you like" nature.. There's a slight difference,

Re: [Zope3-dev] Re: Idea: Failure to lookup adapters

2007-01-18 Thread Chris Withers
Philipp von Weitershausen wrote: Code like this won't be run with python -O (which is what you'd obviously use in production). obviously... not. How many people actually do this? I wonder whether a different approach could be taken. The APIDOC code does already a registration analysis. Maybe

Re: [Zope3-dev] Re: wildcard adapter

2007-01-18 Thread Chris Withers
Philipp von Weitershausen wrote: If it is, then which of the following should I use to register a generic adapter for any single object to an interface: provideAdapter(...,adapts=(None,),...) This one. Given that you can register adapters for any class, whether or not it implements any int

Re: [Zope3-dev] wildcard adapter

2007-01-18 Thread Chris Withers
Marius Gedminas wrote: BTW passing interfaces to provideAdapter/ is out of fashion. This stuff is getting almost perl-ish in it's "there's many ways to do it, pick the style you like" nature.. I prefer using zope.component.adapts and zope.interface.implements (or zope.component.adapter and