On Tuesday 01 November 2005 04:27, Grégoire Weber wrote:
2005/10/24, Stephan Richter [EMAIL PROTECTED]:
class IFoo(zope.interface.Interface):
attr = zope.interface.Attribute('doc string')
ITaggedValues(attr).someVariable = value
Any comments before I spend time writing this up?
Just for the notes:
I first favoured something like this:
class IFoo(zope.interface.Interface):
attr = zope.interface.Attribute('doc string')
attr.someVariable = value
but this can't work if ``attr`` is defined in ``IBar`` and setting a
tagged value is done in ``IFoo`` (which is
On Wednesday 19 October 2005 05:51, Grégoire Weber wrote:
while modeling the external API of an application I'd like to use the
tagged value feature of the interface implementation.
It seems to me that handling tagged values is implemented inconsequently.
I plan to make a proposal that would
On Monday 24 October 2005 16:44, Jim Fulton wrote:
Any comments before I spend time writing this up?
This won't work for tags whos keys are not python identifiers.
I'd like to encourage people to use ids (dotted names or urls) for
tags.
Okay, in this case I'll implement a mapping interface,
Hi everybody,
while modeling the external API of an application I'd like to use the
tagged value feature of the interface implementation.
It seems to me that handling tagged values is implemented inconsequently.
It would be nice if tagging attributes and interfaces would look the
same as
On Wednesday 19 October 2005 05:51, Grégoire Weber wrote:
Hi everybody,
while modeling the external API of an application I'd like to use the
tagged value feature of the interface implementation.
It seems to me that handling tagged values is implemented inconsequently.
It would be nice if
Stephan Richter wrote:
On Wednesday 19 October 2005 05:51, Grégoire Weber wrote:
Hi everybody,
while modeling the external API of an application I'd like to use the
tagged value feature of the interface implementation.
It seems to me that handling tagged values is implemented inconsequently.
