On 15.11.2006, at 00:39, Fred Drake wrote:
any problems with this? and if no, is it ok to backport it to 3.3
I don't know. It seems like a bug to me, but I'm no bastion of
backward-compatibility.
for me too, so i checked in the fixes on trunk and 3.3
Philipp von Weitershausen wrote:
...hence the quotes. It's a function in that I want to use it as an
adapter that doesn't need to be instantiated by a factory before being
used.
All adapters need to be instantiated.
Why?
def myStrAdapter(something):
return str(something)
This
Jean-François Roche wrote:
I meet a usecase that i don't really see how to solve. My users need
some kind of contextual help and these help files need to be in
different languages. I looked closer at onlinehelp but it seems that no
i18n link have been done. I was wondering if you might have an
Chris Withers wrote:
Philipp von Weitershausen wrote:
...hence the quotes. It's a function in that I want to use it as an
adapter that doesn't need to be instantiated by a factory before being
used.
All adapters need to be instantiated.
Why?
def myStrAdapter(something):
Chris Withers wrote:
Philipp von Weitershausen wrote:
...hence the quotes. It's a function in that I want to use it as an
adapter that doesn't need to be instantiated by a factory before
being used.
All adapters need to be instantiated.
Why?
def myStrAdapter(something):
return
Philipp von Weitershausen wrote at 2006-11-15 15:08 +0100:
...
def myStrAdapter(something):
return str(something)
It instantiates a 'str' object. The 'str' object is the adapter for
'something'.
Huh? This would be a severe terminology abuse:
An adapter should adapt something to
Dieter Maurer wrote:
Philipp von Weitershausen wrote at 2006-11-15 15:08 +0100:
...
def myStrAdapter(something):
return str(something)
It instantiates a 'str' object. The 'str' object is the adapter for
'something'.
Huh? This would be a severe terminology abuse:
I agree, it's bending
Philipp von Weitershausen wrote at 2006-11-15 20:34 +0100:
Dieter Maurer wrote:
Philipp von Weitershausen wrote at 2006-11-15 15:08 +0100:
...
def myStrAdapter(something):
return str(something)
It instantiates a 'str' object. The 'str' object is the adapter for
'something'.
Huh? This
Philipp von Weitershausen wrote:
Dieter Maurer wrote:
Philipp von Weitershausen wrote at 2006-11-15 15:08 +0100:
...
def myStrAdapter(something):
return str(something)
It instantiates a 'str' object. The 'str' object is the adapter for
'something'.
Huh? This would be a severe
Dieter Maurer wrote:
Philipp von Weitershausen wrote at 2006-11-15 20:34 +0100:
Dieter Maurer wrote:
Philipp von Weitershausen wrote at 2006-11-15 15:08 +0100:
...
def myStrAdapter(something):
return str(something)
It instantiates a 'str' object. The 'str' object is the adapter for
Philipp von Weitershausen wrote:
Dieter Maurer wrote:
Philipp von Weitershausen wrote at 2006-11-15 20:34 +0100:
Dieter Maurer wrote:
Philipp von Weitershausen wrote at 2006-11-15 15:08 +0100:
...
def myStrAdapter(something):
return str(something)
It instantiates a 'str' object. The
Jean-Marc Orliaguet wrote:
str(123) has the same syntax as IZopeDublinCore(myobj), but semantically
there is nothing in common between the two expressions.
I disagree.
IZopeDublinCore(obj)
is a flexible version of
ZDCAnnotatableAdapter(obj)
Flexible, because a different
12 matches
Mail list logo
