| Key | Value |
|---|---|
| FileName | ./usr/share/doc/python-protocols/changelog.Debian.gz |
| FileSize | 1942 |
| MD5 | 985EC38953930DB85275EB7E512294D7 |
| SHA-1 | 06C6047872C8CA1A4D21BA1EEF3833CD1B2BCECF |
| SHA-256 | 6E79C67FC3C5A0C6E44BB23686964DA4A4C481DC06AA91AB37FAEBD55C4133F5 |
| SSDEEP | 48:X2E9Ddqj97BVXh6++BtIZwJJNfM78bjDhI3P:mEB0j97HR6+mtIZwJPfXbj6 |
| TLSH | T19A41ECE013E1C0DAAF95F23BF1735C0F2A961E754859812DBE564104276BD75D0D1C99 |
| hashlookup:parent-total | 10 |
| hashlookup:trust | 100 |
The searched file hash is included in 10 parent files which include package known and seen by metalookup. A sample is included below:
| Key | Value |
|---|---|
| FileSize | 36500 |
| MD5 | 08E1315E7E7E2EE3F09C367F5015DC1B |
| PackageDescription | 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 are listed in the documentation.) |
| PackageMaintainer | Debian QA Group <packages@qa.debian.org> |
| PackageName | python-protocols |
| PackageSection | python |
| PackageVersion | 1.0a.svn20070625-8 |
| SHA-1 | 40BE83CF6A9393B9F2256F5B3872EE74891D4F92 |
| SHA-256 | D1E8B4BF58EC59CAA6802412F84A852881B68296BFBCE1023ABDF88745AF5499 |
| Key | Value |
|---|---|
| FileSize | 35828 |
| MD5 | C750757B8C32393897918DCFB5A74015 |
| PackageDescription | 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 are listed in the documentation.) |
| PackageMaintainer | Debian QA Group <packages@qa.debian.org> |
| PackageName | python-protocols |
| PackageSection | python |
| PackageVersion | 1.0a.svn20070625-8 |
| SHA-1 | D4C2750894C3D09090E78EED72D4981A06B1E6DF |
| SHA-256 | 84331E1D2229BF3CD870A5FAC8357005AB765B4A0CCAB10F89D05E7BFACB3FA2 |
| Key | Value |
|---|---|
| FileSize | 37140 |
| MD5 | 5D304C7E8FB3D00A191539C9A787D7FB |
| PackageDescription | 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 are listed in the documentation.) |
| PackageMaintainer | Debian QA Group <packages@qa.debian.org> |
| PackageName | python-protocols |
| PackageSection | python |
| PackageVersion | 1.0a.svn20070625-8 |
| SHA-1 | 163D1E9C85FBD0DB21CA9C53D29C5E86E3329ED6 |
| SHA-256 | E924F590AA6726E4B1FCDFC76A689425D61321F4E5F22D7F177F8D0514E998ED |
| Key | Value |
|---|---|
| FileSize | 37736 |
| MD5 | 2A8A7045549467428988C62B51025824 |
| PackageDescription | 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 are listed in the documentation.) |
| PackageMaintainer | Debian QA Group <packages@qa.debian.org> |
| PackageName | python-protocols |
| PackageSection | python |
| PackageVersion | 1.0a.svn20070625-8 |
| SHA-1 | B2FECC393A928AAE1B1966ECD45AF61B1CBC879E |
| SHA-256 | 26EA9FF8AB853F9D79D7034D46611AC3F9D7B59150A032620E8763C62022905C |
| Key | Value |
|---|---|
| FileSize | 37184 |
| MD5 | FF9C502BCB8C4D1800A42809EDD4590B |
| PackageDescription | 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 are listed in the documentation.) |
| PackageMaintainer | Debian QA Group <packages@qa.debian.org> |
| PackageName | python-protocols |
| PackageSection | python |
| PackageVersion | 1.0a.svn20070625-8 |
| SHA-1 | 58F24565E89EDEBB4CEBEC41E29F808B5B2BFA98 |
| SHA-256 | 2A28747DD5D03287A22C0BBDBCFAAB307C7F3B8D63BCB48BEFD16A3F0395CA3C |
| Key | Value |
|---|---|
| FileSize | 35872 |
| MD5 | 19F39B7C78E8CF109ED59C13EAD2083C |
| PackageDescription | 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 are listed in the documentation.) |
| PackageMaintainer | Debian QA Group <packages@qa.debian.org> |
| PackageName | python-protocols |
| PackageSection | python |
| PackageVersion | 1.0a.svn20070625-8 |
| SHA-1 | 14BEDF7BE80C16C72FC525690DB343DFB9666BB5 |
| SHA-256 | 95EEC7406AFCB32A0979CC1B9D440EEEE9B559AA3887050AF122F0805D5330E3 |
| Key | Value |
|---|---|
| FileSize | 35540 |
| MD5 | 60563A399CA771E509F3B5413C516D12 |
| PackageDescription | 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 are listed in the documentation.) |
| PackageMaintainer | Debian QA Group <packages@qa.debian.org> |
| PackageName | python-protocols |
| PackageSection | python |
| PackageVersion | 1.0a.svn20070625-8 |
| SHA-1 | 8B842DCE8310076C3A79C39030D60864B01910EF |
| SHA-256 | B801C71F5C1E67A031E571E5DEAF759B272ED91119145E9AEC3737DF2560AF08 |
| Key | Value |
|---|---|
| FileSize | 35676 |
| MD5 | DC6E028D3262C70CC6DFE7B19D08BC7B |
| PackageDescription | 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 are listed in the documentation.) |
| PackageMaintainer | Debian QA Group <packages@qa.debian.org> |
| PackageName | python-protocols |
| PackageSection | python |
| PackageVersion | 1.0a.svn20070625-8 |
| SHA-1 | 514BDCA5955AA52314897F261172CBE4BBAB7388 |
| SHA-256 | 68EE1823EE4A26263A71F49E3B378B6FB9CE68F23442060806EF757E87F200C9 |
| Key | Value |
|---|---|
| FileSize | 35656 |
| MD5 | CD2762DB785B7FCEEA5CE68F1CB61E54 |
| PackageDescription | 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 are listed in the documentation.) |
| PackageMaintainer | Debian QA Group <packages@qa.debian.org> |
| PackageName | python-protocols |
| PackageSection | python |
| PackageVersion | 1.0a.svn20070625-8 |
| SHA-1 | F5E7BEFCE6D366A79F4D387726A392098519C5DC |
| SHA-256 | 0FC1F86BA9E0A5F3FC1D2043D7F3FE72EEEE8D13F424A3F03F548041AAC4460C |
| Key | Value |
|---|---|
| FileSize | 35548 |
| MD5 | 360D7482F7818C35C43380447D2933E9 |
| PackageDescription | 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 are listed in the documentation.) |
| PackageMaintainer | Debian QA Group <packages@qa.debian.org> |
| PackageName | python-protocols |
| PackageSection | python |
| PackageVersion | 1.0a.svn20070625-8 |
| SHA-1 | A4616FFE96D1521B06212F5D35FB90CC067631B1 |
| SHA-256 | 2557A654B36CDC3459DFFA47171E04D255EE110D131FFBB410BB31133CC9F77B |