Bug#338692: ITP: python-pyprotocols -- Open Protocols and Component Adaptation for Python
Package: wnpp
Severity: wishlist
Owner: Bob Tanner <tanner@real-time.com>
* Package name : python-pyprotocols
Version : 0.9.3
Upstream Author : Phillip J. Eby <peak@eby-sarna com>
* URL : http://peak.telecommunity.com/PyProtocols.html
* License : http://www.zope.org/Resources/ZPL or http://www.python.org/2.3.2/license.html
Description : Open Protocols and Component Adaptation for Python
Do you hate having to write lots of if-then logic to test what type
something is? Wouldn't it be nice if you could just declare "I want
this object to have this behavior" and magically convert whatever
value you have, to the type you need? PyProtocols lets you do just
that, cleanly, quickly, and robustly -- even with built-in types or
other people's classes.
.
PyProtocols extends the PEP 246 adapt() function with a new
"declaration API" that lets you easily define your own protocols and
adapters, and declare what adapters should be used to adapt what
types, objects, or protocols. In addition to its own Interface type,
PyProtocols can also use Twisted and Zope's Interface types too. (Of
course, since Twisted and Zope interfaces aren't as flexible, only a
subset of the PyProtocols API works with them. Specific limitations
arelisted in the documentation.)
.
Home Page: http://peak.telecommunity.com/PyProtocols.html
Package: python2.3-pyprotocols
Architecture: any
Depends: python, python2.3
Description: Open Protocols and Component Adaptation for Python
Do you hate having to write lots of if-then logic to test what type
something is? Wouldn't it be nice if you could just declare "I want
this object to have this behavior" and magically convert whatever
value you have, to the type you need? PyProtocols lets you do just
that, cleanly, quickly, and robustly -- even with built-in types or
other people's classes.
.
PyProtocols extends the PEP 246 adapt() function with a new
"declaration API" that lets you easily define your own protocols and
adapters, and declare what adapters should be used to adapt what
types, objects, or protocols. In addition to its own Interface type,
PyProtocols can also use Twisted and Zope's Interface types too. (Of
course, since Twisted and Zope interfaces aren't as flexible, only a
subset of the PyProtocols API works with them. Specific limitations
arelisted in the documentation.)
.
Home Page: http://peak.telecommunity.com/PyProtocols.html
Package: python2.4-pyprotocols
Architecture: any
Depends: python2.4
Description: Open Protocols and Component Adaptation for Python
Do you hate having to write lots of if-then logic to test what type
something is? Wouldn't it be nice if you could just declare "I want
this object to have this behavior" and magically convert whatever
value you have, to the type you need? PyProtocols lets you do just
that, cleanly, quickly, and robustly -- even with built-in types or
other people's classes.
.
PyProtocols extends the PEP 246 adapt() function with a new
"declaration API" that lets you easily define your own protocols and
adapters, and declare what adapters should be used to adapt what
types, objects, or protocols. In addition to its own Interface type,
PyProtocols can also use Twisted and Zope's Interface types too. (Of
course, since Twisted and Zope interfaces aren't as flexible, only a
subset of the PyProtocols API works with them. Specific limitations
arelisted in the documentation.)
.
Home Page: http://peak.telecommunity.com/PyProtocols.html
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'oldstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14-1-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Reply to: