ANN: visage (interfaces)

[jwp]

Hi,

I just pushed this up to pypi/github, and I hoped to acquire some c.l.py opinions.
It's experimental at this point, and might get scrapped.

visage is a loosely coupled interface registry. weakrefs make it cake to implement.

Basically, zope.interface, but where the interfaces are referenced by an identifier instead of the defining Interface class. Also, ABC registration isperformed when the Interface becomes available so that isinstance/issubclass checks can be performed on Implementation instances/classes.

FWICT, pyprotocols allows for something like this, but while introducing many "interesting concepts". (;

Currently, visage has no concept of adaption, but I'm suspecting that it could be built *on top* of the existing foundation.

Personally, I'd prefer to reference interfaces by an identifier. Notably, the idea of having to pull in a dependency in order to perform local tests that have no need for the formal Interface class is reason enough for me to use something like this instead of the existing solutions. Sure, to each their own.?

What's c.l.py's perspective on managing interfaces and implementations?

**** it, ship it? =)

 

[jwp]

I just pushed this up to pypi/github, and I hoped to acquire some c.l.py opinions.

http://github.com/jwp/py-visage

 

[alex23]

What's c.l.py's perspective on managing interfaces and implementations?

I've been working with Plone for the past year and have become a big
fan of interfaces. I must admit I _do_ like zope.interface's
adaptation, but your's looks lighter in a way that could be handy for
a side project, so I may have some more concrete feedback soon

BTW I think if you rename the ReStructured Text docs to .rst github
will automatically render them.

 

[jwp]

a side project, so I may have some more concrete feedback soon
=)

BTW I think if you rename the ReStructured Text docs to .rst github

will automatically render them.

Did not know that. Gonna go do a lot of git mv's now.

Thanks.

 

[Steven D'Aprano]

Did not know that. Gonna go do a lot of git mv's now.

Do *one* and see if github actually does render it. Then do the rest.

 

[jwp]

Do *one* and see if github actually does render it. Then do the rest.

Did it for one project. It does render it. =)

Naturally, sphinx autodoc links don't work. =( Come-on github, use dat fundin'

 

[jwp]

What's c.l.py's perspective on managing interfaces and implementations?

I pushed another version with support for IID references, so you can refer to implementations in annotations. The ultimate point of this is to give registry queries the ability to check for implementations with particular features:

@visage.lib.implementation('foo')
class Imp(object):
def meth(self) -> visage.lib.reference('bar'):
...

Imp.meth making a statement that a 'bar' implementation will be returned.

That is, consider code that is not aware of the modules that "Imp" is stored in but wants a 'foo' implementation whose "meth" method returns a 'bar' instance. Registry queries pave the way for supporting IID based implementation resolution. There is also the potential that registry information couldbe extracted on package installation for the purpose of an implementation index. Implementations could be imported on demand by modules that have no knowledge of the implementation.